Forum Navigation
Please or Register to create posts and topics.

Rudder Trim stuck

Hi all,

I have just been upgrading, adding a 4th computer so I have been quite busy with ' housekeeping' lately.

I am running P3d v4.2.

I turned the computers on a week ago and for no reason the L rudder trim was fully to the left. So much so it had a red square around it on the EICAS at takeoff. Well you can just imagine that taking off with a rudder pulled to the Left was not going to end well.

What would you do ?

Well I don't mind admitting that it had me stumped. With my experience I went through the obvious first.

Pressing the S on the keyboard showing the plane from behind did not show any deviation of the rudder from neutral..

On the Yoke did someone push the trim switch fully lateral for the Aileron/rudder (whichever you have set it up for ) ?    No was the answer.

Next, do you have a conflict between FSUIPC and the keyboard commands in P3D/FSX ?  Well I pushed on the keyboard combination to center the trim with no change.

So what was the answer ?

Change planes, in my case was the other Learjet 45. Make sure that the rudder trim was centred and then save the flight as DEFAULT.  Then change the plane back to your usual Learjet model, making sure that the centreing of the Rudder trim has 'taken' .  Then SAVE again as DEFAULT flight.

Do not ask me how it is possible to shut down everything that was working fine and then wake up next day to find these glitches happen for no apparent reason. Go figure.

I for months had an issue that I could not solve. Think this through.

1/ Turn the VOR1 OBS knob and the elevator trim goes up.

2/Turn the Heading knob and the outside view changes as if tapping the S keyboard button.

3/Turn the Alt knob and the gear would go up or down.

4/Turn the VOR2 OBS knob and the Trim would change.

Now if you can link any of those actions then you're a legend.

The final fix was to delete most keyboard commands except for a few important ones you need. The problem you may find as I did is now I cannot get any life out of the ATC window. So I hit restore defaults for the keyboards commands. Well thinking I have got back to square one, voila, now the FGC knobs all perform as expected with NO conflicts. Go figure again !

Take home message.

P3D will randomly save configurations to itself. Go back to basics and save and then see what you are still left with.

Trust me, if you can get it all to work at once, our Learjet 45  is a sight to behold. Don't always look for FSUIPC or Interface It  for the solution, it can be Prepar3d itself as the culprit.

Regards

Mark Speechley

Uploaded files:
  • You need to login to have access to uploads.

Hey Mark,

As I was reading through this, I was thinking you were having conflicts with keyboard commands which you also figured out.  There is no rhyme or rhythm why some keyboard commands conflict with some FSUIPC commands.  I have not seen any of your specific conflict issues which tells me it might have something to do with the way P3D assigns interface cards as joystick assignments.  This might be why you may see one set of conflicts while another guy using the same interface cards, FSUIPC offsets and P3D will see a different set of conflicts.  My unproven theory anyway!

If I understand you correctly,  you loaded the keyboard commands back up to "cherry pick" around the ATC window commands but now everything works without deleting any commands?  If so very strange but very good!

 

You are absolutely right Mark! P3D default settings can cause all sorts of problems.   I found deleting all P3D  keyboard settings on a new install of P3D is a must.   I discussed a way to delete / save those settings in the P3Dv4 upgrade thread.  You can save the file somewhere for future use to save you from manually deleting each setting in P3D.

Thanks Ron and Shane,

The point of this forum is to add to the knowledge base with us old timers parting with our 'experience'.

Hopefully it will help out the new guys coming through.

Mark