Yet Another T.16000M FCS HOTAS Review and Setup
-
Glad you sorted it out.
The line reading
USB HID device with hardware id “VID_044F&PID_B687” cannot be found
seemed to indicate the TWCS Throttle wasn’t plugged in at that moment or at least not recognized as such.
I am not aware that i had to reboot at any time during installastion.
Also, you have to run the script everytime before using the throttle in BMS, whether you just rebooted or nor.The initial condition (before running the script) should be that Windows “USB Game Controllers” setup sees “T.16000M” and “TWCS Throttle” USB devices.
After running the script it should instead see “T.16000M” and “Thrustmaster Virtual Game Controller (root)”. -
Yep. That’s what I thought too. I knew the “cannot be found” message had to be pointing to the throttle. After stopping and running the script a couple times and checking the USB Game Controller panel which showed the virtual device correctly, I rebooted and it worked fine after that. I blame Windows 10 because I certainly didn’t do anything wrong.
Thanks again. This entire process made my journey to Falcon BMS relatively painless. Although, this solution for the T.160000.M is just temporary as my Warthog is shipping soon and should arrive in about 10 days (I’m in Okinawa so things take a while to get here).
-
Once again… my throttle isn’t working. The throttle control has moved back to the joystick slider. I’ve tried everything possible. Any chance that the T.16000.M being the second device is causing the throttle to move over? Here is the script output now…
Running script: C:\Users\Jody\Downloads\HOTAS\T.16000M FCS Hotas-Logic\TWCS Throttle-FalconBMS.tmc
Compile Succeeded.
Mapped plugin module “C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll”
Physical USB HID devices managed by script!
Currently plugged USB HID devices[2]:
1: “TWCS Throttle” - “USB\VID_044F&PID_B687&REV_0110”
2: “T.16000M” - “USB\VID_044F&PID_B10A&REV_0500”
USB HID device “TWCS Throttle”(USB\VID_044F&PID_B687\6&241970D9&0&4) selected
Virtual HID devices managed by script!
Connecting virtual joystick…Done
Device name set to Thrustmaster Combined
Connecting virtual keyboard…Done
Connecting virtual mouse (absolute axes)…Donemain returned 0
============================
-
Replying to myself again. I had to unplug the joystick/throttle then plug in again, compiled/ran script and it still didn’t work even though the throttle showed up second this time. Rebooting computer and running through it all again produces the same result. So very frustrating.
****** EDIT (again) ******
Had to go back into the Controllers>Advanced and select the throttle again. Problem solved againRunning script: C:\Users\Jody\Downloads\HOTAS\T.16000M FCS Hotas-Logic\TWCS Throttle-FalconBMS.tmc
Mapped plugin module “C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll”
Compile Succeeded.
Physical USB HID devices managed by script!
Currently plugged USB HID devices[2]:
1: “T.16000M” - “USB\VID_044F&PID_B10A&REV_0500”
2: “TWCS Throttle” - “USB\VID_044F&PID_B687&REV_0110”
Installing filter driver to VID_044F&PID_B687. Please Wait…Done!
USB HID device “TWCS Throttle”(USB\VID_044F&PID_B687\8&1BE45B7D&0&2) selected
Virtual HID devices managed by script!
Connecting virtual joystick…Done
Device name set to Thrustmaster Combined
Connecting virtual keyboard…Done
Connecting virtual mouse (absolute axes)…Donemain returned 0
-
Did you copy DeviceSorting.txt to FalconBMS\User\Config?
In BMS/Setup/Controllers/Controller, you should select T.16000M and never change that again!
Then set up axes as desired, selecting t16000m or virtual controller as wanted. -
Awesome work Logic! Could you recommend an alternate mapping for those of us that don’t have head tracking and need to use the POV hat for, well, POV?
-
Yep. That file is there.
Although I could have suffered through learning BMS with the T.16000.M, I boxed it up and put a new Warthog HOTAS on my desk yesterday. Only problem I have now is my mild-OCD is being triggered by a burned out light on the throttle (FLOW R). Sent a message to Thrustmaster and hope I can just replace the light inside. There are so many buttons and now I need to learn how to use them all. -
Awesome work Logic! Could you recommend an alternate mapping for those of us that don’t have head tracking and need to use the POV hat for, well, POV?
In my latest setup, i have assigned view directions to the SHIFTED TWCS castle hat as i use them with the 2D (snap) cockpit at times. (Without diagonals :?)
If this is sufficient for you i can just update the initial post with my latest setup.But you probably want to map view to the joystick POV hat? In that case it needs some modification, but stays simple to do.
Mapping the Pov hat for view is simple, just replace the appropriate section in the key file with this:#============================================================================================== SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -2 "***** 8-Way POV Hat *****" #============================================================================================== OTWViewUp 0 -1 -3 0 0X0 -1 "VIEWGEN: Rotate View Up" OTWViewUpRight 0 -1 -3 1 0X0 -1 "VIEWGEN: Rotate View Up-Right" OTWViewRight 0 -1 -3 2 0X0 -1 "VIEWGEN: Rotate View Right" OTWViewDownRight 0 -1 -3 3 0X0 -1 "VIEWGEN: Rotate View Down-Right" OTWViewDown 0 -1 -3 4 0X0 -1 "VIEWGEN: Rotate View Down" OTWViewDownLeft 0 -1 -3 5 0X0 -1 "VIEWGEN: Rotate View Down-Left" OTWViewLeft 0 -1 -3 6 0X0 -1 "VIEWGEN: Rotate View Left" OTWViewUpLeft 0 -1 -3 7 0X0 -1 "VIEWGEN: Rotate View Up-Left"
Then you need to find another place for your TMS commands of course.
-
Yep, I was thinking along those lines, was just wondering if you already had an alternate mapping scheme already set up. Although I am an original falcon player from '98, I’m still a bit of a noob to the BMS version. What is a “SHIFTED TWCS castle hat”? Also, what does the “#” denote on your layout PDF? I realize they are secondary commands for that button, but how do you activate them? Thanks again and please pardon my ignorance. Happy flying and check six!
-
What is a “SHIFTED TWCS castle hat”? Also, what does the “#” denote on your layout PDF? I realize they are secondary commands for that button, but how do you activate them?
TWCS is the throttle controller name. Castle hat is the hat that looks like a castle tower (bottom on side of TWCS). SHIFTED means secondary function, as you already figured out.
BMS allows to assign each button with two functions, one regular and one SHIFTED. The latter are the ones i marked with “#” in my layout. The SHIFT key is the one to be used (hold down) to access the secondary functions, in my layout it is the leftmost forward button of the TWCS, marked with “#DX SHIFT”. (But you can reassign it to somewhere else of course)
(See https://www.benchmarksims.org/forum/content.php?153-DirectX-Shifting-Facility for specs) -
How do I change the button assignments in your script?
ETA: Nevermind, I figured out I can do it in Falcon setup.
-
Thanks! Got my 16000m figured out. Now I just have to figure out how to fly the f-16
-
Great work! Stick, rudder and throttle are working well together and with all buttons and functions. I will change some buttons, because i own the rudder, but this is no problem anymore.
Thank you very much!S!
Leo -
Hi Logic,
I am having some problem having buttons on my TWCS throttle to be assign with a fixed DX assignment.
For example, after running my script and pressing the 1st button on the throttle, the falcon 4 controller setup screen would button no “65” instead of the expected “33”.
I had tried deleting the devicesorting.txt file and changing the order of devices and sometime it would show “33”, but sometime it would remain as “65”.
Any help on this?
-
Looks definitively like a device order problem.
Verify that when your script is run, you only have the “T.16000M” and “Thrustmaster Virtual Game Controller (root)” in your Windows USB controllers setup.
If you still see “TWCS Throttle” there, then your script isn’t running/working or something else is messed up (Did you run Teampseak before? Then this is the issue! See ReadMe on first page).
Of course also verify your devices are plugged-in before you run the script. -
I had the following with regards to the devicesorting file;
1. delete the entire file and let BMS recreate it
2. gone into the file and ensure t16000M is the 1st device follow by TM Virtual controller as the 2nd device
3. delete the line containing TWCS throttlethe funny thing is TWCS throttle always keep reappearing (as the last device though).
BTW I do not run teamspeak.
-
the funny thing is TWCS throttle always keep reappearing (as the last device though).
That means TARGET script is not running (well) when you start BMS.
Otherwise BMS shouldnt ever see “TWCS throttle”.
Check with Windows USB controllers settings. -
I also was having problems with the order in which the device sorting.txt was putting them in. It would put the throttle first every time. But I found out that the problem I had was, that if you use the BMS alternative launcher. It will switch it over back the the throttle. After launch bms manualy. I went to settings, the default was on keyboard and switching to the joystick and loading my profile or the logic.key seems to be working as intended. Thought I post this for anyone else who was about 2 pull out there hair, like me.
-
Update….
When I ran Logic’s script everything turns out ok. Then when i ran my script, it also ran ok! Check windows games controller and TWC throttle did not appear.
However, there’s a few instances where my script doesn’t work & the same problem reappear. What i do would then is to run Logic’s script, follow by my script and it would be back to normal.
I would then launch BMS. Stick & throttle work ok. After quitting BMS, i would check the devicesorting.txt and guess what?! TWCS throttle is in the devicesorting.txt file as the last device!
I can’t really figure out where my mistake lies in.
-
I also was having problems with the order in which the device sorting.txt was putting them in. It would put the throttle first every time. But I found out that the problem I had was, that if you use the BMS alternative launcher. It will switch it over back the the throttle. After launch bms manualy. I went to settings, the default was on keyboard and switching to the joystick and loading my profile or the logic.key seems to be working as intended. Thought I post this for anyone else who was about 2 pull out there hair, like me.
Hi,
Had tried this method many times but it didn’t work for me