A Guide to Morphine’s Profile for BMS 4.33 and Beyond
-
Sometimes when my computer is coming out of sleep, it does that to me. I now restart anytime I’m going to use the Warthog.
-
Would be great if you solved this. I’m having the exact same problem, and I don’t really know how to fix it…
There is nothing for me to fix, the problem lies somewhere on your end. I used the profile last night and had zero issues. Since I cannot replicate what you and other have experienced, all I can do is offer advice on how to ensure your system is properly configured.
This is what Target says after compiling and running:
Running script: C:\Users\Fredrik\Desktop\BMS Warthog profile\Warthog_BMS_Full_4.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[1]:
1: “Joystick - HOTAS Warthog” - “USB\VID_044F&PID_0402&REV_0100”
USB HID device with hardware id “VID_044F&PID_0404” cannot be found
Installing filter driver to VID_044F&PID_0402. Please Wait…Script stopped!
Done!
Error:(internal) cannot associate a filter with the selected USB HID device “VID_044F&PID_0402”Runtime Error: STOP request received while running main on line 15 in “C:\Users\Fredrik\Desktop\BMS Warthog profile\Warthog_BMS_Full_4.tmc”
Error:Script run timed out!The script is telling you it cannot see warthog throttle. The first thing you should do is properly reinstall the drivers.
1-Uninstall Thrustmaster drivers (do not unplug the joystick and throttle )
2-Uninstall Target Script Editor Software
3-Unplug all devices (Joystick, Throttle and Rudder pedals)
4-Restart Computer
5-Install Thrustmaster drivers
NOTE : while installing TM driver,you will prompted to plug in the joystick, (DO NOT PLUG IN THE JOYSTICK AND THROTTLE BEFORE PROMPTED)
6-Install Thrustmaster Target Software.
7-Run the profile in the Script Editor.It’s key that you first get a clean install of the drivers before you start trouble shooting elsewhere. The last windows update messed with a lot peoples drivers and settings.
If the profile still doesn’t work, make sure you applied the Teamspeak bug fix from page 1. At that point if it’s still not working, you can start trouble shooting windows power saving, ect. Finally the issue can be related to your motherboard. The warthog throttle at full power draws a lot of amps, some motherboards do not supply enough. Also, some motherboards with USB 3 slots do not have good compatibility with USB 2.0 devices, like the TM warthog. So you may have to update your USB drivers and updated your BIOS. See your mobo’s manufactures website for details.
-
Gastone,
Love the profile, but have had something goofy occurring of late. I’m so new to the Warthog that I’m not sure if it’s a hardware or software issue. Up until the last couple of days, whenever I used the “china hat” on the throttle, my TGP would go from x1 to x4 depending on how long I held it forward and stop when I let off. Now, when I zoom in and let off, it goes from whatever zoom I requested and when I let off, it automatically goes back to x1, or unzooms on its own. I’m not sure if that’s a feature that I accidentally triggered or what?
-
Gastone,
Love the profile, but have had something goofy occurring of late. I’m so new to the Warthog that I’m not sure if it’s a hardware or software issue. Up until the last couple of days, whenever I used the “china hat” on the throttle, my TGP would go from x1 to x4 depending on how long I held it forward and stop when I let off. Now, when I zoom in and let off, it goes from whatever zoom I requested and when I let off, it automatically goes back to x1, or unzooms on its own. I’m not sure if that’s a feature that I accidentally triggered or what?
First try and rule out a hardware fault. Launch the profile, Then in the windows start bar run joy.cpl. Select thrustmaster combine and check to see if the china hat axis is jumping around.
If you have been messing around with the the target files and enabled line 133, you may have broken the china hat functionality.
-
First try and rule out a hardware fault. Launch the profile, Then in the windows start bar run joy.cpl. Select thrustmaster combine and check to see if the china hat axis is jumping around.
If you have been messing around with the the target files and enabled line 133, you may have broken the china hat functionality.
Doesn’t seem to have any issues there. I don’t mess with the target files because I don’t understand them.
-
Ever since I switched from the CH Fighterstick to the Warthog, I had trouble trimming my stick. With even the most minor adjustment, it wants to roll the other way hard. Posted in this thread and Darkman listed a couple of old threads that explained why this is happening.
https://www.benchmarksims.org/forum/showthread.php?33076-Asymmetrical-Loadouts
Gastone, you know already I don’t understand all this DX programming stuff, but I think Morphine’s profile has this issue (all or nothing on trim) and it sounds like it can be fixed if you know what you’re doing, which I don’t. Could you look into this pretty please? Right now, I simply have to jettison an extra bomb because the plane is hard to fly untrimmed. Thanks!
-
Gastone, you know already I don’t understand all this DX programming stuff
Seems like the perfect time to learn.
I think Morphine’s profile has this issue (all or nothing on trim)
False, The only version of the profile which is capable of suffering from the stuck button issue is the Hat View Version, which i made specifically for you.
it sounds like it can be fixed if you know what you’re doing, which I don’t. Could you look into this pretty please? Right now, I simply have to jettison an extra bomb because the plane is hard to fly untrimmed. Thanks!
A work around all ready exists and is on the first page of one of the links you provided.
- Press and hold shift key
- press Trim key and hold it
- continue holding both keys for enough time to achieve desired trim effect
- release Trim key
- release shift key
The only other work around is to not use a shift function in conjunction with trim. Because you requested trim and view control on the same hat, the only other solution is rebinding.
If you spend 30 mins with the Keyfile manual you’ll be capable of editing the profile on your own.
I’ll even start you out, These are the call backs you want to edit
OTWViewUp 0 -1 -3 0 0x0 0 OTWViewUpRight 0 -1 -3 1 0x0 0 OTWViewRight 0 -1 -3 2 0x0 0 OTWViewDownRight 0 -1 -3 3 0x0 0 OTWViewDown 0 -1 -3 4 0x0 0 OTWViewDownLeft 0 -1 -3 5 0x0 0 OTWViewLeft 0 -1 -3 6 0x0 0 OTWViewUpLeft 0 -1 -3 7 0x0 0 AFElevatorTrimUp 2 -1 -3 0 0x0 0 SimDoNothing 2 -1 -3 1 0x0 0 AFAileronTrimRight 2 -1 -3 2 0x0 0 SimDoNothing 2 -1 -3 3 0x0 0 AFElevatorTrimDown 2 -1 -3 4 0x0 0 SimDoNothing 2 -1 -3 5 0x0 0 AFAileronTrimLeft 2 -1 -3 6 0x0 0 SimDoNothing 2 -1 -3 7 0x0 0
Swapping the first digit to the right of the call back, will change if it’s shift + hat or just the hat switch. While the fourth number changes which hat position executes that call back. With 0 being up and 1 being the upper right diagonal.
-
Having an issue here, I just reinstalled windows and BMS with it, and now when I run the TARGET script, I’m not seeing “Thrustmaster Combined” in the setup menu or in my windows devices list. I’m only seeing “Thrustmaster Virtual Game Controller (root).” Using the most recent version of TARGET and have never had Teamspreak installed. Any help appreciated, thanks.
Just to note that I too am running in this issue and investigating the solutions pointed by Gastone.
-
Uninstall target, uninstall all the devices, and start from scratch. it’s the only way I’ve figured out how to keep it working.
Win 10 is being a bear nowadays along with the Nvidia drivers.
Just have to deal with it the best we can. -
Just to note that I too am running in this issue and investigating the solutions pointed by Gastone.
solved!
-
solved!
How? I have exactly the same problem. Currently only some of the buttons work and some buttons do pretty weird things.
EDIT: Got it working too! Just downloaded the new files from the 1st page as directed. Now I feel stupid
-
Good Job bro, thank you …
I installed your profile and config and everything was just fine, until suddenly when I click TQS UHF button, which is the right hat switch on the throttle, when i pull it up, it also presses on left MFD OSB 3 at the same time, I closed the game, closed YAME, and just let the profile running, when I press TQS UHF on desktop, the mouse changes it’s location and presses on the same place where OSB 3 on my second screen… -
Check that device sorting is setup properly, the Thrustmaster combine should be at the top. Next, verify that the target software is working properly. With the profile running hit the Windows start button and type joy.cpl This opens the joystick control panel. You should only see Thrustmaster Combine, the software should be hiding the actual joystick and throttle when a profile is running.
-
This post is deleted! -
Check that device sorting is setup properly, the Thrustmaster combine should be at the top. Next, verify that the target software is working properly. With the profile running hit the Windows start button and type joy.cpl This opens the joystick control panel. You should only see Thrustmaster Combine, the software should be hiding the actual joystick and throttle when a profile is running.
I checked everything, and all was OK…
I checked the Throttle mapping to figure out what is the name of this switch that is responsible for TQS UHF, and it was MIC Switch up, so in .tmc text file, I found this line
"//Mic Switch
MapKeyIO(&Throttle, MSU, DX27, CHAIN( MOUSE_CENTER, DX27)); "
I thought that this “Mouse_Center” is doing something wrong, so i took a copy of the file, and erased this word
Of course that ruined everything, so i undo the modification I made, but it didn’t help …
So I removed Target, removed the profile text file and key mapping file, and installed everything from scratch…
Guess what, the problem still exist -
I checked everything, and all was OK…
I checked the Throttle mapping to figure out what is the name of this switch that is responsible for TQS UHF, and it was MIC Switch up, so in .tmc text file, I found this line
"//Mic Switch
MapKeyIO(&Throttle, MSU, DX27, CHAIN( MOUSE_CENTER, DX27)); "
I thought that this “Mouse_Center” is doing something wrong, so i took a copy of the file, and erased this word
Of course that ruined everything, so i undo the modification I made, but it didn’t help …
So I removed Target, removed the profile text file and key mapping file, and installed everything from scratch…
Guess what, the problem still existSomething else is going on outside of the profile causing your issue. The profile sends one of two commands, depending on if the shift button is pressed. The profile sends either Joystick button 27 or Joystick button 27 and the middle mouse button. It sounds like you have OSB button 3 bound to joystick 27 button in YAME or middle mouse button. Check the callbacks tab in YAME to see what’s going on. Also, just make sure you have all the most recent files for the profile. They are on page 1 of this thread. If you really think the middle mouse button is causing your problems, you should be able to comment out that line of code and have the profile work just fine. Change```
MapKeyIO(&Throttle, MSU, DX27, CHAIN( MOUSE_CENTER, DX27));to
//MapKeyIO(&Throttle, MSU, DX27, CHAIN( MOUSE_CENTER, DX27));
-
It sounds like you have OSB button 3 bound to joystick 27 button in YAME or middle mouse button. Check the callbacks tab in YAME to see what’s going on. Also, just make sure you have all the most recent files for the profile. They are on page 1 of this thread.
Thank you for the quick response, well it’s a good point of view as I was playing with Helios and I found a key map or something that ties YAME, Helios with joystick profile, I’ll try to find it and then delete it.
But I wanna say that this issue happens even if YAME is not running, Like if I started Hotas profile and clicked on this MIC Switch Up ( on desktop), the mouse moved to the same place of OSB3 on my second screen and clicks …
so, does YAME have something to do with it ? -
Thank you for the quick response, well it’s a good point of view as I was playing with Helios and I found a key map or something that ties YAME, Helios with joystick profile, I’ll try to find it and then delete it.
But I wanna say that this issue happens even if YAME is not running, Like if I started Hotas profile and clicked on this MIC Switch Up ( on desktop), the mouse moved to the same place of OSB3 on my second screen and clicks …
so, does YAME have something to do with it ?Here’s the bottom line, unless you’ve messed with script, the only thing the joystick sends is Joystick button 27 or Joystick button 27 + middle mouse button. It does not manipulate mouse position in anyway, and therefore the profile can not be the cause of you’re issue.
With each additional post you keep telling me about more third party software that could be sending commands based on joystick button presses. You need to debug that software on your own. Troubleshooting the profile and 2 pieces of third party software goes beyond the scope of support I’m willing to provide. Just as one last sanity check, please post the contents of you’re devicesorting.txt here.
-
Just as one last sanity check, please post the contents of you’re devicesorting.txt here.
{FFFF044F-0000-0000-0000-504944564944} “Thrustmaster Virtual Game Controller (root)”
{C215046D-0000-0000-0000-504944564944} “Logitech Extreme 3D Pro USB”
{0402044F-0000-0000-0000-504944564944} “Joystick - HOTAS Warthog”
{0404044F-0000-0000-0000-504944564944} “Throttle - HOTAS Warthog”
{076406A3-0000-0000-0000-504944564944} “Saitek Pro Flight Combat Rudder Pedals (USB)” -
Based on your Devicesorting.txt, I can tell target is not functioning properly. In your device sorting, you should have “Thrustmaster Combined” at the top. “Thrustmaster Virtual Game Controller (root)” means the profile did not complete it’s setup correctly. The number 1 cause of this issue is the teamspeak bug. You’ll have to remove the joystick addon and restart. Detailed instructions are on page 1 of this thread.
There may also be numerous other causes of the Target Bug. It’s been reported that it maybe caused by performance monitoring software like MSI afterburner, power management settings, registry settings, ect. Review the last few pages of the thread and you’ll see numerous people struggling with the problem also.
I run a pretty clean system, Windows 10, and I have zero issue with the script or target. And since there is an infinite combination of system configurations and software, the problem is not something i can feasibly debug for everyone. The only way to eliminate causality is to do a clean install of target and warthog drivers, including deleting any registry entries for the devices. Remove as much of the 3’rd party software as u can, until you get Thrustmaster Combine to appear in the joystick control panel. Click start and type joy.cpl to view it. However before you going doing that, try fixing the teamspeak bug first. It’s generally the most pain free fix.