The rudder (through my rudder T-Pendular) are responding fine when the engine is off (cold start). I tried in 172 & P18 dakota. As soon as the engine is running, I lose the rudder control (the brakes controls are still fine).
FREQUENCY OF ISSUE
Immediatly as the engine start.
REPRODUCTION STEPS
Load Dakota or 172 cold and dark
Check rudder control (fine) parking control (fine)
Start the engine
Check rudder control (failed), parking control (fine)
YOUR SETTINGS
If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.
What peripherals are you using:
Are you using Developer Mode or have you made any changes to it? No
Just flew the Dakota on a 1hr flight, cold and dark start. No issues with rudder for me, taxied at departure and arrival with no problems, rudder also responsive in flight.
May be. But when reverting to SU3 everything is normal. And I do not see any other rudder assignment to my other periphericals (mouse / keyboard / throtthle / joystick or pendular rudder).
I’m not seeing this issue in the default C172. Does this issue still occur if, for testing purposes, you unplug your Thrustmaster T-Pendular and just use the keyboard for rudder control?
I agree with @scruffyphal that there could be a binding problem with your rudder settings in SU4.
Waco biplane, DC-3, Stearman, you name it. Rudder stops responding once engine is running. Once going fast enough it starts working again (somewhere around 25-40 kts).
You need to turn off the prop wash effect on the controls in FSRealistic Pro. It’s breaks them for some reason. At some point I assume the developer of FSRealistic Pro will fix this issue.