![]() ![]() ![]() This version might work better on Windows 10: Release v2.2.1.1 Īs declaimer: while I understand Github to be generally safe, I’m hardly an expert in these thing. I personally use this version with Windows 11: Release v2.1.9.1 Possibly also try it in some different game to see if it works, if you don’t have one aside MSFS there are games which are free to use in the basic version around like DCS, Rise of Flight or Warthunder. At very least, check the Windows USB game controller interface (it’s clumsily tucked away these days, run search for USB game controllers or joy.cpl). This is not exactly what I referred to and I don’t think anyone should need to buy new controller to work around what might be an issue in the game, rather:įirst of all ensure your controller is working correctly otherwise. I have a lot of money (to me) tied up so that I can fly and I don’t do any other gaming… If purchasing a new (different) hotas would solve the problem for sure I’d go that way but there is no guarantee that it would work. Lastly, make sure your pedal toe brakes are assigned to right brake axis and left brake axis. Consult Thrustmaster’s documentation on how to do that. As earlier there’s an afterburner detent blocking the full range of the throttle, you might want to physically disengage it as there is no such detent in typical aircraft in the game. If the throttle is “going the wrong way” then you need to check (or uncheck) the “reverse axis” tickbox in the control options, right next to the appropriate axis. You’ll probably want to bind one throttle axis to throttle 1 axis (not the 0-100%) and the other to the throttle 2 axis. You have a HOTAS style throttle intended to for a twin engine jet with an afterburner detent. The issue and hardware you are having are completely different to OP and you are kinda hijacking the thread here, so I’ll be brief. Only the last part after the quote was in reply to you, you can ignore the part before that. To clarify, my previous post was almost wholly in reply to OP. Let me know if you are interested in trying this and I can make a small guide with pictures on how to do it. ![]() I believe your HOTAS does not support the OEM’s programming software (TARGET) so you’d need to use third party one. The game would think this is coming from entirely new, different device which might bypass whatever hiccup you are experiencing. Then reinstall and try again.įailing that, as workaround you could use programming software to assign your throttle to a virtual controller axis, then bind that virtual controller axis to the MSFS throttle axis. Might want to backup the folder in any case.Įdit: On MS Store version, it seems the analogous files are held in different appdata directory: Joystick Profile Location - Steam? - #5 by hobanagerikįailing that don’t just delete that folder, but in addition: uninstall the sim delete any cache files related to the game go manually delete whatever remains of the MSFS installation folder and go manually delete whatever remains of the MSFS appdata folder. Note that this might delete your flight log information, if you care for such things. ![]() If you have the Steam version, you could go reset all your settings to default, delete all custom controller profiles, quit the sim and go delete the folder “C:\Program Files (x86)\Steam\userdata\Steam_userID#\1250410”, then reboot the sim and try again. ![]()
0 Comments
Leave a Reply. |