Thrusmaster Hotas Warthog not working
-
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.
-
Hi All,
Just to update everyone, I tired everything i could to get the TH to work including the last ditch effort by Frederf but could not get it working. So technically i lost it and what i did was that i removed all devices that is connected to my PC with the exception of my Mouse and keyboard, uninstalled TM Drivers, TARGET Software and did a reboot. Following which, i downloaded the TH driver and software (TARGET) and reinstalled it all over again. Connected by Throttle 1st followed by my stick and i tried running MUD’s profile…Guess what…IT WORKED!!! So what i did was that i reconnected back all other devices back to my PC. So as on now…it’s working as it should be. With this being said, I would like to Thank you all for your assistance and guidance. I’m sure i will face another issue someday but I’m hoping not too. Till then …Happy Flying to all.
Thank you and Regards
-
Glad to hear you sorted it out, happy flying!!!
Verstuurd vanaf mijn F5121 met Tapatalk
-
Gizmo Good on You!!!
-
That was a wise debugging methodology for PC hardware to OS issues. Go back to the very basic device config (mouse and kb) and add one at a time (to MB powered USB ports, USB2 before usb3 for older devices). Once successful, add one more and repeat test cycle. Wash and rinse until all devices work or identify which is causing the issue. Then isolate the one that fails and try it by itself.
I have found that motherboards have different abilities to power and enumerate a certain number of USB devices, some more and better than others. Which is why when I build my PC, I pick the very best MB which was made for gaming and has 18 or more USB Ports (USB 2 and 3).
Being I use all of these ports (Cougar with TUSBA set, Warthog set, Saitek Throttle Quad, 3 USB LCDs, USB ICP, USB wireless mouse and kb, numpad, TIR, WEBCAM, USB rudders, USB powered hub,… (Think that’s what 16 or so there); its critical that I have a strong USB platform. I use an AUSUS Z87 something MB and Win7 with all the auto powering off. My controllers go to the primary MB backside USB ports, via a powered data switch so I can quickly switch from COUGAR to WARTHOG set as needed (BMS or DCS).
When debugging USB to controller (or any devices),Windows Devices and Printers tool provides USB connection info. To a certain degree, this tool does provide a great way to identify USB details for the devices connected to a PC and to specifically identify what device was connected to what port.