Thrusmaster Hotas Warthog not working
-
Hi Guys,
I’m having this problem. I run the script editor and it compiles success but when i got into my BMS Setup page, when i choose Thrustmaster Combined, the Throttle and the joystick does not move at all. I tried moving the usb to other various slots including a 3.1 slot but still the same issue. Am i missing out something ? When i choose Throttle directly,it’s no issue. Works fine. Likewise for the Stick. Really need your help please.
Thank you
Regards
-
More info required. What profile are you using? Does TARGET detect the axis? Have you set up the axis correctly in the SETUP -> CONTROLLERS -> ADVANCED tab?
-
Might check his devices in the DeviceSorting.txt file
-
I guess he is changing his primary device Tab which should be kept for the Stick.
Docs/Falcon BMS Manuals/BMS-Manual.pdf 4.3.6 CONTROLLERS page
-
Hi Guys,
Thank you for your replies. What actually happened was that I unplugged my TM Hotas from my PC and replugged into a different USB. From that point on, Target dectects my TM and shows TH Combined but in the game setup, when i choose TH Combined, my stick and throttle doesn’t move unless I change it to TM Thttotle and stick manually and my key profiles doesn’t work.
Thank you
-
Hi Guys,
I just checked on DXDIAG that my throttle is no 1 and my joystick is no 2. I tried changing to all USB slots including my USB 3.0 and still keeps having the same numbering. What else can i do to rectify this issue??? Very frustrating. Really need your help please.
-
Does not really matter, correct sequence for BMS is set in the devicesorting.txt, like AV8R already mentioned in post 3….
Verstuurd vanaf mijn F5121 met Tapatalk
-
Hi Terminator,
How do i do that and where can i find the devicesorting.txt? Would you be able to guide me pls?
-
Hey Gizmo,
The devicesorting.txt can be found in the X:\Falcon BMS 4.33 U1\User\Config folder.
I can see you are new on the forum, but you can see people responding to your post with questions. In the future it might be a good idea to answer the questions asked. Ice already replied with the questions important to help you solve the problem. So keep that in mind next time you need help, a lot of people on the forum are willing to help, but you need to give them the information they need to help you. Just a friendly and free tip!
So,
1. what profile are using?
2. What controller do you select on the main controller setup page?
3. What does your devicesorting.txt look like?With that info we can make a start to solve the problem.
Verstuurd vanaf mijn F5121 met Tapatalk
-
Troubleshooting 101, divide and conquer.
Until you understand and have confidence in what your joystick devices are outputting logically it’s best to leave Falcon out of it. Windows as well as TARGET have a lot of testing resources to verify that the logical output matches expectations before running Falcon.exe is even considered.
TARGET’s design is that when run it hides the controllers its using for input (usually all of them) and inserts itself as a new logical device in their places. To Windows it appears as if you have unplugged the joystick and throttle and plugged in a totally different device. If you ever see all three in the USB game controllers list at the same time something is wrong. TARGET manages which devices are visible by disabling and enabling them in Device Manager which can mess up especially in the newer security-conscious versions of Windows.
The TARGET service runs a script which is either generated from the GUI program or as entered manually. Unless explicitly excluded on a device by device basis all TM devices are hidden. The hidden devices’ input is then used by the service to determine the virtual device’s output as programmed by the script.
Diagnosis:
1. Set up your controllers to play Falcon BMS. Open up the Game Controllers control panel and look at the devices listed. What devices are there? Are they what you expect? The most common use case is that you will have only one Thrustmaster-related device called “Thrustmaster Combined.”
2. Run the TARGET Device Analyzer. Look at the output of the Thrustmaster Combined device (may have to choose it from the circular button top left corner). Does the input (left pane) match the expected output (right pane) according to your TARGET programming?
3. If everything looks correct in steps 1 and 2, start Falcon and set the joystick device in the dropdown menu to the device which has the pitch and bank stick axes on it. Do not select a different device from this dropdown menu in an attempt to get other functions (throttle, etc.) to work. This selected device must be the device which has the pitch and bank axes. All other button and axis functions are configured elsewhere in the menus.
-
Good post Frederf
-
Hi Terminator,
Yes i am new to this forum. You are absolutely correct about not giving the info required and there is no excuse for that. I do appreciate that there are fellow simmers willing to help and i thank you for that. Moving forward, here is the info you mentioned which i have compiled.
-
Trying to use Mud’s profile.
-
I did select Thrustmaster Combined from the main controller page but my throttle and stick doesn’t work.
-
As for the device setting… pls see below
{FFFF044F-0000-0000-0000-504944564944} “Thrustmaster Combined”
{0402044F-0000-0000-0000-504944564944} “Joystick - HOTAS Warthog”
{0404044F-0000-0000-0000-504944564944} “Throttle - HOTAS Warthog”
{076306A3-0000-0000-0000-504944564944} “Saitek Pro Flight Rudder Pedals”I have uninstalled drivers for TM Hotas completely and reinstalled the drivers following which i plugged my HOTAS (stick and throttle) only to ensure only those were detected but to no avail. Problem still persist. In BMS controller setup page, it doesn’t even show Thrustmaster Combined anymore.
Following is the response from the Script editor when run Mud’s profile:
Running script: C:\Program Files (x86)\Thrustmaster\TARGET\scripts\BMS 4.33 - Mud.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: “Throttle - HOTAS Warthog” - “USB\VID_044F&PID_0404&REV_0100”
2: “Joystick - HOTAS Warthog” - “USB\VID_044F&PID_0402&REV_0100”
Installing filter driver to VID_044F&PID_0404. Please Wait…Done!
Error:(internal) cannot associate a filter with the selected USB HID device “VID_044F&PID_0404”
Installing filter driver to VID_044F&PID_0402. Please Wait…Done!
Error:(internal) cannot associate a filter with the selected USB HID device “VID_044F&PID_0402”
USB HID device with hardware id “VID_044F&PID_b351” cannot be found
USB HID device with hardware id “VID_044F&PID_b352” cannot be found
USB HID device with hardware id “VID_044F&PID_B10B” cannot be found
USB HID device with hardware id “VID_044F&PID_B687” cannot be found
USB HID device with hardware id “VID_044F&PID_B679” cannot be found
Virtual HID devices managed by script!
Connecting virtual joystick…Script stopped!
Done
Device name set to Thrustmaster CombinedRuntime Error: STOP request received while running main on line 18 in “C:\Program Files (x86)\Thrustmaster\TARGET\scripts\BMS 4.33 - Mud.tmc”
Error:Script run timed out!Regards
-
-
Looks like the hiding of the devices from Windows is failing. VID_044F&PID_0402 is the joystick and 0404 is the throttle.
Line 18 is the first line after the device exclusion area so the script is probably stopping because of the failure to filter the two devices.Perhaps try running TARGET Script Editor with administrator privileges and it might succeed in messin’ with the Device Mananger?
-
That’s what I was thinking. I don’t use Mud’s profile but i downloaded it and ran it in my setup, below the results:
Running script: F:\Falcon\MUD\BMS 4.33 Script - Mud v3.06\BMS 4.33 - Mud.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[5]:
1: “T-Rudder” - “USB\VID_044F&PID_B679&REV_0110”
2: “F16 MFD 1” - “USB\VID_044F&PID_B351&REV_0100”
3: “Joystick - HOTAS Warthog” - “USB\VID_044F&PID_0402&REV_0100”
4: “Throttle - HOTAS Warthog” - “USB\VID_044F&PID_0404&REV_0100”
5: “F16 MFD 2” - “USB\VID_044F&PID_B352&REV_0100”
USB HID device “Throttle - HOTAS Warthog”(USB\VID_044F&PID_0404\5&521A615&0&5) selected
USB HID device “Joystick - HOTAS Warthog”(USB\VID_044F&PID_0402\5&521A615&0&8) selected
USB HID device “F16 MFD 1”(USB\VID_044F&PID_B351\7&A8C2512&0&4) selected
USB HID device “F16 MFD 2”(USB\VID_044F&PID_B352\7&A8C2512&0&3) selected
USB HID device with hardware id “VID_044F&PID_B10A” cannot be found
USB HID device with hardware id “VID_044F&PID_B687” cannot be found
USB HID device “T-Rudder”(USB\VID_044F&PID_B679\6&24A7EF&0&3) 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
The script runs fine on my system, (disregard the extra devices found)
If something is failing already running the Script something must be wrong in windows.
So what first comes to mind:If they work/test fine in the device manager Frederf’s tip might work, but my guess is the Windows hardware setup……
EDIT:
hmm, of course your stick and throttle are recognized, they should be ok. Did you try to reinstall TARGET?
If that don’t work I found this solution on the world weird web:open regedit (Windows + R, write “regedit” and run it) go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB{Your Device ID here} you can retrieve your ven id/dev id through TARGET by trying to load a script if you have multiple joysticks, they are listed by their virtual ID (I guess) here. Do the following step for both of them. go to Device Parameters now set everything that is “1” to “0” restart
(https://www.reddit.com/r/hotas/comments/5it8q2/solution_to_thrustmaster_target_software/)
-
- I did select Thrustmaster Combined from the main controller page but my throttle and stick doesn’t work.
Aside from the script not running, in the main controller setup page select the stick from the drop down menu (like Frederf mentioned in post 10)
3. If everything looks correct in steps 1 and 2, start Falcon and set the joystick device in the dropdown menu to the device which has the pitch and bank stick axes on it. Do not select a different device from this drop-down menu in an attempt to get other functions (throttle, etc.) to work. This selected device must be the device which has the pitch and bank axes. All other button and axis functions are configured elsewhere in the menus.
even with no script running this should give you control over the stick axes and most of the buttons.
BTW, i found something else similar your problem running scripts (google is your friend:D) here in post 11, possible solution at the bottom of post 13:
By the way, for anyone else reading my earlier posts with images regarding TARGET not working/running scripts etc. the problem turned out to be my Firewall (COMMODO Free Firewall)!!
Uninstalled it, went with ZoneAlarmPro and it worked like a dream first time and has been ever since?
Worth trying or knowing if you use TM gear i guess?
Does that make sense? I don’t know, maybe some firewalls prohibit changes in the registry, but worth a try i think.
Good luck!
-
Hi Terminator and guys,
I am using Win 10 and i really cant seem to find my TM on my device Manager. I am also using a unpowered USB which are directly connected to my PC.
-
Hi Terminator and guys,
I am using Win 10 and i really cant seem to find my TM on my device Manager. I am also using a unpowered USB which are directly connected to my PC.
Try connecting directly without the HUB and see what happens….
Verstuurd vanaf mijn F5121 met Tapatalk
-
Hey gizmo I had a similar issue two years ago, my WH would go to sleep every now and then talked to thrustmasters/email two solutions given. 1. use only a powered hub for the WH. 2. better yet to plug the WH into the main computer, this will keep WH up and running. I to was using a UN-powered hub, switched WH to the main computer MB and no problems since, not a user of win 10, so just my two cents.
-
Hi Weaklink,
Thank you for your solutions. Previously i did try plugging into the PC directly but that didn’t work. I will try that again and will revert back. BTW, which powered HUB would you recommend getting?
-
Make sure Windows isn’t using USB power saving and any USB port is providing the full power spec. However if the joystick devices work properly without TARGET running then it’s unlikely that the addition of TARGET will cause any problems related to USB power.
My W10 Device Manager TM devices are as follows:
Human Interface Devices>
HID-compliant game controllerThose are all three of them (Thrustmaster Combined, Joystick - HOTAS Warthog, Throttle - HOTAS Warthog). How you can tell them apart is by hardware ID or by the Game Controllers dialog and enabling/disabling them to see what drops off the list. To check hardware ID right click the Device Manager entry and look in properties.
In properties, Details tab, Property dropdown, Hardware Ids
HID\VID_044F&PID_0402&REV_011
That’s the joystick.What you should see on a double-replace TARGET script is that the Thrustmaster Combined device (you’ll see as a hidden device if you enable that in View, Show hidden devices) will go enabled and the two joystick, throttle devices will go from enabled to disabled. You can watch this all happen with Device Manager open as you hit the play and stop buttons. If those actions don’t happen as expected then there’s something preventing TARGET from interacting with Device Manager properly.
