March 9, 20224 yr I am still experiencing issues with my throttle when used on the Hawk T1 following the latest update. Previously, as with most of my other planes my Thrustmaster Hotas Throttle was bound to the T1 Hawk via FSUIPC to the throttle axis, and all worked fine. Now it is moving to full power and then 'automatically' going back to idle, and it is only with further movement of the throttle that I get it to re-engage, the bottom line is that I am no longer in control of my thrust with my throttle. I posted on this subject before, and someone kindly suggested that I now needed to bind the throttle to throttle axis 1 - this I have tried, both using FSUIPC and the MSFS control options - and neither work for me. I am obviously doing something wrong, but cannot figure it out. Any thoughts or suggestions? Just has another attempt to resolve the issue. If I bind the Thrustmaster Hotas Throttle to the Throttle 1 axis via MSFS2020 control options - that works until I move it to 'full power' when the thrust just cuts out. I have cleared all other non relevant bindings, and have the lastest MSFS2020 and windows updates Edited March 9, 20224 yr by SquadronLeader George Westwell
March 9, 20224 yr Hi Just booted up my T1 Hawk, using the Honeycomb throttle quadrant, and all seems normal here. My throttle, like yours, is 'Throttle Axis 1' and then I personally have the switch below the throttle detent set for 'Engine Autostop'. As long as I don't go below the detent, then the throttle will spool up to full power and back normally. However I and a number of other users have suffered a few issues relating to the bindings following SU8 on a number of aircraft. We are not sure exactly what the cause is, but it seems that there have been other HOTAS controls set up for the same action - and therefore you end up with a conflict of commands. In my case it was rudder (but other users have had other clashes) - my previous bindings had the rudder assigned to my Thrustmaster rudder bar, but SU8 had added a command too to the thrustmaster joystick. So my rudder bar said 'turn' and the twist stick said 'stay!' The result was that my rudder didn't work. The fix was easy - in the Controls section, I just selected each of the HOTAS controls in turn and searched for the command - and when I found the duplicate simply deleted it. The other way is to switch to each 'Default' control bindings profile and just recreate your custom ones. So it is entirely possible that there is another HOTAS command set for throttle which is causing the problem. If so, you should be able to find the clash as above. If you are using a separate throttle block, it is possible that your joystick slider has also reset itself with SU8 to throttle and is causing the clash. If it is this, can you let us all know as there is a bug logged that hasn't yet got enough votes to go onto ASOBO's 'to be actioned' list... Ryzen 7 9800x3D @5.2GHz; ASUS X670-P Motherboard; nVidia 4080 (factory o/c); 32G 5600MHz DDR5 SDRAM; Pimax Crystal Light VR Headset; Quest 3 VR Headset
Archived
This topic is now archived and is closed to further replies.