December 1, 20241 yr Somehow or other I've managed to lose full travel on my TM Warthog throttle. I get full throttle, but can't get back to full idle - it jumps (and stays) at around 30%. None of the below have fixed it. 1) Checked Windows hardware settings. I'm seeing full/normal travel there. 2) Unplugged/reinserted the USB cable for the throttle - with and without restarting/rebooting. 3) Deleted the throttle axis assignments then re-added them. 4) Tried setting up various sensitivity/deadzone settings. Is there any way to force an axis reset and/or recalibration? Back in the old/pre-cloud days, I think there was a config file you could fiddle with. Is that possible in 2024? Help! ;) Edited December 1, 20241 yr by Adamski_NZ
December 1, 20241 yr Flag your topic as MSFS2024 CPU Ryzen 7800X 3D RAM 32GB Corsair VENGEANCE DDR5 6000MHz GPU GEFORCE RTX 4090 Monitor AOC AGON AG352UCG UltraWide G-Sync @ 3440x1440 Internal Storage 1TB NVMe PCIe SSD External Storage Three 4Tb HDs
December 1, 20241 yr Hi Adam Is it in all aircraft? I ask this because one of mine has no animation. However it is actually working but simply no moment in the cockpit. All other aircraft seam to work fine. Good to hear from you again. I may give you a call later and we can compare notes. best wishes. Bob
December 1, 20241 yr Author 1 hour ago, rlaycock said: Is it in all aircraft? I ask this because one of mine has no animation. However it is actually working but simply no moment in the cockpit. All other aircraft seam to work fine. Good to hear from you again. I may give you a call later and we can compare notes. Hi Bob! Yes - it's a problem in all aircraft. The throttle animates OK in the cockpit, but the circle/blob thing in controller settings never moves. All was fine until I got some weird USB resources error, so I moved some of my cables around. That error went away - and all my controllers (stick, throttle, rudder etc.) are recognised in both Windows and MSFS. However - MSFS seems to have lost the ability to recognise the full range of throttle input values. I'll see iof FSUIPC can sort it ... UPDATE: It appears that the FSUIPC Beta causes this when running. As soon as I close/quit it, everything goes back to normal. The problem is that I need to run FSUIPC when using APL ("A Pilot's Life") ... so it looks like I'll need to duplicate my MSFS Throttle Profile and clear the throttles axes - then let FSUIPC inject the inputs. Early days, eh? Edited December 1, 20241 yr by Adamski_NZ
Create an account or sign in to comment