Throttle operating left brake

[Peter32427]

I'm running P3d V4.3 along with FSUIPC 5.132 which is registered.  I'm running it in Win 10 64 bit.

Everything was running fine until I installed the A2A Spitfire.  Prior to that I was running the FSLabs A320 and the A2A C172 with out problem.

But now when I advance the throttle, it causes the left brake to activate.

My controller is a Saitek X55.

In 'Axis Assignment' everything checks out OK, so when I move the throttle, 'Throttle' comes up along with 'Send Direct to FSUIPC Calibration.  The same with Left Brake and Right Brake.

But in 'Joystick calibration' (2 of 11) when I advance the throttle, numbers start to appear in the Left Brake section.

Typically, now when I advance the throttles in the A320, it move forward, but turns to the left!

I've double checked any conflicts.  The Saitek control software has no control entries.  Similarly the are no axis controls in P3D - all the axis controls are run through FSUIPC.

Help!!

Pegards,

Peter

[Thomas Richter]

Hi,

the A2A installation might have forced P3D to reset the Controller setting. Make sure box for 'Controllers' is disabled in P3D option settings.

Thomas

[Peter32427]

Hi Thomas,

Thanks for your reply, but I have already ensured that the 'Controllers were Disabled' in P3D.

Peter

[Pete Dowson]

1 hour ago, Peter32427 said:

when I advance the throttle, it causes the left brake to activate.

You certainly have multiple assignments. There's really no way otherwise.

1 hour ago, Peter32427 said:

But in 'Joystick calibration' (2 of 11) when I advance the throttle, numbers start to appear in the Left Brake section.

The calibration section detects what is going into the simulator, NOT what thejoysticks or their assignments are doing. Measurements there could even come program a program or plug-in.

If you'd like to attach your FSUIPC5.INI file I can check your assignemtns there, but from what you've said it doesn't sound likely to be anything there.

Pete

 

[Peter32427]

Hi Pete,

Thanks for your reply.  The ini file is atached.

Peter

FSUIPC5.ini

[Thomas Richter]

Hi,

Quote

[JoyNames]
AutoAssignLetters=No
0=Saitek Pro Flight X-55 Rhino Throttle
0.GUID={F1964850-9A3D-11E7-8004-444553540000}
1=Saitek Pro Flight X-55 Rhino Stick
1.GUID={F1966F60-9A3D-11E7-8005-444553540000}
2=CH Pro Pedals USB
2.GUID={B62EAC30-9A51-11E7-8007-444553540000}

[Axes]
PollInterval=10
RangeRepeatRate=10
0=0X,384,D,7,0,0,0    -{ DIRECT: LeftBrake }-
1=0Y,256,D,8,0,0,0    -{ DIRECT: RightBrake }-
2=1X,256,D,1,0,0,0    -{ DIRECT: Aileron }-
3=1Y,367,D,2,0,0,0    -{ DIRECT: Elevator }-
4=1R,5219,D,1,0,0,0    -{ DIRECT: Aileron }-
5=2X,256,F,65765,0,0,0    -{ TO SIM: AXIS_THROTTLE_SET }-
6=2Y,256,F,65765,0,0,0    -{ TO SIM: AXIS_THROTTLE_SET }-

[Axes.A2A C172]
RangeRepeatRate=10
0=0X,384,D,7,0,0,0    -{ DIRECT: LeftBrake }-
1=0Y,256,D,4,0,0,0    -{ DIRECT: Throttle }-
2=0Z,256,F,65764,0,0,0    -{ TO SIM: AXIS_RUDDER_SET }-
3=1X,256,D,1,0,0,0    -{ DIRECT: Aileron }-
4=1Y,367,D,2,0,0,0    -{ DIRECT: Elevator }-
5=1R,5219,D,1,0,0,0    -{ DIRECT: Aileron }-
6=2X,256,D,7,0,0,0    -{ DIRECT: LeftBrake }-
7=2Y,256,F,8,0,0,0    -{ TO SIM: Custom control: <8> }-

