A Guide to Morphine’s Profile for BMS 4.33 and Beyond
-
Was the device unplugged when u installed it? If not that can cause an issue. I think u need to uninstall unplug the HOTAS, restart, run the software, wait to plug in till prompted by the installer. If that fails you may need to uninstall, unplug and restart. Then remove any entries for the warthog from the registry.
-
Nope. Still no Luck. I even Did a System Restore back to a day before the Stick Arrived, and before I installed my Pedals and Target. Removed Teamspeak Completely before Installation of everything. Uninstalled the Joystick Addon for TS3 too just to be sure. Checked all Folders for Traces of all three programs, and Ensured Registry had no traces of Either the Stick, Or the Throttle. Followed All Directions to the Letter. Still nothing. This is what Everything looks like when it fails.
Without Pedals:
With Pedals:
-
Have you tried moving them to different USB ports? This sometimes causes windows to see them as new devices and may shake things out.
-
Tried That… Went from my Two USB 2.0 Hubs to the USB 3.0. Just Added new lines to the The Log. Still comes out as Thrustmaster Virtual Game Controller (Root)
Here’s the new one:
Running script: C:\Users\owner\Desktop\Warthog_BMS_Full_4.tmc
*** Allocated ProcInstances found from the previous run: use FreeProcInstance() ***
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[3]:
1: “Joystick - HOTAS Warthog” - “USB\VID_044F&PID_0402&REV_0100”
2: “T-Rudder” - “USB\VID_044F&PID_B679&REV_0110”
3: “Throttle - HOTAS Warthog” - “USB\VID_044F&PID_0404&REV_0100”
Installing filter driver to VID_044F&PID_0404. Please Wait…Done!
USB HID device “Throttle - HOTAS Warthog”(USB\VID_044F&PID_0404\5&E658374&0&2) selected
Installing filter driver to VID_044F&PID_0402. Please Wait…Done!
USB HID device “Joystick - HOTAS Warthog”(USB\VID_044F&PID_0402\5&E658374&0&1) selected
USB HID device with hardware id “VID_044F&PID_0403” cannot be found
USB HID device with hardware id “VID_044F&PID_B68F” cannot be found
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
-
? I Used Thrustmaster’s Driver.exe.
Tried That… Went from my Two USB 2.0 Hubs to the USB 3.0. Just Added new lines to the The Log. Still comes out as Thrustmaster Virtual Game Controller (Root)
Here’s the new one:
So after reviewing the thread again, the only other thing I can think of is, you’re not installing the correct drivers. Your mention of Drivers.exe makes me think it may be the wrong set. For warthog, but the most recent driver package is called 2018_TMHW_1.exe. You can find it here. https://support.thrustmaster.com/en/product/hotaswarthog-en/
Other than that it seems like there is a driver issue preventing target from working correctly. Unfortunately I do not know how to trouble shoot that other than other steps mentioned in this thread. However you still maybe able to get away with using the root controller since the warthog hotas is not showing up in joy.cpl. You shouldn’t get any button double press, ect usally caused by the Target bug because there is only one joystick your system sees, Thrustmaster root.
-
Sadly those are both the Latest Drivers and Firmware I installed from their site as well. I’ll keep working on it. What’s funny is the Throttle Inputs still work just fine, It’s the stick’s button’s that don’t map correctly. I might be able to Jury-Rig it with a personal Key File Customized off of Morphines’s/Your Update… Just Sad I really can’t unlock the full features of the Stick after waiting so many years to get one when I had some Spare Cash. :sad:
-
I’m still convinced it is a combined device driver issue.
The combined device should be named “Thrustmaster Combined” or something similar, not “Thrustmaster Virtual Game Controller (root)”.
Try a different USB port (2.0 if you have that available) and try again please.
-
I just thought of this, it works for some people, launch the script from a desktop short cut, set the target as “C:\Program Files (x86)\Thrustmaster\TARGET\x64\TARGETGUI.exe” -r “C:\Users\XXX\Downloads\Warthog_BMS_Full_4.tmc” Use the quotes and set file location to where ever you are storing the profile.
-
Nope, Same Issue. Still fails to produce Thrustmaster Combined when the Script it Launched…
Flow, you are Correct, it IS a Combined Driver Issue. As in, When the script launches it’s not switching over to that and all attempts to fix it fail. I’ve tried on both USB 2.0 and USB 3.0
Unless there is a Specific Driver I’m apparently missing to Download, This issue probably will not be fixed. -
What version of windows are you running ?
-
Windows 8.1 64-bit.
-
Hmm… That is strange.
If you do a simple profile without anything in it using TM TARGET GUI, is it working or not ? Or does it do the same error ? -
Still shows up as Thrustmaster Virtual Game Controller (root). And it’s also Affecting the Rudder when I add it to the Profile As well. More Searching, More Solutions that Don’t Work. At this point I’m going to hope one day it works, And Figure out my Jury Rig from here. Thanks for the Help at least.
As a Last Desperate Gasp, I’ve sent the Issue to Thrustmaster Support, And Leave you with my Window’s Troubling Shooting Screens for the Stick and throttle to see if it will help.
-
Still shows up as Thrustmaster Virtual Game Controller (root). And it’s also Affecting the Rudder when I add it to the Profile As well. More Searching, More Solutions that Don’t Work. At this point I’m going to hope one day it works, And Figure out my Jury Rig from here. Thanks for the Help at least.
As a Last Desperate Gasp, I’ve sent the Issue to Thrustmaster Support, And Leave you with my Window’s Troubling Shooting Screens for the Stick and throttle to see if it will help.
Not sure if you tried this registry trick, but it may be worth a shot.
https://www.reddit.com/r/hotas/comments/5it8q2/solution_to_thrustmaster_target_software/Also if you want to give up on target, Joystick Gremlin maybe a viable alternative.
-
Yep, I am out of options.
I would try to remove TARGET and reinstall it with windows in a mode that does not want the drivers to be signed :after that I have no more ideas.
-
Hi Gastone,
I face some problems when installing Morphine’s profile:
1. When running Warthog_BMS_Full_5.tmc in TARGET, it doesn’t stop running (see pic).
2. BMS setup all required settings done. Throttle looks okay, but stick seems not recognized, stick doesn’t work.Your guidance would be appreciated.
Thx Vordy
-
@Vordy87th:
Hi Gastone,
I face some problems when installing Morphine’s profile:
1. When running Warthog_BMS_Full_5.tmc in TARGET, it doesn’t stop running (see pic).
2. BMS setup all required settings done. Throttle looks okay, but stick seems not recognized, stick doesn’t work.Your guidance would be appreciated.
Thx Vordy
Looks like the script is running fine, you just leave it running in the background.
If your button numbers seem to be off, make sure that the x:\Falcon BMS 4.33 U1\User\Config\DeviceSorting.txt has “Thrustmaster Combined” as the first line.
-
Looks like the script is running fine, you just leave it running in the background.
If your button numbers seem to be off, make sure that the x:\Falcon BMS 4.33 U1\User\Config\DeviceSorting.txt has “Thrustmaster Combined” as the first line.
Thx for your reaction TxMtb (Texan ??)
1. TARGET has to run in the background intentionally ??
2. Yes did that, ‘Thrustmaster Combined’ is t(already was) he first line in DeviceSorting.txtSo, it has to be something else, any (other) clue ??
Many thx, Vordy
-
@Vordy87th:
Thx for your reaction TxMtb (Texan ??)
1. TARGET has to run in the background intentionally ??
2. Yes did that, ‘Thrustmaster Combined’ is t(already was) he first line in DeviceSorting.txtSo, it has to be something else, any (other) clue ??
Many thx, Vordy
Yep it has to run in the background all the time.
There is an error in the script I overlooked the first time, &PID_0403 not found.
Might try re-installing the drivers for the stick and throttle.
-
This post is deleted!