T16000M again…
-
I, for the life of me, can’t seem to get a reliable set of controls working for the T16. I bought this thing because it was cheapish and had everything I needed on it. Now, I’m in a war with TARGET and BMS to try and get everything set up. I have tried sbelcl’s script, and it seems that a couple of functions are missing or broken. I don’t know if anyone else is experiencing this, though. Is his script the only reliable one out there, or does someone have something else? Also, if I wanted to edit the key commands set with a TARGET script/BMS keyfile combo, where do I edit them? I don’t want to wage war with this thing trying to get it to work, I just want to fly :(.
P.S. I’m running the latest version of BMS. -
Just got one myself and am patiently waiting for that idiots guide to appear either here or on you tube. Not sure I am ready to start changing, adding, deleting code just yet but feel that I am going to have to as I am not sure that effectively mapping the 1600 HOTAS can be done without doing it.
-
Bump-does no one have a reliable way to set this stick up?
-
I’m in the same boat; just started with BMS and I have got this stick as I thought it would be good for future games and support as well. So far I’ve only been able to assign the axis the way I want. This TARGET script editing is confusing as hell and makes it an even steeper learning curve as it already is; without even setting foot in a virtual cockpit…
I want to recreate the various controls as close as I can to the original Cougar; however I’ve run into a couple of hickups. The POV hat on my stick works just fine; the one on my throttle isn’t recognized by BMS.
-
see here : https://www.benchmarksims.org/forum/showthread.php?29319-Thrustmaster-T16000-FCS
and also here : https://www.benchmarksims.org/forum/showthread.php?30303-Another-TM16000-questionHope that helps!
-
see here : https://www.benchmarksims.org/forum/showthread.php?29319-Thrustmaster-T16000-FCS
and also here : https://www.benchmarksims.org/forum/showthread.php?30303-Another-TM16000-questionHope that helps!
Thank you. I gave it a go, had some trouble with it and decided to just try it from scratch with the TARGET GUI software.
Currently I’m at the point where all my keys and necessary axis are bound the way I like them using just the GUI software (still got buttons to spare on the foot of my stick). So far so good. Basically what I’ve done so far is creating events in the software that create keyboard shortcuts sent to BMS.Now I noticed layers when I was setting up my basic controls in the program. They are seperated two (I,O) by three (U,M,D). I honestly have no idea what they mean. If I had to make a guess I think they are something like when you hold down your pinkie switch you can get to another layer of controls. If this is correct I’d like to know how I’d be able to access those ‘shifted’ functions. I also could be completely dead wrong
-
I’m using the guts of one of these I rigged into some actual hardware, can’t really say, I’m using the stock throttle assembly…
My best hope is that thrustmaster like CH sometime, makes that hat toggle through control panel to a digital input instead. The quickest way, is to just sacrifice something, and set up everything else DX in game.TARGET IS A POS, and it is FUBAR…it will reassign axis, and basically be broken every other time.
All that we need is that Throttle and stick to have a driver update which adds digital toggle functionality to the POV hats. if anyone has any pull with those guys tell them, CH did this for this reason specifically. Think of a HOSAS or a YOKE…this isn’t going to go away.
that thrustmaster throttle is absolutely by far the best in it’s range, and I would say, pushes those above it pretty good. This is an absolute ball breaker
-
I learned TARGET in and out, and tried for 2 days. Frankly it’s crap…the only way to go about it is very limiting as far as tertiary and non thrustmaster controls. I use analog inputs for trim, in any configuration I tried i run out of axis even with target and the script will not run consistently, EX. it works once and then will not work again. I’ve got a plan using some 3rd party software and some modifications.
just want to try and save someone time in the future, if you use the serial port from the 16000m to your rudder pedals the axis will duplicate, if you plug the pedals in separate with USB serial adapter it wont do that. I thought I had fixed it, but then I ran into the problem of target just sucking in general…
I am happy that the 16000m works great in other games, I will be using it as a left hand stick in the future, I am going to build a second flight chair with all digital buttons and 12 bit analog axis so as to avoid anymore of these problems and to simulate the legacy fleet as best as possible. Probably going to go with my own creations, I’m really unimpressed with everything available, be it software or hardware shortcomings.
-
I mapped everything on my FCS 16000 in BMS without using Target. Why are you using Target?
-
You’re using the T.16000m and TWCS? How are you using the 8way hat on the throttle and do you have any shifted commands for any of the buttons?
-
I mapped everything on my FCS 16000 in BMS without using Target. Why are you using Target?
I did as well. I used the keyfile generator, I think. If it wasn’t that, it was some sort of spread sheet. I used the generic controller section of it.
-
Bump-does no one have a reliable way to set this stick up?
Hi, I am trying to build up a reference setup for all the BMS community; if you’d like to stay up to date please follow this thread. (I plan to release the first really working version in 2-3 weeks… real, not Falcon’s :D)
I want to recreate the various controls as close as I can to the original Cougar; however I’ve run into a couple of hickups. The POV hat on my stick works just fine; the one on my throttle isn’t recognized by BMS.
This is not BMS but DX limit: you can have more than one POV hat on the same device, but you can’t use POV hats on different devices; DX only recognizes hats on the device marked as primary.
I did as well. I used the keyfile generator, I think. If it wasn’t that, it was some sort of spread sheet. I used the generic controller section of it.
Good to know, can you please confirm you can effectively map both POV hats to sim callbacks?
This would destroy my understanding of DX limits as expressed above, but would be more than welcome and I will no doubt use the tool and see how it makes the whole thing work. :headb:
