@fvelazdem said in Morphine’s Profile For 4.37:

Thank you very much Gaston!!

I had already lost hope of having the profile updated.

I have followed your installation instructions but unfortunately it doesn’t work for me, I always use the Paddle Switch as Shift and it doesn’t work. For example, HSD RANGE UP. Neither does Master ARM or RDR ALT work.

You probably don’t have the correct key file loaded in game. The game must always be started with
the Launch Without Override selected. If not, the new launcher will override all you settings, load the default BMS full key file and change your devicesorting.txt file.

In game go to the settings, and see which key profile is loaded. If it’s auto or full, the launcher ate your settings. You need to reload Morphine’s Full and PRESS APPLY. exit the game, edit devicesorting.txt again, then go back in game and setup your axis.

You also cannot change any key binds within the launcher. That all should be done with txt editor.

If you can’t get it to work just use the launcher and set everything up.

@fvelazdem

There was an issue with the master arm switch in Target files. It’s been fixed and the files and dropbox have been updated. Try downloading the files again from dropbox.

@fvelazdem

I’m having a hard time understanding what the issue you’re having is.

The expected behavior for the Paddle swap profile is

1. Press and Hold Paddle.
2. Press DMS right
3. The waypoint increases

Or

1. Press and Hold Paddle
2. Press DMS Left
3. The Waypoint decreases

Without out the paddle held, DMS and TMS should function normally.

If this not the case, it looks like the target software is not working properly on your system. When the profile runs. It should hide the Joystick and throttle from windows.

If you open the windows joystick panel with target running. All you should see is thrustmaster combine, the MFDS, and your rudder pedals. If you see the throttle or joystick and thrustmaster combine. The profile will not work.

@Finger-Jam-0 said in Morphine’s Profile For 4.37:

I don’t seem to have a “Thrustmaster Combined” in my DeviceSorting.txt file.

With the scripting running open the windows joystick control panel

You can also open the panel by clicking on the windows button in the lower left and typing joy.cpl

What do you see listed in the windows joystick control panel.

The only devices should be the thrustmaster Combined, the MFD’s (if you have them) and any other USB joysticks you have plugged in. Such as rudder pedals, ect.

If you can grab a screen shot of the target interface with the profile running that would be helpful.

You can grab a screen shot by pressing the windows key on your keyboard shift and s at the same time.

@fvelazdem said in Morphine’s Profile For 4.37:

In the same way, CMS or TMS do not work. I tried to launch flares and nothing happened or to activate the ECM. TMS in the same way.
Obviusly I downloaded from your last link.

I just downloaded the paddle swap from the dropbox, Started it in Target and it ran perfectly fine.

I recorded a video of BMS and the Thurstmaster Device Analyzer running. So that you can see the button press’s happen in real time. DMS + paddle functions as expected so does CMS and all of the other HOTAS commands.

I would try downloading the target files and the .key file then follow the steps on the first page. Be sure to recheck the Devicesorting.txt too. As the game will change it if you happen to start BMS without target running.

If that doesn’t work try I’ll need some more information to try and help you.

1. Get a screen shot of Target with the profile running
   

2. Get a screen shot of the Joystick control with the profile running in Target.
   
   

Or a list of what’s in that panel when the profile is running.

3. Get a screen of the set up page in BMS.
   
   Or list the controller and the Current Profile Selected.

4. A screen shot of your devicesorting.txt
   
   Or a complete list of what’s inside the file. The best way to open it is with notepad ++

Button Layout Pics:

An Overlay you can print out and place over your throttle see instructions in the post below.

TLDR: Instructions:

1. Download the files from the dropbox. The popular paddle swap version of the profile is included.

https://www.dropbox.com/sh/6ne27l56c1iuyiv/AAD4Rl8i1rgaB2mO3AHjHX4Ba?dl=0

2. Copy BMS 437 Morphine Full.key and Falcon BMS User.CFG into the BMS / User / Config folder.
   

3. Start Morphine BMS 437.tmc in Target.
   

4. Start The BMS Launcher and select Launch without any setup override.
   

5. Click Ok
   
   You will have to keep this selected at all times! If you don’t the launcher will overwrite your settings including the devicesorting.

6. Load the profile in Game
   

7. Exit the Game and edit the DeviceSorting.txt file So that the thrustmaster combine is at the top and the Cougar MFDs are in this order.
   
   Then add the following line of code
   set g_nHotasPinkyShiftMagnitude 512
   to the file falcon bms.cfg or Falcon BMS User.cfg
   

