A Guide to Morphine’s Profile for BMS 4.33 and Beyond
-
had trouble (not seeing rudder axis in bms) when plugging my new TPR pendular rudder and its updated TARGET v.3.0.18.328, but adding the following line to the beginning of the script made it work like a charm again:
Configure(&TFRPHARudder, MODE_EXCLUDED);
Thanks for that mate, had me scratching my head awhile!
Fubar
-
Thanks for that mate, had me scratching my head awhile!
Fubar
Nice! I figured I’d not be the only one scratching my head on this
-
A Guide to Morphine’s Profile for BMS 4.33 and Beyond.
Now you can start BMS, head back to setting menu and begin to bind the axis per the profile.I haven’t run this sim since the late 90s and setting up the warthog is really confusing me. I can get everything set up, up until the point where it says to “bind the axis per the profile”.
Can someone give me a hand, I think I’m making this harder than it is. I just want to get in the sky a learn how to fly this bad boy again!!!
Also, is there a map out of what each switch controls after this profile is installed?Thanks in advance.
-
There are two images in the drop box (link in first post) which shows what is mapped to each button and switch.
The axis are assigned in game, under “Setup”. Two tabs at the top “Flight Controls” and “Avionics Controls”. Click on the drop down and pick the axis to assign, then test.
Hope that helps.
-
Thank you Sarge55, I forgot about those.
I was looking into DCS:F86, to see if a simpler jet might be better to start off on, and have been away from Falcon for a week.Back to i!
-
No problem, glad to help.
Sabre is simpler but I found the F-16 pretty easy to fly and fight. Once it’s installed and HOTAS set up of course, I think that’s the hardest bit. DCS is pretty but until they figure out A/G radar and dynamic campaigns it’s not really a combat flight sim, especially if you fly single player.
Just follow Red Dog’s training manual/plan (Docs folder) and TE’s in game and you’ll be well on your way. Lots of good videos online to augment the training or provide some visual instruction which I find quite helpful. Try searching for Supernova, he has a good collection and there are many others. Check the dates though as some maybe dated and not provide instruction consistent with the current release and update.
Welcome back to Falcon.
-
Thanks again!
Yes, DCS is very lacking in robust s/w and campaigns.
The set-up is hard enough without wonky s/w messing with you. I thought it would be easier to get back into with a “slower paced” sim, but easier it isn’t.
I’m going to get back to training on F-16 BMS and suck it up : ) -
I’m running into this When I attempt to run any script in T.A.R.G.E.T. I’ve Followed all instructions to the letter, Retried Driver Installations, Switched to my USB 2.0 Ports instead of USB 3.0… No Matter What, This is the log I get. once done it comes up as Thrustmaster Virtual Game Controller (Root) As well… Any help would be appreciated. On the verge of Insanity here.
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: “T-Rudder” - “USB\VID_044F&PID_B679&REV_0110”
2: “Joystick - HOTAS Warthog” - “USB\VID_044F&PID_0402&REV_0100”
3: “Throttle - HOTAS Warthog” - “USB\VID_044F&PID_0404&REV_0100”
USB HID device “Throttle - HOTAS Warthog”(USB\VID_044F&PID_0404\5&E658374&0&7) selected
USB HID device “Joystick - HOTAS Warthog”(USB\VID_044F&PID_0402\5&E658374&0&8) 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)…Done -
I’m running into this When I attempt to run any script in T.A.R.G.E.T. I’ve Followed all instructions to the letter, Retried Driver Installations, Switched to my USB 2.0 Ports instead of USB 3.0… No Matter What, This is the log I get. once done it comes up as Thrustmaster Virtual Game Controller (Root) As well… Any help would be appreciated. On the verge of Insanity here.
Are you running Teamspeak? Also have you tried with T-rudder unplugged.
-
Just Tried with the Rudder Unplugged. Same Result as First post but with the bit retaining to it gone.
The Teamspeak one is a bit of a Yes and a No.
First Time I tried, And failed, I reread your post, looked a couple of things up, tried again and failed. On a Whim, I checked to see if I had Teamspeak installed, even though I don’t use it.
Turns Out I did. I Removed the Add-on, Restarted the Computer, Then uninstalled Teamspeak completely since I don’t use it. Issue remains though. -
Hi Char0093 !
I made that a while back : https://forums.eagle.ru/showthread.php?t=207115
Check to see if it can help you pinpoint your issueFlow.
-
Okay, I think we’re making a sort of Progress… Looking through the Event Log Under Administrative Events gives me these two Errors, Though not when I run the Script… Perhaps on Restart, Perhaps on Plugin…
Driver install failed, result=0x80004005 for devnode ‘{152CECC0-AE87-4FB2-811F-F20A0F636B7B}\THRUSTMASTERLOWERHIDFILTER\6&2D303D53&0&01’
Driver install failed, result=0x80004005 for devnode ‘{152CECC0-AE87-4FB2-811F-F20A0F636B7B}\THRUSTMASTERLOWERHIDFILTER\6&3335D1CB&0&02’
I Imagine it’s The Drivers but… I’ve Uninstalled and Reinstalled them (Per Other advice Elsewhere)… Perhaps I didn’t do it right? I Used Thrustmaster’s Driver.exe.
-
Did you try to remove / reinstall TARGET ? That might be your solution. Maybe the drivers for the composite device are not installed correctly.
-
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.