Help w/ T1600 stick and throttle
-
I just purchased T1600 stick and throttle. I cant use them both in the game at the same time. Could someone help me with this problem? Thanks in advance
-
I’m just getting started myself. Took about an hour to figure it out. I loaded the drivers for windows first. Launched BMS, setup, controllers, make sure you see, keyboard, joystick and throttle in pull down. Leave it on keyboard. Pick advanced, flight controls, change the throtle from keyboard to twcs and pick the axis for back and forth throttle movement. For pitch and roll deadzone choose the t16000 and it’s correct axis. If your not sue what axis to choose, go out of the advanced menu back to the previous menu, select the controller to set, go to the advanced menu and it will tell you what it is using. I wrote my down but still have a way to go. I’m trying to locate a profile that someone has already created, but no luck so far.
-
If you don’t use Target you lose the throttle POV Hat. I suggest you try the target script of sbelcl here :
https://www.benchmarksims.org/forum/showthread.php?29319-Thrustmaster-T16000-FCS
It’s a good starting point. I am testing a Target profile that i made. When it is done i’ll put it online
-
I’m not very computer savvy. Still struggling. I just want to fly. I didn’t think upgrading stick and adding a throttle would be so difficult.
-
I know, been there too! if you want to use it without using Target, you set your controller as T16000 stick in the BMS setup window, then you go to advanced and choose the axes for avionics, etc… the thing is, BMS tend to assign the axes in a messy way, so what i do is select Keyboard for every axe (to have a “blank” profile), then i can choose the axes. Hope that helps?
sorry for my bad english ^^ -
Edited as fixed own problem.
(I was having issues getting the TWCS throttle to map - discovered that I was mapping “slider” instead of “Z axis” on the TWCS and then wondering why it wasn’t working….)
-
is there a fast and dirty low drag way to make BMS see the secondary POV hat as a digital input not a DX one? something in the software knows it’s a coolie POV. TARGET SUCKS, I desire to just subvert the nonsense. it’s really on windows, the COUGAR and the WARTHOG had this problem, it’s not BMS, it’s stupid windows. This is a bummer right now- keyfile edits are a drag and I’m too lazy to deal with all that.
someone rewrite that 3 or 4 weeks from now so it stops doing that weirdo pov behavior. Seems like a symptom many experience.
