A Guide to Morphine’s Profile for BMS 4.33 and Beyond
-
If the profile works then stops, check the windows 10 power savings settings. Make sure selective suspend is disabled. Windows has a habit of powering off USB ports if the power savings is in use. You may even have to get into the device manager and disable windows from shutting off power saving. I would also re-download the profile again too if you have been making edits. It’s easy to inadvertently break the profile.
After you trouble shoot windows power saving, if u still have issues Try moving the usb hub to other ports and ot replace your USB hub. The issue sounds like it’s power related on your end. Follow those steps and you’ll eliminate the causality tree for power issues. After, that you’ll have to look at Windows issues.
Thanks for the heads up….i disabled windows usb powermanagement both in the power profile, and in every singe usb device in the hardware control panel, buth nothing works so far.
The only thing that makes the profile working for now is to comment the parts of the script where there is the led management…so i thing it could be something relating to thrustmaster drivers not managing leds well under windows 10…no one with the same issue? -
Thanks for the heads up….i disabled windows usb powermanagement both in the power profile, and in every singe usb device in the hardware control panel, buth nothing works so far.
The only thing that makes the profile working for now is to comment the parts of the script where there is the led management…so i thing it could be something relating to thrustmaster drivers not managing leds well under windows 10…no one with the same issue?I have windows 10 and no issues with the LEDs.
-
I think I found an error in the keyfile.
SimCMSUp 14 8 -2 0 0x0 0
SimCMSRight 15 8 -2 0 0x0 0
SimCMSDown 16 8 -2 0 0x0 0
SimCMSLeft 17 8 -2 0 0x0 0In the Morphine file, SimCMSLeft is actually SimCmsLeft (MS not capitalized), which make the CMS left button default to down just like CMS down does. You may want to fix and reupload to dropbox. Cheers!
-
I think I found an error in the keyfile.
SimCMSUp 14 8 -2 0 0x0 0
SimCMSRight 15 8 -2 0 0x0 0
SimCMSDown 16 8 -2 0 0x0 0
SimCMSLeft 17 8 -2 0 0x0 0In the Morphine file, SimCMSLeft is actually SimCmsLeft (MS not capitalized), which make the CMS left button default to down just like CMS down does. You may want to fix and reupload to dropbox. Cheers!
Thanks, nice catch. Fixed it in both versions, vanilla and paddle swap. Working fine now.
-
No prob. Question: one thing I use a lot is the 2d pit to do my ramp startup (a lot easier for me trying to move dials with TrackIR moving). I noticed the snap function isn’t mapped anywhere in this profile and maybe I was tired last night, but I couldn’t find anything on the keyboard file to snap around in the 2d pit. On my old CH Fighterstick, they used the POV hat on the stick, with pinky/POV for trimming the stick. I’m afraid to say I’m not much of a DX programmer, would it be possible to change this profile this way since we’re not using the pinky/POV anyway. If not, I can use the keyboard if I can figure out which keys to use. Thanks!
EDIT: Ok, with the light of morn, it looks like the shift-number pad is what I’m looking for and I’ll try when I get home. I still think it would be a good idea to either add the snap view to the POV hat either as the primary or the shift. I think the shift makes more sense for the trimming so you don’t accidentally add trim, which you’d need the pinky shift for.
-
After giving myself a headache trying to figure out TARGET by RTFM, is there anyone out there kind enough to take the Morphine profile, change the trim function from POV to shift-POV and assign the POV hat back to the default cockpit view so I can use it in the 2d cockpit on startup to look around? I could be wrong, but if one knew what they were doing, I’m guessing this wouldn’t take long? You will have my everlasting thanks and I’ll consider naming my next grandchild after you unless you have a really, really weird name
-
After giving myself a headache trying to figure out TARGET by RTFM, is there anyone out there kind enough to take the Morphine profile, change the trim function from POV to shift-POV and assign the POV hat back to the default cockpit view so I can use it in the 2d cockpit on startup to look around? I could be wrong, but if one knew what they were doing, I’m guessing this wouldn’t take long? You will have my everlasting thanks and I’ll consider naming my next grandchild after you unless you have a really, really weird name
No worries target can be tough to get into. Though in this case you don’t have to edit the target files, the TMC ones. To make this kind of change you would need to edit the .key file. If there is something you want to change in the profile, the first thing to do is look at the .tmc file. If it’s a button that says keyfile controlled, you’ll probably be looking at editing a directx setting in the key file. Items like Pinky Switch send keyboard commands. So if you want to change the function of the pinky switch, just edit the keyboard commands there.
Anyway, because this stuff is such a pain and it’s also a great idea, that could be helpful to others, I’ve gone ahead and implemented it. If you all ready have the TMC, no need to download it again, it’s exactly the same. Just download the .key and apply it per the instructions on the first page.
Download Morphine’s Hat View From Below Now included in the primary dropbox, Just use the Hat Views keyfile in game
https://www.dropbox.com/sh/kayxm1llc5qp72d/AAC4vU2S4JvVJh_i-GNSDPBTa?dl=0Edit: Since this code snippet maybe helpful to others who wish to have both trim and hat view in their profile, I’ll provide it below. If you want to add it to your own .key, just make sure you delete all your view and trim hat assignments first.
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
-
you da man!
-
Would be great if you solved this. I’m having the exact same problem, and I don’t really know how to fix it…
-
Wow. Just did some more testing. Ran the .tmc file in TARGET and the throttle just died. Re-booted the computer, the throttle turned on momentarily, but died again as soon as Windows started. Switched to another USB post and the throttle turned on instantly. Ran the .tmc file again and once more the throttle died. Did one final test, and now I actually have three USB ports where the throttle is just dead. The strange thing is that the joystick still works in those “dead” USB ports. Does anyone know what might have happened?
-
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! -
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.