rvakkeren Posted August 18, 2014 Report Share Posted August 18, 2014 Hi there, A few days ago I noticed that after a long haul flight that my joystick was disabled. I found out soon enough this was because of Win8 and that it could be solved easily by using FSUIPC and setting up the controls manually. Once I did, I noticed that if I move my thrust lever (I'm the owner of an Thrustmaster T.Flight Hotas-X), that is just snaps to 100% directly. So it's ether 0% thrust, or 100%. Has anyone here experienced the same problem or does anyone got a solution for this? Thanks in advance. Kind regards, rvakkeren Link to comment Share on other sites More sharing options...
Pete Dowson Posted August 18, 2014 Report Share Posted August 18, 2014 A few days ago I noticed that after a long haul flight that my joystick was disabled. I found out soon enough this was because of Win8 and that it could be solved easily by using FSUIPC and setting up the controls manually. I've seen folks say this, but I've also seen folks say the opposite. I nkow of no reason why FSUIPC assignment would fix any Win8 problem, though. Once I did, I noticed that if I move my thrust lever (I'm the owner of an Thrustmaster T.Flight Hotas-X), that is just snaps to 100% directly. So it's ether 0% thrust, or 100%. Have you calibrated in Windows first? Did you calibrate in FSUIPC? This action is almost always a result of the device being categorised in the Registry as a "digital" control rather than "analogue". You might need to go to a Thrustmaster support website for an answer -- it will likely be a Registry patch. Pete Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now