8. Keep “Launch without any setup override” selected / checked, and relaunch the game. Then go back into the settings and select the Thrustmaster Combine as your controller
   

9. Hit the “Advanced” Button to setup the Flight Controls
   
   And Then Setup Avionics
   

At this point the profile should be working.

Had you just set up everything in the launcher, you probably all ready by RTB twice and about 3 beers deep.

But you’re a stubborn bastard, and now you get to spend the next hour and half just trying figure out why the profile isn’t working for you.

If you have to spend more then 15 mins to get this profile or Target to work, you’re better off just using the launcher to configure everything.

I just happen to like the layout. So for the ride or die Morphine’s people, I cleaned up and commented the Keyfile, and the target profile.

I also tweaked the curves on the slew nub. If you wish to change the curve or sensitivity, the comments in the target file will be helpful.

Changing the magnitude of the pinky shift to 512 was necessary because of BMS now supports 128 DX buttons per joystick. If we had not done this, the shift buttons would have conflicted with the Cougar MFD’s. If you have other DX devices if you may have conflicts.

If you all ready have items in your Falcon BMS User.cfg file, you can just add the line.
set g_nHotasPinkyShiftMagnitude 512 to the file

Kidding aside I do like the profile and some of the virtual axis, ect. However, with every version of BMS there are less free keys available.

Sooner or later, It would be easier to recreate this profile using DX keys. I’ve seen an interesting approach on the DCS boards that may allow us to take this profile beyond the 32 DX limit of target. Which would greatly simplify updates. https://forum.dcs.world/topic/144048-thrustmaster-combined-full-dx-mapping-extending-the-32-dx-buttons-limit/

edit: updated target files to fix master arm.
edit: fixed bug in paddle swap tmc file. updated dropbox link.

@saltyexxer said in Morphine’s Profile For 4.37:

Is there an image anywhere illustrating the button and keyboard mappings (on the stick/throttle)?

I peeked in the dropbox for older versions, and the last one I see with any such images is for bms 4.34. Is it still valid?

Thanks in advance

The profile is still the same as 4.34. The only thing that’s changed is the coolie hat on the throttle and those are just views and zoom. The coolie hat is really easy to customize / change too. Just open the .key file and assign what ever you want to the coolie hat. I’ll add a pic to the drop box later this week though.

The profile is based on the default BMS full keybinds. We just added one or two additional binds. Which is all handled on the hotas. You can refer to keyboard reference image included in the docs folder in BMS, if you have questions about the keyboard key binds.

I decided to integrate the profile with the default keyboard layout because, it makes it easier to teach someone using a common keyboard layout.

Step 5. Place the overlay on top of throttle. Align the switches within the circles like so.

Step 6. Push down on the paper the Switches should emerge from where you cut across the circles.

If the switches do not align within the circles there is a scaling issue with your print. You may have to play with your printer settings or try using the PDF or PNG. The printing out process can be frustrating and there is no exact science to it. I created this file in GIMP and also have a Photoshop file of this profile. If your struggling and want access to those let me know via PM and we can work out a way to transfer them, as they are large files .

If the overlay is the correct size. You can cut out the holes with an hobby knife and tape the overlay down.

You could also take these files and have them either laser cut and etched or printed on foam board. Which is probably how these result we’re achieved.

https://forums.x-plane.org/index.php?/forums/topic/185629-thrustmaster-hotas-warthog-switch-panel-setup/

I’ve created some overlays you can print out and place on your throttle.

The files for the overlays are located within the dropbox for the profile on the first page.

This is the link for the overlay with black text and a white background.

https://www.dropbox.com/s/eia89wh3ri63tri/Throttle Overlay PDF White Background.pdf?dl=0
https://www.dropbox.com/s/zyt34n95qq3qqne/Throttle Overlay White.png?dl=0

I highly recommend using the white background to test and fit the overlay. It will save a lot of black ink / toner. You may have to play with your printer settings to get the files to scale properly

I tend to get the best results by making sure the margins are turned off and image is printed at 100% Scale in Portrait mode.

First Print out the png or PDF, Which one will work best will depend on your printer, ect. You may have to try both to get it to work.

Step 2. Cutout the thin exterior lines you should end up with something like this

Step 3. Fold then cut out the interior boxes.

When your done you should end up with something like this.

Step 4. For you first few print outs the goal is to just make sure the overlay is the correct size. We do not want to spend a lot of time cutting out all the circles for switches just yet. So we are just going to cut 2 lines through the center of each circle, making a bullseye. This can be done with a box cutter or an xacto knife.

You each of the switch circles to look something like this.

