A Guide to Morphine’s Profile for BMS 4.33 and Beyond
-
Yes, I made that initial mistake on my new PC (plugging in HOTAS before being asked) so I completely uninstalled the drivers and software and reinstalled using a different USB Port when prompted to plug in the hotas.
Still did not fix the issue and yes I’ve loaded the keyfile in game per instructions…
About half of the stick and throttle functions work the other half have no keys assigned.
Load the keyfile in game per the instructions on the first page. 2, kill the windows store, uninstall the teamspeak joystick plugin.
-
Kilo,
I fixed this problem on my Windows 10 PC by going to settings/apps/apps & features. There click on microsoft store and advanced options and turn off background apps under app permissions. I haven’t had the issue since. -
With Morphines Profile for 4.33 and beyond, is the Paddle on the throttle just for centering TIR, and if held, turning off Auto pilot? Reason I ask, I am in the TFR training mission, and it says to use the paddle switch to cancel fly up. With this profile, what is programmed to do that function?
-
Quick paddle push to recenter TrackIR. Hold the paddle to temporarily disable autopilot/TFR fly up
-
Is there any update for Falcon BMS 4.35?
Or the 4.34 profiles still works?
I’m trying to load the *.tmc, but don’t hide the joystick, throttle and rudder devices.
The TFRPRudder don’t hide after to run the script.
Best regards.
-
I disconnected and connected all devices and I cannot hide the rudder pedals. What do I suppost to do do solve this and combine the controls?
-
I’m tired. I reinstall all drivers and softwares, unplugged and plugged all USBs, to run the profile and the T-Rudder don’t combined with throttle and joystick. I don’t know how to fix it.
-
I don’t have the rudder pedals, but the profile working for me like worked for 4.34
-
I commented the //Configure(&TFRPRudder, MODE_EXCLUDED); and didn’t show any errors but the controls are not combined.
The rudder axis and toe brakes don’t work.
How to setup the rudder axis and toe brakes in this profile?
Best regards.
-
I fixed. I uncommented the rudder and setup the rudder axis and toe brakes in the advanced options. Thanks all.
-
I disconnected and connected all devices and I cannot hide the rudder pedals. What do I suppost to do do solve this and combine the controls?
The profile is not supposed to hide the rudder pedals. It needs to be visible to BMS to be bound in game. If you’re getting thrustmaster Root in the joystick menu, try disabling the Microsoft store from running in the background.
To disable the Microsoft store from running in the background. In windows 10, Hit the start button, type background Apps. Turn off everything you don’t need, reboot. See if target is functioning properly. Target should hide your joystick and throttle when running.
The teamspeak joystick plugin will break Too.
The profile will output errors if excluded hardware is not detected. It’s fine and will run as expected in this case.
-
Just as an FYI, there are some changes to the new keybinds in 4.35 that effect this profile. Nothing big so far, It’s just the The APU switch and the motor switches. I’ll get to fixing in the next few days.
-
Hey Gastone,
you are doing an excellent job with this profile - thx for this.Regarding some changes in 4.35 I also noticed that “Parking break” button stoped working. Is it the example of this changes or my Warthog decided to give up?
Regards
-
Hey Gastone,
you are doing an excellent job with this profile - thx for this.Regarding some changes in 4.35 I also noticed that “Parking break” button stoped working. Is it the example of this changes or my Warthog decided to give up?
Regards
Yeah the parking breaking was changed too so it won’t work with the old morphine key file. There’s a couple of other things too. But most of the HOTAS functions should work.
It takes a bit to update the files, because Target translates many of the switches to keyboard switches; and BMS keeps adding things to the Basic Map while changing callbacks . So I have to make sure that the switches are not double bound and the call backs are not depreciated. So it takes a minute to reintegrate everything.
-
Profile is updated for 4.35.
You need to use the new .Key file and TMC. And rebind all your axis,
Let me know if you have any issues. I’ll get to a paddle switch latter.Get it Here: https://www.dropbox.com/sh/s4x2hexndkxuagy/AADQaHaL8Ph1tccR-zsXz5ZFa?dl=0
Or the link on the Front Page with the instructions.Of note: I commented the hell out of the Target code to make it easier to update in the future. It would be a good example to learn from, if u wanted to use target in another game.
//APU Switch // Switch AFT MapKeyIO(&Throttle, APUOFF, PULSE+L_SHIFT+L_CTL+L_ALT+'e', PULSE+L_ALT+L_CTL+'u'); // Switch AFT = EPU Off // SimEPUOff = CTRL + ALT + u = 0X16 6 // Pink Shift + Switch AFT = EPU ON // SimEpuOn = SHFT + CTRL + ALT + e = 0x12 7
Here we see what the APU switch does when its hit aft. This is the code target uses
MapKeyIO(&Throttle, APUOFF, PULSE+L_SHIFT+L_CTL+L_ALT+‘e’, PULSE+L_ALT+L_CTL+‘u’);When the Key is hit aft it Pulses Left Alt + CTRL and the U key.
If the Shift Button is held it pulses Shift + CTRL + ALT + E
The shift state is always first.Below the target code is what we want ctr +alt + u to do. In this case move the EPU switch in the cockpit to the off postion. This section of code and anything with // in front don’t do anything. They are just notes.
// Switch AFT = EPU OffThe next part:
// SimEPUOff = CTRL + ALT + u = 0X16 6
the first part; SimEPUOff is the call back BMS uses in the keyfile to trigger the event, followed by the Key commands in plain text and finally the Hex code and modifier that invokes the call back in the .key file. -
Gastone! Thanks for commenting everything. I’ve never looked at the script even though I’ve been using it since I started flying BMS last year!
Your comments on the china hat gave me an idea after I noticed Coolie Switch Up and Down were now functioning as FOV adjustment in your new key file.
I have FOV adjustments disabled in my config file so that I’m not randomly changing my view when using the mouse wheel for instruments. So I changed the slider axis to CSU/CSD like the china hat.
Of course that means the slider can’t be used anymore as an axis… but, is it possible to change the slider to send gear up and gear down callbacks at each end of its range of motion? It would be an elegant gear lever!
Thanks!
-
Gastone! Thanks for commenting everything. I’ve never looked at the script even though I’ve been using it since I started flying BMS last year!
Your comments on the china hat gave me an idea after I noticed Coolie Switch Up and Down were now functioning as FOV adjustment in your new key file.
I have FOV adjustments disabled in my config file so that I’m not randomly changing my view when using the mouse wheel for instruments. So I changed the slider axis to CSU/CSD like the china hat.
Of course that means the slider can’t be used anymore as an axis… but, is it possible to change the slider to send gear up and gear down callbacks at each end of its range of motion? It would be an elegant gear lever!
Thanks!
There were a couple of errors with last night publish, nothing critical. But I do recommend re downloading both files. There was a typo in the slew commands that may make it a bit jumpy in the X axis.
FYI, those FOV changes were published by mistake, It’s just something I do in my own setup. But you can change the Coolie using the in game menu to what ever u like. Just find the command u want in the list and click on it then press the coolie hat. Same goes for all the DX buttons.How do people like the curve on the slew? I’m not happy with myself so I’ve been playing with it to try and make it less jumpy.
MapAxis(&Throttle, SCX, DX_XROT_AXIS); SetSCurve(&Throttle, SCX, 0, 2, 0, 15, -10); //Negative number at the end reduces the sensitivity of the cursor X-axis MapAxis(&Throttle, SCY, DX_YROT_AXIS); SetSCurve(&Throttle, SCY, 0, 2, 0, 15, -10); //Negative number at the end reduces the sensitivity of the cursor Y-axis ```This is my latest attempt. Feel free to change to your liking too. If you don't want to muck about with target. Comment out the set curve options. Like so
MapAxis(&Throttle, SCX, DX_XROT_AXIS);
// SetSCurve(&Throttle, SCX, 0, 2, 0, 15, -10); //Negative number at the end reduces the sensitivity of the cursor X-axisMapAxis(&Throttle, SCY, DX_YROT_AXIS);
// SetSCurve(&Throttle, SCY, 0, 2, 0, 15, -10); //Negative number at the end reduces the sensitivity of the cursor Y-axisIf you want to use Target to fine tune the axis response we do it here
SetSCurve(&Throttle, SCY, 0, 2, 0, 15, -10); //Negative number at the end reduces the sensitivity of the cursor Y-axis
I break this down further below. This says; we're calling for an S curve on Throttle slew control Y axis.
SetSCurve(&Throttle, SCY,
This defines the response of the curve,
0, 2, 0, 15, -10
The 2 is the center dead zone and works as described. You have to move the axis more than 2% from the center before an input is registered. "15" is the Size of the curve. The values go from -20 to +20\. Negative values make the axis more sensitive around the center, while positive values provide better control in the center position. The next "0" Is the Right Dead zone, it does the same thing as left just in the opposite direction. -10 is the scale of the axis. The values go from -20 to 20\. A negative number reduces the maximum input by fixed amount. RE the gear lever: It's do able with target.
KeyAxis(&Throttle, THR_FC, 0,AXMAP2(LIST(0,10,90,100), PULSE+‘g’,0, PULSE+‘g’))
FYI the target script manual is full of handy tricks like that. [https://ts.thrustmaster.com/download/accessories/pc/hotas/software/TARGET/TARGET_Script_Editor_Basics_v1.5_ENG.pdf](https://ts.thrustmaster.com/download/accessories/pc/hotas/software/TARGET/TARGET_Script_Editor_Basics_v1.5_ENG.pdf)
-
Paddle Swap is done, U just need TMC. It uses the same .key as the default. I just used target to do the swap. Works much better this way. Less stuck keys.
https://www.dropbox.com/sh/7x71pt7wgs2v8ie/AADX_4g3QJY6eHPcMGVPBB4ia?dl=0%5B
-
Thanks for that info! While you were typing all that up for us, I figured it out, too
I added callbacks to the key file for gear up and down so that each direction of the slider is unique.
//Slider as a gear handle
KeyAxis(&Throttle, THR_FC, 0, AXMAP2(LIST(0,10,90,100), PULSE+L_CTL+L_SHIFT+‘l’,0, PULSE+L_ALT+L_SHIFT+‘l’)); -
Not to be a pest but your files are still showing 4.34. or am I missing something? Appreciate the support