A Guide to Morphine’s Profile for BMS 4.33 and Beyond
-
Greetings Gastone and thanks for your work. Been using the “pinky/paddle” swap profile. Great stuff. I’ve recently replaced my TFR pedals with the MFG ones.
Night and Day.
Just want to make sure which “Target”’ profile I should be using.
Is it the"Full" or “Full 5”? I read at the beginning of this thread that the “Full 5” cancels the new Thrustmaster pedals. Is that the one I should be using?
Thanks. -
Greetings Gastone and thanks for your work. Been using the “pinky/paddle” swap profile. Great stuff. I’ve recently replaced my TFR pedals with the MFG ones.
Night and Day.
Just want to make sure which “Target”’ profile I should be using.
Is it the"Full" or “Full 5”? I read at the beginning of this thread that the “Full 5” cancels the new Thrustmaster pedals. Is that the one I should be using?
Thanks.Run Full, you only need full 5 if you have the TPR pedals. The only reason there are two versions is because legacy versions of target wont’t work if you exclude the TPR in the script.
-
Gastone, thanks for all your support and excuse if the following issue is already covered. I just start using 4.34 and when I use “Boat Switch” to start DF mode it doesn´t work, even if a press through the keyboard D , C or M. I am using Target V.3.018.328 and I load there: Wartog BMS_ Full_swap.tmc, (I tried also WartogBMS_Full_4_434_Paddle.tmc). In BMS I am using: BMS_Full_&_Morphine_paddle_swap.key. I have a friend that have the same issue. Any idea of what is going wrong? thanks in advance
-
The Keyfile for the paddle swap had a bug. The keyfile wouldn’t load in game, which is why none of your keys worked. I updated the dropbox with a fix. Download the key file again, Reload it in BMS. Should be working.
Edit: The whole profile was messed up. I redid it all, it’s working again. Download and install everything, delete the old version. -
Thanks a lot Gastone. I just downloaded the file Morphine_434_Paddle.key as your suggestion and made a quick test in BMS. Still the same issue, the only way to activate the dogfight mode is to maintain press on D through the keyboard. In addition I can not block a target through TMS UP or the radios Through the “mic switich” also do not work propperly, it doesn´t matter if press the paddle or not, it alway ask to Awacs. In TARGET I loaded WartogBMS_Full_4_434_Paddle.tmc That is no there anymore, the only file I see is in dropbox for paddel switch is Warthog_BMS_Full_5_434_Paddle.tmc
-
Thanks a lot Gastone. I just downloaded the file Morphine_434_Paddle.key as your suggestion and made a quick test in BMS. Still the same issue, the only way to activate the dogfight mode is to maintain press on D through the keyboard. In addition I can not block a target through TMS UP or the radios Through the “mic switich” also do not work propperly, it doesn´t matter if press the paddle or not, it alway ask to Awacs. In TARGET I loaded WartogBMS_Full_4_434_Paddle.tmc That is no there anymore, the only file I see is in dropbox for paddel switch is Warthog_BMS_Full_5_434_Paddle.tmc
Just use the new files. Delete the old ones. Run the script. Hit the start button in windows. type joy.cpl. What joysticks do you see listed?
-
I just run Warthog_BMS_Full_5_434_Paddle.tmc and after I executed Joy.cpl and is listed: Thrumaster combined and T-Rudder. I went in BMS and still the same issue. I tried to use the radios and works ok. After I did the same to get in contact with Awacs using the paddle, after that the radios do not work, even not using the paddle when I push up or down the mic switch I get the awacs. About dogfight or blocking a target the same
-
Have you loaded the .key file in game? Page 1 goes over how to do that. You need both files for the profile to work.
-
Gastone, this is what I am doing:
1.- Run Target
2.- Load WarthogBMS_Full_5_434_Paddle.tmc and “run”
3.- Launch BMS
4.- Go to Setup and controller
5.- Load Morphine_434_Paddle and “apply”
The issues still remain. I tried to load the old file key: ( BMS_Full_&_Morphine_paddle_swap.key) with a size 89KB and the radios work fine, I can block with TMS UP but the dogfight mode still not work and the ext lights do not work with the pinky switch on the TQS -
Gastone,
I found the mistakes, my mistake :neutral:.
In BMS configuration in the section “hardware” it was enable “dogfight/missile override self cancel”. I disable it and dogfight mode works now perfectly. I think I am going to use BMS_Full_&_Morphine_paddle_swap.key because I was able to fix the other issues. I reasigned again the lights directly in BMS and now it works correctly. the same for the radios. I tried your new file (Morphine_434_Paddle.key) and radios do not work propperly, not able to switch with awacs as I mentioned. ALso I was not able to block targets througth the radar. -
I’ve gone through and updated Paddle Switch profile. It should make it more reliable. You should only need one Keyfile (the base morphine will work) from now on. All the paddley bits are handled through Target now. The BMS keyfile and the target script are in the dropbox . I’ve also deiced to stop keeping a version of the script for legacy version of Target. So no more full 4. I’ve found newest version for target along with firmware updates much more reliable on win 10. I can actually stop a script and not have it glitch the joystick now. Just make sure you update the firmware too. It’s a separate step from the driver install. See Page 2 https://images-eu.ssl-images-amazon.com/images/I/81hIXiPy5wS.pdf
-
Thanks a lot Gastone, I will check the firmware and also test your new files. I will let you Know.
-
Gastone,
I Load the new version for Target/firmware and I test the new files and everything is correct. Thanks for your help and support!! -
Hi Gastone,
one quick question…
I just installed your 4.34 profile following the suggested procedure in the first page.
I have TM Wharthog (fw: #12 and 23), CH Pedals, three TM Cougar MFD’s and using latest version of TARGET. (3.0.18.328)
In the setup>controllers page on BMS I see a device called “Thrustmaster Virtual Game Controller (root)”.
In the stick the only functions working are the trim and the Paddle Switch (center TIR).
All others don’t…
In the setup>controllers page, if I press the buttons on the stick, I see the relative S button lighting up but I also see the message " Button # no functions assigned" ( where # is the number of the button).
Did I miss something ?Till last week in 4.33 all worked great…
Thanks -
When you see thrustmaster root, it is an indication that the script has not initialized properly. This can be caused by numerous factors, Windows updates, the teamspeak bug, etc.
Here’s a few things you can do to fix the issue. First update target and the firmware and reboot. A guide on how to do so is linked above. Fix the teamspeak bug, outlined in the first page. Try moving the hotas to different USB ports, this will cause windows to re-enumerate the device.
You get the button mismatch because target hides the physical controllers from the system and creates a virtual device. When target fails to initialize, it does not hide the physical devices from the system, and BMS reads both the physical and virtual device. If you can’t get target to work properly, and are stuck with the virtual root device, there is a work around. List the physical devices at the bottom of the devicesorting.txt file. This will force the physical joystick out of the range of the profile.
Also don’t use the 4.34 profile for 4.33. Call backs changed and it won’t work properly. Make sure you follow all the directions and setup the devicesorting.txt file. It’s critical to having the profile function.
-
Hi Gastone,
thanks, I will try all what you suggest and report back. -
Ok,
This is what I did:
Disabled TS addon (I don’t use TS when using BMS)
Changed USB ports of TM WarthogHere the screen of Target GUI and Devicesorting.txt
Tried BMS 4.34…same problem…
-
The attachments you posted don’t work. Update the firmware https://images-eu.ssl-images-amazon.com/images/I/81hIXiPy5wS.pdf. You have to remove the TS joystick add on and reboot. Once you start TS it breaks target until you restart. Do me a favor and grab another screen shot too. With the script running, type joy.cp in the windows start menu, and get a screen shot of the joystick control panel.
-
I have already upgraded the firmware.
TS addon removed.
Here the screenshots:
https://www.dropbox.com/s/pcy5fuqwwpxwd07/Screen%20Shot%2011-21-19%20at%2003.20%20PM.JPG?dl=0
https://www.dropbox.com/s/66rv98igns4zphh/Screen%20Shot%2011-21-19%20at%2003.20%20PM%20001.JPG?dl=0
https://www.dropbox.com/s/z626or86su8d7h5/Screen%20Shot%2011-21-19%20at%2011.28%20PM.JPG?dl=0
Hope it work. -
I have already upgraded the firmware.
TS addon removed.
Here the screenshots:
https://www.dropbox.com/s/pcy5fuqwwpxwd07/Screen%20Shot%2011-21-19%20at%2003.20%20PM.JPG?dl=0
https://www.dropbox.com/s/66rv98igns4zphh/Screen%20Shot%2011-21-19%20at%2003.20%20PM%20001.JPG?dl=0
https://www.dropbox.com/s/z626or86su8d7h5/Screen%20Shot%2011-21-19%20at%2011.28%20PM.JPG?dl=0
Hope it work.Move Thrust Virtual Root to the top of devicesorting.txt as a work around. Something is preventing target from renaming the virtual device correctly. It’s most likely a Windows thing.