Throttle 2 Axis Not Working Properly

[iflygary]

Hello, I suddenly started encountering problems with FSUIPC 7 Throttle 2 axis.  I've done everything I can possibly imagine. I've reinstalled MSFS thinking it may have been the issue.  I've reinstalled FSUIPC 7 twice and the issue still persists.  The throttle 2 axis is no longer stable. It either advances on its own while idling, or when at full throttle, it will retard fully.  I am using the latest version 7.4.12a.  I have attached my ini as well.

FSUIPC7.ini

[John Dowson]

Please also attach your FSUI{C7.log file when attaching your FFSUIPC7.ini file, as I need to see basic information, such as which aircraft you are using...

Your FSUIPC7.ini file is pretty empty, and shows that you only have a few axis assigned, and only for use with one specific aircraft ('Black Square B60 Duke N43DH'):

Quote

0=BX,256,D,9,0,0,0    -{ DIRECT: Throttle1 }-
1=BY,256,D,10,0,0,0    -{ DIRECT: Throttle2 }-
2=BZ,256,D,17,0,0,0    -{ DIRECT: PropPitch1 }-
3=DX,256,D,1,0,0,0    -{ DIRECT: Aileron }-
4=DY,256,D,2,0,0,0    -{ DIRECT: Elevator }-
5=DU,256,D,18,0,0,0    -{ DIRECT: PropPitch2 }-

You have also assigned using 'send direct to FSUIPC calibration'  but have not calibrated your assignments. If assigning with this, you should also calibrate your assignments.

Please also check your MSFS assignments. If assigning in FSUIPC, you need to make sure that the same axis/button is not assigned in MSFS. Best to create an empty profile for your controllers in MSFS if assigning in FSUIPC.

Any further questions/issues, please attached both your .ini and .log files, and activate logging in FSUIPC to show your issue (i.e. for problems with axis assignments, you should activate logging for Axes Controls).

John

[iflygary]

On 5/26/2024 at 6:06 AM, John Dowson said:

Please also attach your FSUI{C7.log file when attaching your FFSUIPC7.ini file, as I need to see basic information, such as which aircraft you are using...

Your FSUIPC7.ini file is pretty empty, and shows that you only have a few axis assigned, and only for use with one specific aircraft ('Black Square B60 Duke N43DH'):

You have also assigned using 'send direct to FSUIPC calibration'  but have not calibrated your assignments. If assigning with this, you should also calibrate your assignments.

Please also check your MSFS assignments. If assigning in FSUIPC, you need to make sure that the same axis/button is not assigned in MSFS. Best to create an empty profile for your controllers in MSFS if assigning in FSUIPC.

Any further questions/issues, please attached both your .ini and .log files, and activate logging in FSUIPC to show your issue (i.e. for problems with axis assignments, you should activate logging for Axes Controls).

John

Hello,

The issue seems to still persists.  I cannot fly any of the twin aircraft due to Throttle 2 being so unstable.  I have attached both files for you review.

 

Kind regards,

Gary

FSUIPC7.ini FSUIPC7.log

[John Dowson]

That is a completely different ini file from the one you originally posted!
The ini file now shows that some of your device GUIDs have changed, and rather than fix this issue you have then re-assigned to the new joy letters:

Quote

A=Saitek Pro Flight Yoke << MISSING JOYSTICK >>
A.GUID={1EEF6B30-95E3-11E5-8004-444553540000}
B=Saitek Pro Flight Rudder Pedals << MISSING JOYSTICK >>
B.GUID={1EEF6B30-95E3-11E5-8003-444553540000}
C=T.Flight Hotas X << MISSING JOYSTICK >>
C.GUID={1EEF6B30-95E3-11E5-8001-444553540000}
D=Saitek Pro Flight Quadrant << MISSING JOYSTICK >>
D.GUID={1EEF6B30-95E3-11E5-8005-444553540000}

You are also NOT using substrings for your aircraft profiles - this can cause issues with the assignments not being loaded when using the same aircraft with a different livery. You should use substrings for your aircraft profile names.

The aircraft you are using (Aircraft="Black Square TBM 850 N851TB") does not match any profile, so will be using your general profile sections, so for axes it is using the [Axes] section. You have no assignments to a throttle 2 axis in your general profile, just to the Throttle control and on multiple controllers (A,C, D and G) although only one of these exists (G - Saitek Pro Flight Quadrant). The Throttle control should control the throttle for all engines - is this not the case? Why do you think the throttle 2 axis is not working, when you are not assigning to this?

I don't understand how your ini file got into such a mess, but I will try and correct it and post an updated version later today  for you to try - don't have time just now.

John

[John Dowson]

I have corrected what I can - please download and try the attached ini file.

There are still some issues that you need to sort out:

1. You have two profiles for the Skymaster:

Quote

[Profile.Skymaster]
1=Carenado C337H Skymaster II N79252
2=Carenado c337 Skymaster 1975 Retro
3=Carenado c337 Skymaster Don't Shoot
4=Carenado C337H Skymaster II N6276K
...
[Profile.Carenado skymaster]
1=Carenado C337H Skymaster II N5JD
2=Carenado c337 Skymaster N2QD
3=Carenado C337H Skymaster II VH-SBZ
4=Cessna 337 Skymaster Westpac VH-SBZ
 

Do you really need different profiles for the same aircraft with different liveries? Take a look at those profiles and decide which one to keep, then delete all of the profile sections for the other profile. Then corrrect the aircraft in the profile section, i.e. either:

Quote

[Profile.Skymaster]
1=Carenado C337
2=Cessna 337 Skymaster

or

Quote

[Profile.Carenado skymaster]
1=Carenado C337
2=Cessna 337 Skymaster

Or, if you want to keep the two different profiles, maybe it should be a different profile for the Cessna 337 to the Carenado, e.g.:

Quote

[Profile.Skymaster]
1=Cessna 337 Skymaster 
...
[Profile.Carenado skymaster]
1=Carenado C337

? It is up to you to decide, but it seems strange having the same aircraft with different liveries assigned to different profiles - different liveries should not affect the aircraft controls and so you don't need to use a different profile for a different livery.

2. Your general [Axis] section has the same axis assigned to multiple controllers/devices:

Quote

0=BX,256,D,7,0,0,0    -{ DIRECT: LeftBrake }-
1=BY,256,D,8,0,0,0    -{ DIRECT: RightBrake }-
2=BR,256,D,3,0,0,0    -{ DIRECT: Rudder }-
3=AX,256,D,1,0,0,0    -{ DIRECT: Aileron }-
4=AY,256,D,2,0,0,0    -{ DIRECT: Elevator }-
5=AZ,256,D,4,0,0,0    -{ DIRECT: Throttle }-
6=AU,256,D,18,0,0,0    -{ DIRECT: PropPitch2 }-
7=AV,256,D,15,0,0,0    -{ DIRECT: Mixture3 }-
8=CX,256,D,1,0,0,0    -{ DIRECT: Aileron }-
9=CY,256,D,2,0,0,0    -{ DIRECT: Elevator }-
10=CZ,256,D,4,0,0,0    -{ DIRECT: Throttle }-
11=DX,256,D,4,0,0,0    -{ DIRECT: Throttle }-
12=DY,256,D,5,0,0,0    -{ DIRECT: PropPitch }-
13=DZ,256,D,6,0,0,0    -{ DIRECT: Mixture }-

You have aileron, elevator and throttle all assigned to device A (Saitek Pro Flight Yoke) and C (T.Flight Hotas X), and the throttle also assigned to D (Saitek Pro Flight Quadrant). Having the main flight axes assigned to multiple controllers can cause issues, as the axis position can be sent from both controllers, causing the axis to jump. Revise those assignments and remove the ones not needed - just assign  one axis to each of the main flight axes (aileron, elevator, throttle, left brake, right brake, rudder, Mixture, PropPitch) to avoid problems.

So, please revise the above, make the necessary changes to your ini file and try again., Any issues, please re-attach both your FSUIPC7.log and FSUIPC7.ini files and describe the issue.

John

FSUIPC7.ini

[iflygary]

John,

Thank you so much. All is working fine now. Sorry about the mess I created but is there something I am doing wrong?  Every time I download a new aircraft livery, FSUIPC doesn't work for the livery.  I then check the profile specific box and then choose "new based upon" and will assign it to whatever aircraft is already assigned in FSUIPC.  Should I handle things differently moving forward??? I don't want to create additional problems moving forward.   Also regarding the T. Flight Hotas X.  I use it whenever I am flying an aircraft with a stick. How should I handle having multiple controllers?

 

Kind regards,

Gary

[John Dowson]

10 hours ago, iflygary said:

Every time I download a new aircraft livery, FSUIPC doesn't work for the livery.  I then check the profile specific box and then choose "new based upon" and will assign it to whatever aircraft is already assigned in FSUIPC.  Should I handle things differently moving forward???

Yes - you should assign it to the same profile (it is the same aircraft!) and not create a new one. Better still, once you have created a profile, it is always a good idea to open your FSUIPC7.ini and change the aircraft name just added to the profile to be a substring of the aircraft name that matches all aircraft, regardless of liveries. I have done this now for yo now, except for the Skymaster profiles which you need to sort out yourself. Once this is done, whenever you create a new profile or add an aircraft to an exisiting profile, get into the habit of then editing the aircraft name in the profile and shorten it to a string that matches the aircraft you want to capture in the profile.

You can also use the ini parameter UseAirLocForProfiles which changes the way aircraft are matched to profiles. See the Advanced User guide for details. If you switch to using this method, you will have to redo all your profile mappings (NOT the profiles themselves). I can help if you want to try this.

10 hours ago, iflygary said:

Also regarding the T. Flight Hotas X.  I use it whenever I am flying an aircraft with a stick. How should I handle having multiple controllers?

By using profiles. All axes assignments are profile specific, so aircraft with a stick should use a profile (maybe the same one, maybe there are a few different stick-profiles) with the stick assigned to the aircraft axes, and the other profiles would use the yoke. You can also assign the "other" device's axes to something else, or leave them unassigned, but just don't assign them to the same aircraft axes (elevator, aileron, throttle, mixture, prop pitch, rudder, left/right brake). 

Cheers,

John

[iflygary]

10 hours ago, John Dowson said:

Yes - you should assign it to the same profile (it is the same aircraft!) and not create a new one. Better still, once you have created a profile, it is always a good idea to open your FSUIPC7.ini and change the aircraft name just added to the profile to be a substring of the aircraft name that matches all aircraft, regardless of liveries. I have done this now for yo now, except for the Skymaster profiles which you need to sort out yourself. Once this is done, whenever you create a new profile or add an aircraft to an exisiting profile, get into the habit of then editing the aircraft name in the profile and shorten it to a string that matches the aircraft you want to capture in the profile.

You can also use the ini parameter UseAirLocForProfiles which changes the way aircraft are matched to profiles. See the Advanced User guide for details. If you switch to using this method, you will have to redo all your profile mappings (NOT the profiles themselves). I can help if you want to try this.

By using profiles. All axes assignments are profile specific, so aircraft with a stick should use a profile (maybe the same one, maybe there are a few different stick-profiles) with the stick assigned to the aircraft axes, and the other profiles would use the yoke. You can also assign the "other" device's axes to something else, or leave them unassigned, but just don't assign them to the same aircraft axes (elevator, aileron, throttle, mixture, prop pitch, rudder, left/right brake). 

Cheers,

John

Thank you so much for your full explanation! It's well appreciated. I now realize as opposed to creating so many profiles a better way of doing things would be "twin engine profile" or "stick profile".  This makes a lot more sense now. 

Kind regards.

Gary

Edited May 29 by iflygary
left out a phrase

[John Dowson]

11 hours ago, iflygary said:

I now realize as opposed to creating so many profiles a better way of doing things would be "twin engine profile" or "stick profile".  This makes a lot more sense now. 

Yes, that used to be the best way to assign. However, as many aircraft in MSFS, especially add-ons, use lvars, hvars, input events or a combination of all three via calc code/presets, and all of these are aircraft specific, you will probably find that you need a specific profile for many aircraft. It is still useful to initially start with profiles as you say, but if you find you need to use an aircraft-specific control for one function, you can then create a specific profile for that aircraft.

John