They dont have to perfect, At this point we are just trying to make sure that the print out is the correct size.
When you’ve cut all the switch circles the overlay should look like this.

TBD in the next post

@saltyexxer said in Morphine’s Profile For 4.37:

Is there an image anywhere illustrating the button and keyboard mappings (on the stick/throttle)?

I peeked in the dropbox for older versions, and the last one I see with any such images is for bms 4.34. Is it still valid?

Thanks in advance

The profile is still the same as 4.34. The only thing that’s changed is the coolie hat on the throttle and those are just views and zoom. The coolie hat is really easy to customize / change too. Just open the .key file and assign what ever you want to the coolie hat. I’ll add a pic to the drop box later this week though.

The profile is based on the default BMS full keybinds. We just added one or two additional binds. Which is all handled on the hotas. You can refer to keyboard reference image included in the docs folder in BMS, if you have questions about the keyboard key binds.

I decided to integrate the profile with the default keyboard layout because, it makes it easier to teach someone using a common keyboard layout.

@fvelazdem said in Morphine’s Profile For 4.37:

I repeat it again, there is something that conflicts when I press Paddle and the configuration stops working on my computer

There is nothing in the either the target files or the key which “conflicts” when you press the paddle. The cause of your problems is that BMS is not correctly configured to run the profile, and or Target is not working correctly on your system.

I will take the time to prove this mathematically as your statement implies that there is some underlying issue problem with the profile. Which there is not.

Let’s look at the directx / joystick buttons binds in the 4.35 and 4.37 .key file.

The code for DMS right is the same for both 4.35 and 4.37

SimDMSRight 11 8 -2 0 0x0 0 "DMS RIGHT"

This says when the joystick button 12 from the first controller in Devicesorting.txt is pressed, then DMS right is pressed in the sim.

BMS sees joystick button 12 as “11” because it transforms button 1 to 0 and counts up from 0. E.G. Joystick button 1 = BMS Button 0, and Joystick Button 10 = BMS Button 9.

The BMS joystick button shift function works by increasing the joystick button by a fixed value.

For the 4.37 profile we set the shift value to 512, with the following line of code in the user.cfg file.

set g_nHotasPinkyShiftMagnitude 512

With this line of code, when we press and hold the pinky or paddle (depending on the version of the profile) and press DMS right on the warthog stick. The sim inputs BMS button 11 + 512, which is BMS buttons 523.

The 4.37 key file tells the sim that BMS button 523 should increment the way point up.

SimNextWaypoint 523 8 -2 0 0x0 0 "DMS RIGHT + PINKY = NEXT STPT"

The 4.35 profile is based on a 256 joystick shift. Meaning when the paddle / pinky is held and you press DMS right, the sim inputs BMS button 11 + 256 = BMS button 267,

267 also happens to be, by no coincidence, the binding to increase the way point in the 4.35 version of the key file.

SimNextWaypoint 267 8 -2 0 0x0 0 "DMS RIGHT + PINKY = NEXT STPT"

If everything was setup properly for 4.37 and you used the 4.35 key file. Then you pressed paddle + DMS nothing should happen. As nothing is assigned to BMS button 523 in the 4.35 keyfile.

If you have setup everything correctly for 4.37 and are using the 4.35 key file. Then, you press paddle + DMS right and the way point increases. Then the sim is seeing BMS button 267.

and you haven’t finished the setup
as

set g_nHotasPinkyShiftMagnitude 512

is greater than 267.

@fvelazdem said in Morphine’s Profile For 4.37:

The only conclusion I can get is that BMS 437 Morphine Full.key has a conflict with both *.tms and this is the reason why the new profile do not work proppely.

I downloaded the target scripts and the Morphines BMS 437 full from the dropbox again.
https://www.dropbox.com/sh/6ne27l56c1iuyiv/AAD4Rl8i1rgaB2mO3AHjHX4Ba?dl=0

They key file and the target scripts both work in BMS 4.37.

From your feedback I can conclude, that your difficulties are self inflicted and a result of one or more of the following.

1. You have either edited or saved over the BMS 437 Morphine Full.key file.

2. You have not installed in the profile correctly. If the shift function are the only thing not working. You skipped the last step in the install process, setting shift magnitude correctly. by adding the following line of code

set g_nHotasPinkyShiftMagnitude 512 

to either file falcon bms.cfg’ or Falcon BMS User.cfg

3. You are trying to the use the .key file meant for BMS version 4.37 in a earlier version of BMS. This keyfile wil not work in earlier versions of BMS because of changes to the Joystick code within BMS.

The new profile and key file do work properly in BMS 4.37. I have had multiple people test it as well.

