Samoaboyzsamoababy Posted December 9, 2017 Posted December 9, 2017 Ok so bear with me guys, first post on this forum. I just recently bought a thrustmaster t16000m fcs. The joystick seems workingfinewith battle of Stalingrad but the throttle doesn't seem to be doing anything. does anybody know how I can go about getting my throttle to work? If you need more details you can ask, I just don't know how to explain this properly
Mitthrawnuruodo Posted December 9, 2017 Posted December 9, 2017 (edited) Welcome to the forum! A few questions to help narrow it down: Have you checked the Il-2 control settings to make sure the throttle is bound? Did you download any software from Thrustmaster for your controller? Hopefully we can get to the bottom of this without too much trouble. Edited December 9, 2017 by Mitthrawnuruodo
Samoaboyzsamoababy Posted December 9, 2017 Author Posted December 9, 2017 Welcome to the forum! A few questions to help narrow it down: Have you checked the Il-2 control settings to make sure the throttle is bound? Did you download any software from Thrustmaster for your controller? Hopefully we can get to the bottom of this without too much trouble. when I try to map the throttle it sometimes works but its not very effective. like when I go up on the throttle it doesn't detect unless I go all the way forwards, and I downloaded target gui from thrustmaster website
Mitthrawnuruodo Posted December 9, 2017 Posted December 9, 2017 Hmm If you run the configuration in TARGET and go to the 'Device Analyzer', does it show the position changing as you move the throttle?
Thad Posted December 9, 2017 Posted December 9, 2017 Salutations, The FCS Throttle does indeed work with IL2. There is no need for their TARGET software. Simply follow the installation instructions and calibrate it in Windows. Then set the buttons up in the game as you desire. See link below. https://forum.il2sturmovik.com/topic/30758-recommended-button-maps-t160000m/
Horna Posted December 9, 2017 Posted December 9, 2017 I had similar problem with target software just week ago, stick worked, throttle not. I spent few hours fighting with the damned software until I tried a different USB port and after changing the port from front panel to back panel, it started working I hope this helps.
Sokol1 Posted December 9, 2017 Posted December 9, 2017 (edited) when I try to map the throttle it sometimes works but its not very effective. like when I go up on the throttle it doesn't detect unless I go all the way forwards, and I downloaded target gui from thrustmaster website This is normal, some controller axis are only detect backward in controls (Key mapping), so after assign in that way click in the curved arrow ahead axis name for invert then, the inverted arrow icon became highlight and throttle axis will work correct. And don't use TARGET if you don't know well how use, will more hurt than help. Keymappers (TARGET and cia) between controllers (joy, throttle...) and games can be a convenience, but is not a necessity. In this game map josytick/throttle axes/buttons direct in game controls is sufficient. Edited December 9, 2017 by Sokol1
Samoaboyzsamoababy Posted December 10, 2017 Author Posted December 10, 2017 just an update: I uninstalled target but I still have the same issue. the throttle will be mapped to some weird controls, and the joystick wont control the plane. I don't know how to fix this. if anyone can guide me step by step how to install a hotas setup that would be much appreciated. Hmm If you run the configuration in TARGET and go to the 'Device Analyzer', does it show the position changing as you move the throttle? for some configurations it did but others it didn't work
Sokol1 Posted December 10, 2017 Posted December 10, 2017 the throttle will be mapped to some weird controls, and the joystick wont control the plane. This is normal, this game don't assign controls for joystick/throttle axes and buttons automatically you need do this manually in Keybinds. Look at this topic for how other guys assign T.16000M FCS and TWCS buttons: https://forum.il2sturmovik.com/topic/30758-recommended-button-maps-t160000m/?hl=%2Bthrustmaster+%2Btwcs&do=findComment&comment=504304 But before all assure that Throttle are working correct in Windows. Press and hold Wind Key, press R key. In the box type: joy.cpl Hit Enter and in the new window double click over throltle name to access the test screen, move axis and press buttons and see in the screen match what you do. If all are OK go for game controls and start assign and test axes and buttons.
Samoaboyzsamoababy Posted December 10, 2017 Author Posted December 10, 2017 This is normal, this game don't assign controls for joystick/throttle axes and buttons automatically you need do this manually in Keybinds. Look at this topic for how other guys assign T.16000M FCS and TWCS buttons: https://forum.il2sturmovik.com/topic/30758-recommended-button-maps-t160000m/?hl=%2Bthrustmaster+%2Btwcs&do=findComment&comment=504304 But before all assure that Throttle are working correct in Windows. Press and hold Wind Key, press R key. In the box type: joy.cpl Hit Enter and in the new window double click over throltle name to access the test screen, move axis and press buttons and see in the screen match what you do. If all are OK go for game controls and start assign and test axes and buttons. Oh okay thank you guys. so basically all I have to do is map them myself? for some reason I assumed it would be mapped for me but that makes sense
Mitthrawnuruodo Posted December 11, 2017 Posted December 11, 2017 Yes, it is usually necessary to map some axes yourself.
SvAF/F19_CoNa Posted December 25, 2017 Posted December 25, 2017 (edited) I’m having issues with my warthog throttle and keymapping. In the settings, it detects throttle and any key assigned to any switch or button. But once flying neither of then works. The joystick axis and buttons works as it should though. I have tested both with the TH software installed and without. If i go to DCS everything works as it should. Any ideas what to do? Edit:Found the issue. The throttle did not like some of my other USB devices. Removing them and deleting the input folder resolved the issue. Edited December 25, 2017 by SvAF/F19_CoNa
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