Here I am again with yet another strange problem that not that many people have had.

After installing FSLabs and going back to PMDG 737, my throttles are controlling the rudder and I have no clue as to why.

I've checked everything is FSUIPC and Prepar3d and nothing is out of whack.

Has anyone had this happen before?

Thanks.

36 minutes ago, Jeff Nielsen said:

After installing FSLabs and going back to PMDG 737, my throttles are controlling the rudder and I have no clue as to why.

I've checked everything is FSUIPC and Prepar3d and nothing is out of whack.

Seems pretty clear that something is out of whack.

Your throttles--plural--are controlling the rudder?  How so?  Movement of each throttle lever does what, exactly, with the rudder?

How did you "check everything" in FSUIPC and P3D?  I'd recommend you move your FSUIPC5.ini file out of the modules folder and let it build a new one and see if the behavior persists.  If it doesn't, you have some investigation to do in your control assignments there.  If the behavior remains, the next step would be to disable FSUIPC entirely (set disabled to True in the dll.xml file) and see if it persists.  If it does, then time to check all of your control axis assignments in P3D via the menu.  Are you using a third-party device driver or control program with your flight controller?  If so, there could be something amiss there, too.

Regards

 

18 minutes ago, w6kd said:

Seems pretty clear that something is out of whack.

Your throttles--plural--are controlling the rudder?  How so?  Movement of each throttle lever does what, exactly, with the rudder?

How did you "check everything" in FSUIPC and P3D?  I'd recommend you move your FSUIPC5.ini file out of the modules folder and let it build a new one and see if the behavior persists.  If it doesn't, you have some investigation to do in your control assignments there.  If the behavior remains, the next step would be to disable FSUIPC entirely (set disabled to True in the dll.xml file) and see if it persists.  If it does, then time to check all of your control axis assignments in P3D via the menu.  Are you using a third-party device driver or control program with your flight controller?  If so, there could be something amiss there, too.

Regards

 

Thanks for the reply, but yeah, I've been all over FSUIPC and the in sim settings.  No third party control program is being used.

3 minutes ago, Jeff Nielsen said:

Thanks for the reply, but yeah, I've been all over FSUIPC and the in sim settings.  No third party control program is being used.

All over...as in manual inspection of the .ini file?

Are there any axis assignments related to the steering tiller axis?  Could P3D autorudder have been turned on?

Regards

 

1 minute ago, w6kd said:

All over...as in manual inspection of the .ini file?

Are there any axis assignments related to the steering tiller axis?  Could P3D autorudder have been turned on?

Regards

 

No, not that all over.  I'm going to load of the FSL A320 and take off the nose wheel steering.  I have a feeling that may be the issue.

When this happens to my sim most times P3D added a new axis (usually more than one) in the axis control in the sim. Take a look at each device under axis in the sim. You'll probably find the throttle control also assigned to a rudder axis.

4 minutes ago, Irishcurse said:

When this happens to my sim most times P3D added a new axis (usually more than one) in the axis control in the sim. Take a look at each device under axis in the sim. You'll probably find the throttle control also assigned to a rudder axis.

Ok, yeah, but only in the calibration settings do I see this.  it's clear as day.  Not sure why it's using the same letters to assign axis like that.  In the axis assignments, however it doesn't do this.  This is absolutely insane.

Now the brakes are also moving the rudder

Ok, back in business.  FSUIPC had a different axis assigned.  Not sure how, but it did.

 

5 hours ago, Jeff Nielsen said:

Ok, back in business.  FSUIPC had a different axis assigned.  Not sure how, but it did.

In the Advanced User Guide for FSUIPC it describes how to assign a fixed ID for a joystick device (alpha rather than the Windows-assigned numeric Joystick ID) that will persist across disconnections and reconnections of the USB HID devices.  Sometimes if you disconnect a device, or even if the connection is intermittent or pulled loose, Windows can assign a different joystick ID to the device when it reconnects.  Once I started using that facility, random changes to my assigned axes pretty much stopped happening.

Regards