A Guide to Morphine’s Profile for BMS 4.33 and Beyond
-
@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! -
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.
Re-installed drivers, still this script error message: USB HID device with hardware id “VID_044F&PID_0403” cannot be found
-
That PID is for F/A-18 grip that has not yet been released. So it isn’t causing any issues, I run with the same warning and all is good for me. Have you loaded the .key file from dropbox in BMS? You need that to make it work too. I’ve updated to the latest version of target and the profile is working fine for me. If that doesn’t work then look at the last few pages of this thread. Many people have issues with target, the most frequent is either due to the teamspeak bug or driver install issues. The driver install issue are the most difficult to fix, but it doesn’t look like you have those. So try following all the steps on the first post, if that doesnt work, start the target script, get screen shots of Joy.cpl, the setup menu in BMS and Advanced-> Flight Controls menu too.
-
Ok so I looked at your script startup page again. Whats going is that target is not seeing your throttle. It’s probably related to bad install / windows poor handling of USB devices as of late. You are probably going to have to delete the registry entry for the device, reboot and plug it back in. Then run the script. If that doesn’t work; delete the drivers, then the registry entry, unplug everything, reinstall the drivers, then plug in the devices only when prompted by installer. Once that’s done run the script.
The registry entry for the device is located at:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_044F&PID_0404
You can copy and paste that into regedit, and it will take you to folder, unplug the throttle and right click and delete. Leave it unplugged and reboot. -
Thx Gastone, appreciate your help.
The throttle looks good, eg. radar microstick and speedbrakes are working fine. TARGET doesn’t see the joystick. You’re probably right that it might be a combination of W10 bad handling of USB devices/ports and registry problems. I will delete the drivers, clean the registry and follow your steps. I also will give feedback of the results.
Cheers Vordy
-
With target running, check the status of the hotas in the windows joystick control panel. Click the windows button type joy.cpl either take a screen shot or list the devices there. The fact that throttle is working maybe just a coincidence. I can tell something is up because in the startup the line USB HID Device “”() selected indicates that throttle has not been properly enumartion by target. However if you wish to delete the registry entry for the Joystick too the registry entry is the nearly the same except the PID is 402
-
What to do now ???
-
Check the properties and see if it looks like this:
The trigger should be button 1 for 1st detent and 6 for 2nd detent.
-
Check the properties and see if it looks like this:
The trigger should be button 1 for 1st detent and 6 for 2nd detent.
This and make sure you loaded the keyfile from the dropbox in game.
-
Some good news … my HOTAS is up and running
But I did it the hard way: uninstalled everything, cleaned the registry from all Thrustmaster and PID entries and started all over. Installed drivers, installed Target and followed again your ‘Guide to Morphine’s’ step by step. No problems this time and my Warthog seems okay. I will do some FCF’s to verify everything.
Many thx again for your support guys, appreciate it !!
Follow-on questions:
1. Is it possible to change the stick axas in the tmc file?? I noticed that Target only accepts fcf files for editing.
2. My Cougar was FCC2, which I prefer compared to the moveable Warthog stick. Is a Warthog FCC mod available somewhere?? -
@Vordy87th:
Follow-on questions:
1. Is it possible to change the stick axas in the tmc file?? I noticed that Target only accepts fcf files for editing.Target has two parts a GUI and a script editor. The GUI is basically a program that writes TMC scripts. You can edit the TMC with the thrustmaster script editor to your liking. However you will be writing in code to do so. Generally it is better to run scripts via The Script Editor. As the GUI has issues with closing down properly.
@Vordy87th:
2. My Cougar was FCC2, which I prefer compared to the moveable Warthog stick. Is a Warthog FCC mod available somewhere??
-
Thx Gastone
Website RealSimulator … FSSB R3 only available under request for professional use
So not for funsimmers like us ??
Any idea of the price ?? -
@Vordy87th:
Thx Gastone
Website RealSimulator … FSSB R3 only available under request for professional use
So not for funsimmers like us ??
Any idea of the price ??It shows 450 Eur plus shipping for home customers.
There’s a different version for professional use that can only be bought by contacting them.
-
This post is deleted! -
For the time being I use the mechanical afterburner stop, for fuel management reasons.
In the .tmc the LIST parameters are: LIST(0,5, 65,70, 75,70, 100,100)); //start at 5% for idle cuttoff & create a deadzone between 65% and 75% for AB
Does the 65-75% deadzone correspond with the AB stop, or do I have to change the parameters ??
-
@Vordy87th:
For the time being I use the mechanical afterburner stop, for fuel management reasons.
In the .tmc the LIST parameters are: LIST(0,5, 65,70, 75,70, 100,100)); //start at 5% for idle cuttoff & create a deadzone between 65% and 75% for AB
Does the 65-75% deadzone correspond with the AB stop, or do I have to change the parameters ??
The values can be adjusted for precision but should work ok as they are.
I changed the AB detent to an aftermarket one and wanted to adjust the values to get it lined up better.
The values I ended up with are : LIST(0,5, 72,72, 77,72, 100,100));There’s an easy way to set this up.
Find a joystick tester that shows raw values, at min the throttle showed 65535, when it hit the AB detent it read a little under 18000, which is ~27% of the throttle range.
Want the dead zone to start right below that value, so 72 was the value used.
The default one would still have worked as it covers 65-75% of the throttle range for a dead zone.
I noticed the dead zone starting before hitting the AB with the stock values so that’s why it was changed. -
Find a joystick tester that shows raw values, at min the throttle showed 65535, when it hit the AB detent it read a little under 18000, which is ~27% of the throttle range. Want the dead zone to start right below that value, so 72 was the value used. The default one would still have worked as it covers 65-75% of the throttle range for a dead zone. I noticed the dead zone starting before hitting the AB with the stock values so that’s why it was changed.
Thx TxMtb. What joystick tester would you recommend ??