A Guide to Morphine’s Profile for BMS 4.33 and Beyond
-
Hi Gastone,
Recenter TIR with (unshifted) S4/Paddle is a nice feature. I want to implement it on my Cougar also, through Foxy.
The codes I’ve found in the Morphine/Gastone Warthog .key and .tmc files are:
.key file:
RecenterTrackIR -1 0 0XFFFFFFFF 0 0 0 1 “SIM: TrackIR Recenter (additional)”
.tmc file:
//Paddle/S4
MapKey(&Joystick, S4, TEMPO(PULSE+F12, DX4, 500));Do you know how to ‘translate’ these codes in Cougar/Foxy ‘language’ (for the .key, .tmj, .tmm files) ??
Thx Vordy
-
@Vordy87th:
Do you know how to ‘translate’ these codes in Cougar/Foxy ‘language’ (for the .key, .tmj, .tmm files) ??
Thx Vordy
It shouldn’t be to hard to figure out, if you read the BMS keyfile manual and the target script editor manual. http://ts.thrustmaster.com/download/accessories/pc/hotas/software/target/target_script_editor_basics_v1.5_eng.pdf
-
It shouldn’t be to hard to figure out, if you read the BMS keyfile manual and the target script editor manual. http://ts.thrustmaster.com/download/accessories/pc/hotas/software/target/target_script_editor_basics_v1.5_eng.pdf
I’ve tried to RTFM, but that made me realize that I’m not a software engineer nor a good translator: Note for HOTAS Cougar users: The new script is totally different from the Cougar syntax. :frusty:
-
It has been many years since I used “Foxy,” but I am pretty sure that you can not use DX number commands.
-
For the life of me I can’t get thrustmaster combined to show up on the list from drop down menu. I get virtual controller (root) instead. Any ideas as to how to fix that. I uninstalled and re-installed thrustmaster drivers for warthog and pendular pedals, as well as updating the firmware. I would love for this to work, but I’m so close to being done with BMS altogether because of this issue.
-
For the life of me I can’t get thrustmaster combined to show up on the list from drop down menu. I get virtual controller (root) instead. Any ideas as to how to fix that. I uninstalled and re-installed thrustmaster drivers for warthog and pendular pedals, as well as updating the firmware. I would love for this to work, but I’m so close to being done with BMS altogether because of this issue.
There are a few work arounds posted on this thread. They tend to get buried though so I’ll post them here. Before doing so always run the script through the script editor or via a command line. The GUI is pretty bugged right now in the current version of target.
The first solution is slightly more complicated. It’s to delete the all registry entries for the warthog hotas. Multiple entries seem to conflict target. See below. The Second and easier is to use an older version of target, a link to which is provided below. Also, if using the older version of target you need to use a profile that is compatible with the legacy version of target. a link to which is here https://www.dropbox.com/sh/4l2j2sbbkkmwoaa/AAAMks8YYDvUsOQ6vr7bi5bia?dl=0. If you are going to use the older version of target, you may not need to use the older driver. I wouldn’t try and downgrade drivers unless everything else fails. Also I’m not sure if the new thrustmaster pedals (pendular or tfrp) will work with old version of target. I can’t test either because I don’t own them. So report back if they don’t work with the legacy profile.
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.Thanks for all of the information in this thread. I have been using the Warthog and TARGET for many years and recently tried to update to the latest drivers for Win 10 and had most of the problems listed in this thread. I spent a few days trying the solutions here and even learned about some new bugs to watch out for. However I was unable to get the new drivers and TARGET GUI to work.
I eventually rolled back to what was working which were the 2014 drivers and the 2016 version of TARGET. And then it started working again. Sometimes if I am working for a long time on my pc, then I have to restart it, before launching TARGET but it works now. So I would like to add one more idea for those who are having problems with the new drivers and TARGET and that is to try the older ones. They can be found at the following ftp sites.
The old 2014_THW_1.exe driver file is at:
ftp://ftp.thrustmaster.com/pub/webupdate/HotasWT/
Older versions of Target are at this site:
ftp://ftp.thrustmaster.com/accessories/pc/hotas/software/TARGET
As others have said already in this thread, it is very important to follow the directions, and sometimes it takes a few different tries to get the stuff to install correctly.
-
After fighting with it all weekend, i got it to work with target. Even though its a virtual controller (root) it works great. What I did was put the virtual controller first and then all the inputs and shift states worked perfectly. I thank the person that maintained this profile for the warthog, that hotas and the tpr pedals are an awesome combination. Thank you for the reply and help and happy flying to you.
-
Yeah I had Tried that before to no avail Jkot…. However That and Using the Older Drivers Brought up by Tea Square… BINGO. It’s Fully Functional and Ready to Splash some MiGs! Thanks to everyone who helped me. And No Thanks to Thrustmaster’s Actual Tech Support That Wanted everything up to the Kitchen Sink and a Blood Sample to prove I owned one, And then Gave me ALL The things you already suggested anyways, ending with them going “Well it works with your other games, Play those”.
-
One more idiosyncrasy to add about Target GUI. If it doesn’t start quickly after hitting the run profile button, then it isn’t working correctly.
Sometimes the Target GUI launching and running profile window lists the white text quickly for the first few lines, then slows down, looks like it is thinking then displays the rest of the lines of text. It may look like is working. If you go into BMS and the axis and key bindings are all messed up then it isn’t working correctly. It is a good idea to always go into setup in BMS and check that the axis are correct before flying to make sure that Target is working correctly. Of course this depends on having set up the axis with a correctly running target to begin with.
If the text loaded slowly and the axis and key bindings are porked, don’t start resetting everything in BMS. It is a big waste of time because Target is not actually running correctly. Exit BMS, close the Target launching and running profile window and then close Target.
You can try to run Target again but I have never had any luck doing that.
What works for me is to restart or turn off and turn on my computer then try to run Target again. The text in the launching and running profile window needs to load quickly and smoothly for it to function properly. If it does that then you can start BMS and go into the setup window. It is really a pain to spend time setting up the axis only to find out that Target wasn’t working properly while you did it. Then try to fly on a different day when Target does start properly and find out that the axis and key bindings are all messed up again.
A short while ago, for about a few weeks, target started loading slowing again. I would have to restart my pc, sometimes more than once, to get it to load correctly. Lately it loads correctly every time. It is a mystery.
-
One more idiosyncrasy to add about Target GUI. If it doesn’t start quickly after hitting the run profile button, then it isn’t working correctly.
Sometimes the Target GUI launching and running profile window lists the white text quickly for the first few lines, then slows down, looks like it is thinking then displays the rest of the lines of text. It may look like is working. If you go into BMS and the axis and key bindings are all messed up then it isn’t working correctly. It is a good idea to always go into setup in BMS and check that the axis are correct before flying to make sure that Target is working correctly. Of course this depends on having set up the axis with a correctly running target to begin with.
If the text loaded slowly and the axis and key bindings are porked, don’t start resetting everything in BMS. It is a big waste of time because Target is not actually running correctly. Exit BMS, close the Target launching and running profile window and then close Target.
You can try to run Target again but I have never had any luck doing that.
What works for me is to restart or turn off and turn on my computer then try to run Target again. The text in the launching and running profile window needs to load quickly and smoothly for it to function properly. If it does that then you can start BMS and go into the setup window. It is really a pain to spend time setting up the axis only to find out that Target wasn’t working properly while you did it. Then try to fly on a different day when Target does start properly and find out that the axis and key bindings are all messed up again.
A short while ago, for about a few weeks, target started loading slowing again. I would have to restart my pc, sometimes more than once, to get it to load correctly. Lately it loads correctly every time. It is a mystery.
Running Windows 10 per chance? I’ve recently run into the same issue.
-
Just out of curiosity, which Track IR profile you guy use with this setup ?
Which key you use to center the Track IR view ?
I installed this profile, but on the BMS Warthog throttle and BMS Warthog joystick pictures there is no Track IR center view command…
Thanks ! -
I use Yassy’s profile. It’s in the forum, quick search should turn it up. And, IIRC it maybe in the Doc’s folder of your install.
I’m away from my setup right now but I think I assigned “Scroll Lock” for centering TIR.
-
I am using Win10. Lately the old version of Target loads quickly every time.
-
I use Yassy’s profile. It’s in the forum, quick search should turn it up. And, IIRC it maybe in the Doc’s folder of your install.
I’m away from my setup right now but I think I assigned “Scroll Lock” for centering TIR.
I see it…so no key on the HOTAS ? I would like to bind it to a HOTAS button…more practical…
-
I see it…so no key on the HOTAS ? I would like to bind it to a HOTAS button…more practical…
It’s bound on the hotas in Morphine’s profile. It’s the paddle switch on the joystick. It works as long you use the default bindings in track IR. It even shows it on the picture of the stick in the downloads, it’s labeled “Center TIR”.
-
Hi guys.
So, in the BMS UI control tab, as soon as I move the throttle, the response of it freezes(it seems to occur when i lift the throotle to set the AB detent). Also the stick doesnt seem to move. Any ideas? Followed the steps to the teeDISREGARD.
uplugged and plugged the stick and it works -
This post is deleted! -
Okay with the new changes to 4.34 it looks like this profile needs to be updated again. I will look at it and see what I can find but if you use any of the radios it gets pretty wonky fast
-
Okay with the new changes to 4.34 it looks like this profile needs to be updated again. I will look at it and see what I can find but if you use any of the radios it gets pretty wonky fast
I followed the same install instruction for 4.33 in 4.34 and everything works fine for me. Make sure you’re setting up devicesorting.txt again.
This is what’s in mine.{FFFF044F-0000-0000-0000-504944564944} "Thrustmaster Combined" {B351044F-0000-0000-0000-504944564944} "F16 MFD 1" {B352044F-0000-0000-0000-504944564944} "F16 MFD 2" {C0F2068E-0000-0000-0000-504944564944} "CH Pro Pedals USB"
-
Hi Pilots,
I’ve updated the Morphine’s Profile to be compatible with the 4.34 “BMS Full keys”
You can dowload it here : https://drive.google.com/file/d/1kzh7MuFMd2mjs59eoBekh645derbKcCP/view?usp=sharing
it also works with MFD Server,Enjoy