Throttle axis: max rpm cannot be achieved

[escaner]

I have the Huey throttle axis mapped to my left Warthog HOTAS throttle. Collective is on my right one.

 

When I move the Huey throttle axis to maximum, it will only reach about 6,000 rpm. I need to press the corresponding key to increase rpm to reach the nominal 6,600 rpm.

 

Anyone else having this problem?

[Mud]

Interesting. I'll try it out tonight.

My throttle is mapped to the right, and collective to the left.

 

What I do experience is that the rpm axis isn't picked up on a cold start until you've pressed page up / down first.

[Mud]

Just tried it with the throttle on both the left and right and mine moves the throttle all the way to the maximum without problems.

 

- Did you test your hotas throttle in Windows device manager to check if it goes to 100% there?

- Long shot but, you don't have the afterburner detent installed?

 

Best regards,

 

Mud

[escaner]

Thanks for the reply Mud, I have been further investigating the issue.

 

Looks like this only happens when I have the Thrustmaster TARGET software running, and also happens with other axes (tried with the slider). Visually, the axis is correctly registered in DCS with full travel range.

It works fine without TARGET.

 

PS: Actually, rpm keeps slowly rising and gets to 6,400 rpm within 20 seconds after reaching 6,000 rpm, but it never gets to 6,600 neither rises as fast as it should.

[PiedDroit]

I had this too on one of the axis, I just added a little deadzone at the end of the axis range (adjust "saturation X" to a value below 100, like 95 for example).

[escaner]

Thanks Pied Droit, I will try that.

 

Now I would like to visualize the actual digital values of the axis. The bug could be anywhere: TARGET, DCS or the Huey module.

[PiedDroit]

Thanks Pied Droit, I will try that.

 

Now I would like to visualize the actual digital values of the axis. The bug could be anywhere: TARGET, DCS or the Huey module.

 

You can use TARGET's Device Analyzer:

- start the profile

- start device analyzer

- main window will display the "Thrustmaster Combined" output (*)

- on the left are displayed the real hardware output values

 

(*) If "Thrustmaster Combined" is not already selected as in the picture, click on the icon on the very top left of the window, there you can select it.

 

Edited October 6, 2016 by PiedDroit

[escaner]

Thank's again, Pied Droit.

I see that the input goes all the way in the 0-16383 range, while the combined output axis only makes -32766 to +32766 out of the -32767 to +32767 range.

 

Seeing that the throttle axis in the UH-1 seems exponential instead of linear (acknowledged bug by Belsimtek years ago), maybe that last value has more importance than it would seem.

[PiedDroit]

Thank's again, Pied Droit.

I see that the input goes all the way in the 0-16383 range, while the combined output axis only makes -32766 to +32766 out of the -32767 to +32767 range.

 

Seeing that the throttle axis in the UH-1 seems exponential instead of linear (acknowledged bug by Belsimtek years ago), maybe that last value has more importance than it would seem.

 

Maybe there is some integer rounding error... It looks your stick and profile work fine (I have the same values) , try changing saturation X and see if you stii have the issue.

[escaner]

I finally found a straightforward workaround to this bug.

 

* Problem

I found this a few months ago while programming a TARGET script to support BMS start/stop: there is a bug in the SetSCurve() function in TARGET that provokes this problem. When using the TARGET GUI, it always generates a call to that function with a flat curve (pretty stupid, but it is there).

 

I contacted Thrustmaster and they replied acknowledging the problem but that they would not fix it because it "made no difference". Belsimtek does not seem to be putting any resources in the Huey anymore, so I doubt they will fix that exponential axis either.

 

 

* Workaround:

So, the obvious the solution was to make a TARGET script without that call, but I was lazy. Finally realized that actually you can convert a TARGET GUI mapping onto a TARGET Script. When editing in the TARGET GUI, below section "2. ASSIGN PARAMETERS", there is a button "VIEW SCRIPT". Just click it, try not to vomit at that elegant piece of programming that you see, remove all the lines "SetSCurve(&<whatever>, <whateverelse>, 0, 0, 0, 0, 0);" and save it as .tmc.

From now on, just run that script instead. Do not delete the original .fcf GUI mapping in case you want to make changes and redo the process whenever that happens.