Morphine's Profile For 4.37
-
Hi Gastone,
I followed your instructions, I modified the device Sorting and run your TMC file in Target and your Key File in BMS.
When I fly everything run OK , TMS, DMS,etc. But as soon as I push Paddle swap , for example: Press and Hold Paddle, Press DMS right. nothing of the Joystick work properly. In the case of the throttel is just the opposite still work perfect.
By the way I openned Windows after run TARGET and everything looks ok, it shows what you said.
Not said before but I also included set g_nHotasPinkyShiftMagnitude 512 in Falcon BMS User.cfg
Not sure if you check the functioning of the Paddle in your files, I guess so… no idea why this mess
-
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
-
I don’t seem to have a “Thrustmaster Combined” in my DeviceSorting.txt file.
-
@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.
-
@Gastone Thanks to you for provide us with this profile, at least for me is a big help.
You deserve a bier!!! I will test tomorrow and let you know., today is a it complicate
-
@Gastone I see “Thrustmaster Virtual Game Controller (root)”.
BMS 4.36
Throttle FW: 23
Stick FW: 12
-
@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 throttleIt can be really hard to fix this issue because it could be be caused many different things.
The first thing I would do is- unplug the HOTAS,
- 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. -
Gastone
As promised I test and sorry for tha bad news, but still not working. Now, when I press Paddle nothing start to be mad like in the past, but nothing happen. I mean, the waypont do not increase for example.
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.
-
@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.
-
Get a screen shot of Target with the profile running
-
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.
-
Get a screen of the set up page in BMS.
Or list the controller and the Current Profile Selected. -
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 ++
-
-
Sorry forthe delay, I was out. Here you have what you requested:
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.Keywith this everything works. I am not using f6 MFD 1 or 2.
-
@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.-
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. -
Are you trying to use the 4.37 profile in BMS 4.35?
-
-
Thanks Gastone,
I will try to update Target and test again
What I am doing is use the 4.35 profile for BMS 4.37 with the version of target that I mentioned before, everything works ok.
-
Already Installed last version of TARGET. I test:
1.- Devicesorting you Provided
2.- Load Throught new version of target :Morphine BMS 437 Paddle Swap.tmc
3.- Load in BMS: BMS 437 MORPHINE FULL.As soon I press and mantain paddle nothing work properly.
Then, I test:
1.- My previous Devicesorting
2.- Load Throught new version of target :WarthogBMS_Full_5_434_Paddle.tmc
3.- Load in BMS: Morphine_BMS_435_full.Keyeverything works correct. This is a mysteri
-
Gastone,
I compared the two files line by line:
Morphine BMS 437 Paddle Swap.tmc
Warthog_Full_5_434_Paddle.tmcAnd I did not found differences.
Based on that, I load through Target: Morphine BMS 437 Paddle Swap.tmc and In BMS: Morphine_BMS_435_Full.Key (mine).I test it and everything Ok, paddle, etc.
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.
-
@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=0They 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.
-
You have either edited or saved over the BMS 437 Morphine Full.key file.
-
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
- 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.
-
-
Thanks Gastone.
I didn’t want to bother you, when I said it didn’t work I was obviously referring to my installation. If it has bothered you, I apologize.I have done the installation again from the new files from the link that you have put and I have made sure that everything is fine. I have tested it again and when I press Paddle everything goes wrong, every time I press something on the joystick it does something wrong.
I don’t think you understood what I said. I use the version: WarthogBMS_Full_5_434_Paddle.tmc
with the file: Morphine_BMS_435_full.Key
both from previous versions and everything works correctly in the current BMS: BMS4.37.Anyway, thank you but I am not going to try again to make the new version that you have created work and I will continue with the one that I have managed to make work.
Regarding the reasons that you state why it does not work in my installation, allow me to answer you:
1.- No, I have not edited that file.
2.- That line is in the Falcon BMS User.cfg
3.- I have never said at any time that I have used files from Version 4.37 in previous versions.The proof is that I have done the installation again and everything remains the same.
It can be concluded that the problem is mine since there have been many people who have tried it and it works. I ask you, please, do not attribute it to the fact that I have done the installation wrong or that I have overcopied files, because it is simply not true. I repeat it again, there is something that conflicts when I press Paddle and the configuration stops working on my computer
Thanks and I hope in the future if you launch a new version I will be able to use it.
-
@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
asset g_nHotasPinkyShiftMagnitude 512
is greater than 267.
-
Thanks Gastone,
What you have explained makes sense and that is why I have thought again, I have reviewed the entire installation and apparently everything is correct.
I have “set g_nHotasPinkyShiftMagnitude 512” in Falcon BMS User.cfg and I thought that maybe this is causing problems, it shouldn’t, but just in case I tried the following:
I have deleted “set g_nHotasPinkyShiftMagnitude 512” from Falcon BMS User.cfg
I have added this line directly in Falcon BMS.cfg.I have tried and it has worked!!!
I don’t understand why the setting in falcon BMS user.cfg did not override the ones in Facon BMS.cfg . That should be an issue. I will post it at the thecnical support to let see.
I want to thank you for your patience all this time.
-
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
-
@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.