P-47D throttle and prop RPM synch

[AKA_Relent]

The P-47D throttle and prop RPM synch does not seem to be working correctly (or like it used to).

 

It used to be that when synched, as you move the throttle up and down, the prop RPM would be in synch.  Now, for the past couple of updates, I've noticed that while the prop RPM stays in synch when you increase throttle, that it doesn't when you decrease throttle.  For example, if you push the throttle to 90% the prop RPM goes to 90%.  But if you throttle back to say 70%, the prop RPM is stuck at 90% and doesn't move until you manually drop it down to synch with the throttle setting (e.g. 70%).

 

Anyone else observe this behavior?  If so, is this a bug, or is the way it's supposed to be?

 

Thanks..

AKA_Relent

[Ghost666]

It's the why it should be, was wrong before.

[LukeFF]

The prop RPM lever latch was designed that way, so the pilot wouldn't inadvertently reduce RPMs before reducing manifold pressure and thus cause engine detonation.  

Edited June 10, 2020 by LukeFF

[AKA_Relent]

Thanks for the replies, good to know.

[SCU_Server]

In the P47-D you can latch the P and B buttons to the throttle with small tabs that push in to place to keep them linked>

In full auto mode the P slider moves back and forward with the throttle with no issues, if however you turn everything to manual the P lever slides forward but wont come back, the B lever works fine both ways, I have the buttons mapped in the controls section for this to happen and can see the little leaves latch and unlatch but the P latch seems broken at the rear and doesnt have enough material to stay latched.

What is the fix for this ??

Cheers

Edited June 11, 2020 by SCU_Server

[migmadmarine]

This is how it functioned on the actual aircraft. 

[SCU_Server]

Really, ok thanks for the info.

So in full auto mode when it latches and moves back and forwards that is incorrect ??, is the full auto mode broken then  ??.

Also flying the DCS P47-D and the P latches for both forward and rearward movement, it could be a different model I guess and changed for that particular version.