Throttle 4 Not Working

[JPL19]

I have dual throttle hardware, with a center detent.  If I un-check Auto-stop power levers at detent throttle 4 stops working.  Throttle 3 continues to work fine as a "Paddle with Detent".

This is not a hardware issue.  Either physical throttle will work fine if assigned to Throttle 3, or 5.  Neither will work if assigned to Throttle 4. 

Combinations tried for Physical axis:

• Physical Axis:
• A (left) - B (right) 
•    3       - 4        (3 works, 4 does not}
•    4       - 3        (4 doesn't work, 3 does)
•    5      - Null    (5 works)
•   Null    - 5        (5 works)
• 4 never works in any combination or even when it is only one axis assigned. 
• There is no other throttle axis assigned anywhere
• No response curves, etc per manual -  You should observe the words, "Add Response Curve" is correctly showing.

If I re-check Auto-stop power levers at detent 4 works in that mode, but I want to use it as Dual Paddles with Detents.

I uninstalled 2.0 and then re-installed 2.01 , rebooted, restarted, and yes I read the new manual.  Tried 4 blade oem and 5 blade GNS.

Joe

[tkyler]

Maybe its time to expand my explanation of how this works a bit...in case there's some hardware bug with Laminar when swapping a bunch of assignments dynamically we don't know about.  I'll even drop my pants and risk embarassment to show my comittment to fixing this  Reference my code for handling THROTTLE 4 (right side)

When you assign an axis to anything in that pull down list...throttle...throttle 1, prop 2..whatever.  Us developers then access a  specific dataref corresponsing to that axis mapping.  Laminar gives us this mapping. The dataref is even called, "joy_mapped_axis_avail[n]"  where n is an index corresponding to the assignment type(throttle/prop, etc).  So if you, for example, assign a lever to "throttle 4", then that means index[24] (24 in Lua, 23 in X-Plane).  So the code above says

If a user moves axis [23] (remember Lua is +1...so 24 here means 23 in X-Plane).......which is the THROTTLE 4 axis,   THEN.....has the user checked the 'auto stop at detent" preference.   If they have, then run the auto-stop at detent code and ignore the detent ratio.  ELSE.....if the 'auto stop at detent' is UNCHECKED, then the user either wants LEGACY behavior, or they have a physical (or desire a virtual) detent. ...so lets now check a few more things.  IF the user sets a power detent ratio of 0, then they want LEGACY behavior, BUT if the power detent ratio is non-zero, then they want to simualte a detent. ..and the final step is I simply read the joystick value between 0 and 1...and then write to the manip value (verify by mouse usage) that same value, between 0 and 1...and that's it. I simply read the joystick and drive the mouse manip.  This is why I ask folks if it works with the mouse.  If it does, then we have either a hardware mapping issue, or some kind of bug in Laminar code we don't know about.

The way I would debug this is use the free Dataref Editor plugin and look at the THROTTLE 4 dataref...and if, when you move it...it goes to 1 AND the value it gives me is non-zero and also moves with the axis....then I expect the code above to work....and it always does for me, not matter how many times I test it....BUT a caveat.

When I dev, I may change hardware assignments 50 times a day...set a lever to throttle 3, then 4, then brakes, then yaw....just to make sure it always works no matter which hardware lever is assign to whatever...I totally randomize my lever assignments when testing....AND I do so without rebooting X-Plane....and there are times when something won't work at some point and it simply does not pass any sniff test and I finally have to chalk it up to some corruption of data and end up rebooting X-Plane and a LOT of times, things go back to normal.  I don't ask why in these cases...as I know switching hardware assignments so agressively could easily expose some weakness in X-Plane code that they never expected users to do, etc.

So...hopefully we're not seeing something more sinister.   God forbid your THROTTLE 4 uses some index that is NOT [23]....as that defeats the entire purpose of the mapping Laminar gives us to handle hardware.  Without verifying (via Dataref Editor Plugin) what values your joystick is changing when assigned to THROTTLE 4, I'm a bit at a loss.

I apply this exact same paradigm to all the other axes possibilities...the code is very similar between all the assignments, not just this THROTTLE 4 example. 

-TomK

 

 

 

Edited July 26, 2022 by tkyler

[Ch.Cole]

I can confirm that while both values (22 and 23 in DataRefTool) change with Auto-stop de-selected, only the left Power Lever moves. With it selected, both move. I can revert between both modes and always get the same results.

[Bulva]

... you can check my temporary solution:

 

[BobGramm]

As an additional trouble-shooting data point: using the Bravo Throttle.  I can get the Modern Throttle Mode to work just fine following the instructions exactly.  Unfortunately, I prefer the Legacy Mode because it operates the same as all other X-Plane turboprops.  Can't get the Legacy Mode to work following the instructions exactly; and the right throttle tends to not move at all.  I can get the Condition Lever to operate correctly and the simulator lever moves to the Emergency Stop position, the engine stops and the prop feathers.  Hope this helps in working out a correction.  Love the MU-2, looking forward to flying the corrected version.  Thanks.

Edited July 29, 2022 by BobGramm
Moving condition lever to Emergency Stop must be conducted only if power lever is above Flight Idle (which I did not do initially). Therefore, the only real problem is the right power lever in the Legacy Mode.

[JPL19]

On 7/26/2022 at 7:44 AM, tkyler said:

....

So...hopefully we're not seeing something more sinister.   God forbid your THROTTLE 4 uses some index that is NOT [23]....as that defeats the entire purpose of the mapping Laminar gives us to handle hardware.  Without verifying (via Dataref Editor Plugin) what values your joystick is changing when assigned to THROTTLE 4, I'm a bit at a loss.

....

I am at a loss as well - seems numerous others report the same experience.  

I also tried a totally different throttle, different brand with three different axis and none worked as Throttle 4 - all as my first post.  So not sure how it can be my throttle.

Edited July 28, 2022 by JPL19

[kdub]

On 7/28/2022 at 4:01 PM, JPL19 said:

I am at a loss as well - seems numerous others report the same experience.  

I also tried a totally different throttle, different brand with three different axis and none worked as Throttle 4 - all as my first post.  So not sure how it can be my throttle.

Same situation for me.  Using VirtualFly TQ6+.

 

kDub

[tkyler]

Sorry guys.  "pull" isn't "rotate"   typo in my lever code from cut/paste.  Fixed.  Trying to blow through all issues before the weekend!

-TomK

Edited August 3, 2022 by tkyler