A Guide to Morphine’s Profile for BMS 4.33 and Beyond
-
A Guide to Morphine’s Profile for BMS 4.34 and Beyond.
The key file is commented and arranged in a way that should make it easier for people to change functions
Since Morphine has been unable to keep his profile up to date, and I have taken it upon myself to provide an updated version. I have had some difficulties in providing a central repository for the working profile and a place to provide support.The links gets bumped and inevitably lost. I would like to create a centralized place to provide links and support for the latest working versions of the profile. All props to Morphine for having the creativity and skill to crete such a wonderful profile. So here Goes a Guide to Morphine’s Profile for 4.33 and Beyond:
Download Morphine’s Profile for 4.35 from here https://www.dropbox.com/sh/s4x2hexndkxuagy/AADQaHaL8Ph1tccR-zsXz5ZFa?dl=0
Download Morphine’s Profile for 4.34 from here https://www.dropbox.com/sh/kayxm1llc5qp72d/AAC4vU2S4JvVJh_i-GNSDPBTa?dl=0
Download Morphine’s Profile for 4.33 from here: https://www.dropbox.com/sh/66rd8borl2zrfbd/AAAnvz5u93ebm0Tzh322Vw6ba?dl=0BASIC CONCEPTS:
This profile contains two files. The first is called Warthog_BMS_Full_4.tmc. This is the script which target runs. The second file is called BMS_Full_&_Morphine.key. This file is the in game key binds needed for the profile to run correctly. Both files need to be installed properly for the profile to function. Target has now updated to version 3.0.18.328, If you’re using that version or the new pendular rudders please use Warthog_BMS_Full_5.tmc located in the dropbox. It will exclude the pedals from the script, freeing you to bind them in game.
Edit
Added a version where the trim switch pans the camera and shift + trim hat trims the aircraft. It’s in the main folder for 4.34 .Just load Hat views.key in game.BACKGROUND / PREINSTALL SETUP:
TEAMSPEAK BUG:
There is currently a bug with TeamSpeak’s Joystick and Gamepad Add-on which prevents the profile from working properly. The simplest method for fixing this issue is to delete the add-on and restart your system. To delete the add-on Open Teamspeak, select tools->Options->addons (it’s on the left sidebar), Select the Joystick and Game Pad addon and delete it and restart your system. If you absolutely need joystick push to talk there is a work around, see here. https://www.benchmarksims.org/forum/showthread.php?32295-Target-Bug-Solution&p=451559&viewfull=1#post451559
The first thing you want to do is make sure that your Warthog drivers and Target is up to date . The current version of Target is v 3.0.18.328, the most recent version of both can be found here. https://support.thrustmaster.com/en/product/hotaswarthog-en/
Next, Download Warthog_BMS_Full_5.tmc. and BMS_Full_&Morphine.key from the dropbox. The .tmc can be installed anywhere on your hard drive, just remember where you put it. BMS_Full&_Morphine.key needs to be placed in your BMS install in the User -> Config folder.
Now launch TARGET and run the TMC profile. Then run BMS.
In the main BMS screen click setup
Then Select Controllers
In the controller menu select Thrustmaster Combined, then click on the Load button in the lower right. and Select BMS_Full_&_Morphine and select Load. Then in the previous menu hit Apply and Ok.
Now quit BMS the profile isn’t quite ready yet we still need to configure another file to insure that the profile runs properly. In order to do so we need to navigate back the BMS->User->Config folder and edit a file named Devicsorting.txt
The purpose of this file is arrange to the joysticks the game sees so that the buttons pressed matched their assigned profiles. It is a simple txt file, which contains a list off all the joystick plugged into your system when BMS ran. In order for this profile to work, Thrustmaster Combine must be at the top of the list. If you’re using Cougar MFD’s they must be second and third on the list. If your warthog and throttle show up place them at the bottom. Makes the nesscarry changes and save the file.
Now you can start BMS, head back to setting menu and begin to bind the axis per the profile. Just a word advice, the “thrustmaster combine Throttle” axis is supposed to be bound to range knob in the avionics section
At this point you should be good to go. Let me know if you have any questions or problems.
Target not working? see here
https://www.reddit.com/r/hoggit/comments/ge58lo/goodbye_target_alternative_recommendation/fplnjoo/
Or Try disabling the Windows Store from running in the background.
In Win 10 press start, Type background Apps, disable anything you don’t need, Restart and try loading the profile again.
Button Layouts -
Since one the most popular request for this profile is to swap the shift button from the pinky to the paddle, I have created another version of this profile which completely switches the function of the paddle to the pinkie. Meaning not only does the paddle now shift, it also controls weapons, and radar FOV,ect. Link below, install instruction same as above.
For 4.35 https://www.dropbox.com/sh/7x71pt7wgs2v8ie/AADX_4g3QJY6eHPcMGVPBB4ia?dl=0
For 4.34 https://www.dropbox.com/sh/zqypnj53u24t0u0/AADS05-RgNwGtuGCQE68zWJOa?dl=0
For 4.33 https://www.dropbox.com/sh/ok1rydgqzz04qc3/AAA5zuKPALgU-6r5830IMg1ma?dl=0 -
Good job Gastone, hopefully they will sticky this so it stays at the top of the list.
-
It’s good to see someone keeping Morphines going
well done….I have this unusual problem particularry using Mavericks and also boresighting them via the TGP, the TMS up button seems very hit n miss… All other munitions it works fine, locks up great in AA FCR and AG FCR, using LGB’s it fine, I get IR point after ground stabilising… The issue is using Mavs on their own, I am TMS ing up like a loon to get a lock, sometimes the lock only appears at 4-5 miles… I have also tried boresighting them via the TGP, I get all sorts of issues, pages not being SOI when they should, lots of issues getting an IR Point, multiple tries etc… I love the Warthogs but this one area is causing a lot of frustration… Anyone have any ideas? I have been through the sorting .txt and all is as it should be. I am running windows 7 64 bit…
-
Just make sure you have the weapon up on a MFD and it’s SOI. The only other advice I can offer is to zoom the maverick seeker head in, pinkie button and then TMS up. I find the IR mav’s like the the D’s are better at getting a lock from further out than the Optical ones.
-
Thanks I appreciate the quick response… I have used the training mission Cavok as a way of boresighting… I made a short video of my attempts, I’m sure its not me… Have you heard of any glitches that could cause this? Here is a link to the video I made
https://www.dropbox.com/s/5lxf3c07xcah6nn/falcon%20bms.exe%2012.04.2017%20-%2022.27.16.01.mp4?dl=0
-
Thanks I appreciate the quick response… I have used the training mission Cavok as a way of boresighting… I made a short video of my attempts, I’m sure its not me… Have you heard of any glitches that could cause this? Here is a link to the video I made
https://www.dropbox.com/s/5lxf3c07xcah6nn/falcon%20bms.exe%2012.04.2017%20-%2022.27.16.01.mp4?dl=0
It’s you, First at 1:05 you go to slew the the TGP and you press the button on the slew controller. This puts the TGP into laser search mode. This starts messing up the process. Next you should zoom out on the TGP if you want to track the ship. Try to put all of the ship under the gap in the center of the cross hairs. After you finally get it to lock, the hand off starts and fails.
You’re trying to shoot AGM 65G’s in the wide FOV. Which means when you hit TMS up, you’re telling the weapon to force correlate. The mode you’re using bypasses the tracker unit, which is why you don’t get a lock. Try zooming in with the missile (pinkie button) or shooting a missile that doesn’t force correlation’ like a Mav D. This is also why when you TMS up repeatedly the missile switches from Area to HOC. It’s not locking a target because the most of the target is out side the the targeting gate. So it goes into Area target mode (force correlate), It’s discussed in the 34-1-1 on page 162.
At 2:53 the TGP loses it’s point tracking on the ship and switches to area mode. This causes the missile switches out of pre. And even while you’re in VIS, mode you are still trying to force correlate the missile. At 3:02 you put the missile back into pre mode and since the TGP isn’t tracking the ship, the missile’s camera jumps off it. And since you failed to boresight the TGP and missile are now both looking at different areas. By 3:05 the TGP is now SOI, the ship isn’t under the TGP’s cross hairs and you’re hitting TMS up. The system thinks the TGP is trying to lock the water. Even though the ship is under mav crosshairs, it won’t lock or force correlate because the mav is not SOI.
-
I really appreciate the feedback… I am about three quarters through my training for the 185th and this issue is driving me mad. I will reload that mission and follow your advice and report back. Many thanks Aim
-
The slew button seems very sensitive to inwards pressure… I’m guessing thats what is going wrong, my trainer is going to fly the cavok training mission with me tonight and we will go through it.
-
Thanks a lot Gastone for updating the profile. Just got back in to BMS and was worried about Morphine’s profile being outdated for 4.33.
I have one issue though. The autopilot switch seems to be reversed. Like flipping the switch upwards on the designated switch on the throttle flips the switch DOWNWARDS in the simulator. Do I only need to modify the keyfile in BMS itself or do I need to modify the target script as well? Because I have no experience with that.
-
Thanks a lot Gastone for updating the profile. Just got back in to BMS and was worried about Morphine’s profile being outdated for 4.33.
I have one issue though. The autopilot switch seems to be reversed. Like flipping the switch upwards on the designated switch on the throttle flips the switch DOWNWARDS in the simulator. Do I only need to modify the keyfile in BMS itself or do I need to modify the target script as well? Because I have no experience with that.
It was setup by Morphine so that Alt hold on the F-16 matched the label on the Warthog Throttle. This is why the position is inverted relative to F-16. To change it, swap the a and the d on lines 166 and 168 of the target script.
-
For some reason when I use this script if I use the pinky shift everything stops working. For example DMS down swaps SOI fine between left and right MFDs but if I press the pinky button at all (and then release) that stops working completely. What am I doing wrong?
-
For some reason when I use this script if I use the pinky shift everything stops working. For example DMS down swaps SOI fine between left and right MFDs but if I press the pinky button at all (and then release) that stops working completely. What am I doing wrong?
When people have issues with this profile, the two major culprits are not deleting the teamspeak joystick plugin and not using the up to date . Key file. See the first page of this post for further info.
-
I believe there was a conflict with the alternative BMS launcher… I had made some axis binds in there and I don’t believe it worked well with this profile. A clean install and following the steps worked and all is good!
-
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.
-
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.
If you are running Target v3.0.16.615 v2 and the latest version of the profile, available on page 1 of this thread, and are getting root, something is preventing target from creating the combine device. There can be numerous causes for this.
Depending on how you reinstalled windows, there maybe registry errors. Or you haven’t installed the warthog drivers yet. It could be the windows power saving settings. Maybe it’s anti virus software, or Target isn’t pointed at the right directory. It could be some type of windows conflict related to the latest windows update. I really can’t tell based on what info you have provided me. What I can tell is, that the problem is on your end.
As of now the profile works on windows 10 version 1703 OS build 15063.850. The bottom line is that the trouble is on your system. There are to many variables and since I have no knowledge of what is going on with your PC, the only advice I can give you is to follow the steps on page one, and then try and trouble shoot it yourself.
I would start with the Warthog drivers, move onto the power saving, Make sure Target is pointed at it’s install folder, then look at anti virus, and finally windows registry and updates. IE eliminate the easy fixes first.
Hope it helps.
Edit: Just upgraded Win 10 to build 16299.125. Profile and target both work, after a restart.
-
Thanks for those ideas. Will work on this and update with any solution!
-
Sorry guys I have troubles with the profile…when I load it it starts then after a while in the Sim the axis stops working…it happens as I touch the throttle and so it is unusable.
It is not the only script that has the same behavior, but others are for Dcs.
I have win 10 up to the latest updates and the latest drivers and firmware for the warthog.
Can someone point me to a fix?
PS I see only thrustmaster combined in the USB control panel and I tried to uninstall and reinstall both Target and drivers
Inviato dal mio ONEPLUS A5010 utilizzando Tapatalk
-
I think I found a workaround……if I comment all the part regarding the throttle led in the profile it works… someone knows why?
I tried this because I tested mud’s profile and it had not the same problem, then analyzed the differences that could be leading to these freezes…that led me to the LEDs…
The problem is that I like the LEDs functionality of morphine profile and I would like to use it…Inviato dal mio ONEPLUS A5010 utilizzando Tapatalk
-
I think I found a workaround……if I comment all the part regarding the throttle led in the profile it works… someone knows why?
I tried this because I tested mud’s profile and it had not the same problem, then analyzed the differences that could be leading to these freezes…that led me to the LEDs…
The problem is that I like the LEDs functionality of morphine profile and I would like to use it…Inviato dal mio ONEPLUS A5010 utilizzando Tapatalk
Please make sure you have downloaded the most recent version of the profile from the first page of this thread. I have no issues with LED’s. The throttle draws a lot of power, it sounds like your motherboard may not be capable of delivering the amps need to drive it. Your first step in trouble shooting should be to try plugging the throttle into a powered USB hub.
