Error in FSUIPC

[Paalron]

I think I started this in the wrong forum, so I've created a new one here.

Sorry to bother you again, but something strange is happening. MSFS2020 and FSUIPC7.5.2. Started sim, checked that all sim controls are for empty profiles and configured what I need in FSUIPC. Throttle 1 and 2 work as they should. The next time I start sim, Throttle 2 is at the top and none of them work. Most likely I have done something wrong, but I can't figure out what.

Can you help me please.

FSUIPC7.iniFetching info...

[John Dowson]

  On 3/30/2025 at 11:02 AM, Paalron said:

I think I started this in the wrong forum, so I've created a new one here.

Expand  

No problem - I have deleted your other post (but I would have moved it for you if you had not posted again).

  On 3/30/2025 at 11:02 AM, Paalron said:

The next time I start sim, Throttle 2 is at the top and none of them work.

Expand  

Not sure what you mean by "Throttle 2 is at the top"...?

But your throttle assignments look very strange:

  Quote

[Axes.PMDG]
RangeRepeatRate=10
0=AX,1124,D,1,0,0,0    -{ DIRECT: Aileron }-
1=AY,643,D,2,0,0,0    -{ DIRECT: Elevator }-
2=BX,256,D,7,0,0,0    -{ DIRECT: LeftBrake }-
3=BY,256,D,8,0,0,0    -{ DIRECT: RightBrake }-
4=BR,3161,D,3,0,0,0    -{ DIRECT: Rudder }-
5=CX,256,D,10,0,0,0    -{ DIRECT: Throttle2 }-
6=CZ,256,D,23,0,0,0    -{ DIRECT: Flaps }-
7=DX,1,D,10,0,0,0    -{ DIRECT: Throttle2 }-
8=DY,1,D,10,0,0,0    -{ DIRECT: Throttle2 }-
9=EX,130,D,22,0,0,0    -{ DIRECT: Spoilers }-
10=EY,1,D,9,0,0,0    -{ DIRECT: Throttle1 }-
11=EZ,28606,D,9,0,0,0    -{ DIRECT: Throttle1 }-
 

Expand  

You have Throttle2 assigned to both the X and Y axis on one Saitek Pro Flight Quadrant (as well as on your BU0836 Interface device), and Throttle1 assigned to axis Y and Z on the other Saitek Pro Flight Quadrant.
I would remove all them and assign again. Do you want to assign both throttles on one device, or each throttle on a separate device?
Once you have assigned and it is working, check and make a backup of your ini. Then the next time, if the set-up has changed again, show me that ini as well as the backup.

 

[Paalron]

Still weird things happening. Deleted the places you said and started over. With the new setup Throttle 1 works, n#. 2 doesn't move. And in the Joystick Calibration picture there is a big difference between In and Out on 1 and 2.

FSUIPC7.iniFetching info... Axes.rtfFetching info...

[John Dowson]

Your ini file shows that you have assigned your throttles to the Y axis on your Saitek Pro Flight Quadrants (devices D and E):

  Quote

[Axes.PMDG]
RangeRepeatRate=10
10=
11=
0=AX,1124,D,1,0,0,0    -{ DIRECT: Aileron }-
1=AY,643,D,2,0,0,0    -{ DIRECT: Elevator }-
2=BX,256,D,7,0,0,0    -{ DIRECT: LeftBrake }-
3=BY,256,D,8,0,0,0    -{ DIRECT: RightBrake }-
4=BR,3161,D,3,0,0,0    -{ DIRECT: Rudder }-
5=CZ,256,D,23,0,0,0    -{ DIRECT: Flaps }-
6=DY,1,D,10,0,0,0    -{ DIRECT: Throttle2 }-
7=EX,130,D,22,0,0,0    -{ DIRECT: Spoilers }-
8=EY,1,D,9,0,0,0    -{ DIRECT: Throttle1 }-
 

Expand  

But the images you attached show Throttle1 assigned to the Z axis. Therefore the images and ini files don't seem to match.
(Also, please make sure that you have exited FSUIPC7 before attaching files).

I think what is happening is that when you are moving the axis you want to assign to the throttle, another axis is being detected first. This can happen, and when it does you can either click Clear to start again, or Ignore Axis if the same axis keeps getting detected. Check the In/Out values are changing once the moved axis is detected - if they stop changing (or only change slightly) then a different axis has been detected and you need to try again,

Also, why are you using a delta value of 1? That is extremely low and is not recommended - the default value of 256 should be sufficient, so just use that for now and only update if you really need a finer resolution, and reduce in stages (e.g. try 200 first, then maybe 175, etc). But 256 should really be sufficient resolution when you have a 32768 value range.

So, I would again delete any axis assignments to throttle (as well as those empty assignments) and try again. Delete these when FSUIPC7 is closed, or when the axis assignment panel is open and click Reload all assignments afterwards. And then re-assign following what I have said.

  On 3/30/2025 at 2:54 PM, Paalron said:

And in the Joystick Calibration picture there is a big difference between In and Out on 1 and 2.

Expand  

That is ok and how it should be. You are assigning with no reverse zone, so the axis range of -16384 to +16384 is calibrated to the forward thrust range of 0 to 16384, so when the axis is at position -16384 the actual axis value that should be sent is 0.