You are the only person I know with this persistent of a problem with it.

If you can’t get it to work, don’t use it. All I ask is that you please stop saying that it does not work. As I have all ready posted a video of the profile working and have gone to the trouble of having others test it out for me.

@fvelazdem said in Morphine’s Profile For 4.37:

In addition to all of this, the target version I am using is: V.3.0.20.826
Last point: I am using the following TMC file and key file:
Warthog_BMS_Full_5_434_Paddle.tmc
Morphine_BMS_435_full.Key
with this everything works. I am not using f6 MFD 1 or 2.

1. You should update Target. The script for BMS 4.37 is was written in the latest version of target 3.0.21.910
   The script runs and performs as expected with this version of Target.

2. Are you trying to use the 4.37 profile in BMS 4.35?

@fvelazdem said in Morphine’s Profile For 4.37:

In the same way, CMS or TMS do not work. I tried to launch flares and nothing happened or to activate the ECM. TMS in the same way.
Obviusly I downloaded from your last link.

I just downloaded the paddle swap from the dropbox, Started it in Target and it ran perfectly fine.

I recorded a video of BMS and the Thurstmaster Device Analyzer running. So that you can see the button press’s happen in real time. DMS + paddle functions as expected so does CMS and all of the other HOTAS commands.

I would try downloading the target files and the .key file then follow the steps on the first page. Be sure to recheck the Devicesorting.txt too. As the game will change it if you happen to start BMS without target running.

If that doesn’t work try I’ll need some more information to try and help you.

1. Get a screen shot of Target with the profile running
   

2. Get a screen shot of the Joystick control with the profile running in Target.
   
   

Or a list of what’s in that panel when the profile is running.

3. Get a screen of the set up page in BMS.
   
   Or list the controller and the Current Profile Selected.

4. A screen shot of your devicesorting.txt
   
   Or a complete list of what’s inside the file. The best way to open it is with notepad ++

@Finger-Jam-0 said in Morphine’s Profile For 4.37:

I see “Thrustmaster Virtual Game Controller (root)”.

ouch. I though we’d seen the last of this…

“Thrustmaster Virtual Game Controller (root)”.
This a sign that Target isn’t working properly on your system. Target works by hiding the stick and throttle from your system and creating a virtual joystick, aka Thrustmaster Combine. Root shows up when target can’t hide either the stick or the throttle

It can be really hard to fix this issue because it could be be caused many different things.
The first thing I would do is

1. unplug the HOTAS,
2. install the drivers again.
   https://support.thrustmaster.com/en/product/hotaswarthogflightstick-en/

When it prompts you to plug in the device, change which USB ports the stick and throttle are plugged into. You can just flip flop them too. This may cause your system to recognize the HOTAS and it’s associated drivers correctly.

If it still doesn’t work. There maybe some software interfering with TARGET. The windows store, which runs in the background, was one that gave many people troubles. You can disable it and anything else you don’t from running in the background and restart.

I even had issues with Discord and Target when I was updating the profile. The Thrustmaster script editor wouldn’t load scripts with Discord running.

If all else fails you can just put “Thrustmaster Virtual Game Controller (root)”. At The top of device sorting and the stick and throttle at the bottom.

something like
“Thrustmaster Virtual Game Controller (root)”.
MFD 1
MFD 2
Rudder Pedals, if you have them
Joystick
Throttle.

Just make sure you select the axis for the virtual root controller in the setup page.
That may work, no guarantees though. I also haven’t checked the compatibility with 4.36 too.

@Finger-Jam-0 said in Morphine’s Profile For 4.37:

I don’t seem to have a “Thrustmaster Combined” in my DeviceSorting.txt file.

With the scripting running open the windows joystick control panel

You can also open the panel by clicking on the windows button in the lower left and typing joy.cpl

What do you see listed in the windows joystick control panel.

The only devices should be the thrustmaster Combined, the MFD’s (if you have them) and any other USB joysticks you have plugged in. Such as rudder pedals, ect.

If you can grab a screen shot of the target interface with the profile running that would be helpful.

You can grab a screen shot by pressing the windows key on your keyboard shift and s at the same time.

@fvelazdem

There was this really weird bug with the paddle swap profile. It was some kind of compiler issue related to the comments. Anyway, I fixed it, tested all the functions then updated the dropbox link on the front page. It’s also included below. Thanks for your feedback, and helping to get this sorted out.

https://www.dropbox.com/sh/6ne27l56c1iuyiv/AAD4Rl8i1rgaB2mO3AHjHX4Ba?dl=0