[Axes.FS Labs A320]
RangeRepeatRate=10
0=0X,384,D,7,0,0,0    -{ DIRECT: LeftBrake }-
1=0Y,256,D,4,0,0,0    -{ DIRECT: Throttle }-
2=1X,256,D,1,0,0,0    -{ DIRECT: Aileron }-
3=1Y,367,D,2,0,0,0    -{ DIRECT: Elevator }-
4=1R,1,F,66818,0,0,0    -{ TO SIM: STEERING_SET }-
5=2X,256,D,7,0,0,0    -{ DIRECT: LeftBrake }-
6=2Y,256,D,8,0,0,0    -{ DIRECT: RightBrake }-
7=2Z,256,D,3,0,0,0    -{ DIRECT: Rudder }-

[Axes.A2A Spitfire]
RangeRepeatRate=10
0=0X,384,D,7,0,0,0    -{ DIRECT: LeftBrake }-
1=0Y,256,D,4,0,0,0    -{ DIRECT: Throttle }-
2=1X,256,D,1,0,0,0    -{ DIRECT: Aileron }-
3=1Y,367,D,2,0,0,0    -{ DIRECT: Elevator }-
4=2X,256,D,7,0,0,0    -{ DIRECT: LeftBrake }-
5=2Y,256,D,8,0,0,0    -{ DIRECT: RightBrake }-
6=2Z,256,F,65696,0,0,0    -{ TO SIM: RUDDER_SET }-

As you can see all your profiles have the LeftBrake double defined, and always to the X-axis of the Saitek Pro Flight X-55 Rhino Throttle.

You need to correct that.

Thomas

[Peter32427]

Hi Thomas,

Many thanks for identifying the problem.  I'm no fsuipc ini expert, but that ini file just looks a complete mess.

Under [joynames], it has assigned 0 to the throttle, 1 to the stck and 2 to the pedals - fair enough.  However under the individual [Axes] things appear to be assigned all over the place including 'LeftBrake' to the throttle!

Can I get FSUIPC to rebuild the ini file from scratch?

Failing that, something like the example below would appear to make more sense.

0=0X,256,F,65765,0,0,0 -{ TO SIM: AXIS_THROTTLE_SET }-
1=0Y,256,F,65765,0,0,0 -{ TO SIM: AXIS_THROTTLE_SET }-

2=1X,256,D,1,0,0,0 -{ DIRECT: Aileron }-
3=1Y,367,D,2,0,0,0 -{ DIRECT: Elevator }-
4=1R,5219,D,1,0,0,0 -{ DIRECT: Aileron }-

5=2X,384,D,7,0,0,0 -{ DIRECT: LeftBrake }-
6=2Y,256,D,8,0,0,0 -{ DIRECT: RightBrake }-
7=2Z,256,F,65764,0,0,0 -{ TO SIM: AXIS_RUDDER_SET }-

I'm not sure when to use {DIRECT} and when to use (TO SIM}.

Your thoughts?

Regards,

Peter

[Pete Dowson]

1 hour ago, Peter32427 said:

I'm no fsuipc ini expert, but that ini file just looks a complete mess.

With multiple controllers like that you'd do much better to assign letters to the entries in the JoyNames section, as described in the Joy Letters chapter of the User Guide. Or set AutoAssignLetters=Yes if you don't mind them being called A, B, C ... I would use Y for Yoke, T for throttle, R for Rudder, and so on. You can do with before running  session and FSUIPC will automatically change the 0, 1, 2 assignments to the assigned letters.

1 hour ago, Peter32427 said:

Can I get FSUIPC to rebuild the ini file from scratch?

Just deleting the INI file does that. Then you'd need to re-do all your assignments and calibrations, and re-set any other options you use.

Alternatively, either delete or correct all of the entries which appear wrong. Deletion and reassignment in-sim is probably safest if you are not sure.

1 hour ago, Peter32427 said:

I'm not sure when to use {DIRECT} and when to use (TO SIM}

The Direct method is more efficient, and offers some axes not otherwise available. But some aircraft don't like that method for some controls as it bypasses their own interception -- for example, throttles for some PMDG aircraft. The "to sim" method is identical to assigning in the simulator's assignments.

So, try the "direct" method to start with, but switch to the "to sim" method if you get any problems with specific axes. It doesn't matter if you mix them.

One exception: to get the steering tiller / rudder blending action offered by FSUIPC, both axes should be assigned "direct" and both calibrated. It may work the other way, but it is more problematic.

Pete

 

 

Pete