Problems with the throttle logic
-
I have the Thrustmaster Warthog HOTAS set up and am trying to understand the aircraft with my hardware. As it currently stands, it is unflyable for me, as the idle is too high. I have calibrated my equipment correctly. I can start the engine (though it does not always work as planned), but it automatically idles at around 70%. If I move the throttle axis forward, the thrust reduces to nearly 60%, without any movement in the levers in sim being registered, particularly if I pump the throttle at the lower end of travel. Then, once I reach the hardware throttle setting that the sim thinks the idle position to be (around 70% again), thrust then begins to increase.
This means that I can never get to the correct idle, so the aircraft will not taxi easily. I am constantly on the brakes to avoid the aircraft from lurching off and taxiing at idle over 30 Kts... landing is a laugh to say the least...
Any tips as to how I should go about this? It is rather frustrating, because all the videos I see have the aircraft idling lower than 70% N1, more like 60%...
Andrew
-
I have the Warthog as well and suffer the same problem but it is not the hardware - it's the same for all multi-throttle setups. You have the axes set for 'throttle 1' and 'throttle 2'. You need to have one axis set only, and set for 'throttle' if I remember rightly. It's a right pain having to reset the assignments every time and I'm still hoping there will be a fix for this, but meantime that should at least have you moving in the right direction.
Cheers,
Paul. -
Thank you for your input. It is interesting that you mention the multi-throttle issue. I removed all assignments to hardware (I have a virtualfly TQ6+ as well which is currently unassigned in the profile I created for the Hawk) and checked the throttle’s idle position without hardware assignment, which was also 70%. Recalibrating did not help, nor did single assignment of one of the levers to throttle instead of throttle 1. All I can try is to separate the two levers from each other by releasing the interconnect and seeing if the assignment of throttle to one lever and only that lever moving will help. That certainly did not work on the TQ6+, as I saw the same idle value of 70% N1.
Could you try something for me? Unassign any hardware throttle axis and see what the idle value is when using the mouse. If it is 70%, then it is the aircraft and not the system...
Andrew
-
Hey Paul,
In XPlane 11, you can set up profiles for controllers, so you should be able to assign hardware buttons and axes in an aircraft-specific fashion. That is what I have done so far, as I have the Dreamfoil Embraer 110 that uses my TQ6+ almost exclusively and the Warthog throttle set is not used there at all... This was one of the reasons I was ready to try out XPlane, as I would have missed this P3D FSUIPC functionality too much otherwise. I use this capability in FSUIPC on the P3D platform exclusively.
Andrew
-
Aah, I see we're at crossed purposes (or sims) here! I saw the post about the throttle problem in the notifications and answered it thinking it was P3D, because that is where I have the problem (and it seems virtually identical to what you describe). I don't have X-plane, so can't go any further in helping you figure this out but perhaps if you drop a support ticket off you may get some more substantial help!
Cheers,
Paul. -
I took a couple of screenshots and can include a video of the behaviour I experience when I am at idle and move the thrust lever back and forth in the first 5-10mm of its travel (hardware Warthog).
The first screenshot depicts the throttle lever in cockpit, engine started and at idle.
The second screenshot is the corresponding N1 setting for idle thrust. Am I the only one experiencing this issue? Or could it be something to do with V1.2?
Let me know if you are interested in seeing the video and I can upload it somewhere...
Andrew
-
Just to add that I had a response in the x-plane.org forum from one of the Thranda team, who made a suggestion. It seems the throttle gate logic is causing me a problem, maybe I can reduce the idle in the acf file.
Whatever I try , I can report back.
A