A Guide to Morphine’s Profile for BMS 4.33 and Beyond
-
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
-
Not to be a pest but your files are still showing 4.34. or am I missing something? Appreciate the support
It was the wrong link. Fixed. Thanks for the find, please if u see anything please let me know so I can fix it. My version controls for this stinks so things fall through the cracks.
New link above and here
https://www.dropbox.com/sh/7x71pt7wgs2v8ie/AADX_4g3QJY6eHPcMGVPBB4ia?dl=0%5B -
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.Thanks Gastone!!. I will wait until “paddle switch” is updated, is the one I use.
-
Thanks Gastone!!. I will wait until “paddle switch” is updated, is the one I use.
It’s done all ready
https://www.dropbox.com/sh/7x71pt7wgs2v8ie/AADX_4g3QJY6eHPcMGVPBB4ia?dl=0%5B -
It’s done all ready
https://www.dropbox.com/sh/7x71pt7wgs2v8ie/AADX_4g3QJY6eHPcMGVPBB4ia?dl=0%5BThanks a lot, Gastone!!
-
Everything is fine but I have a problem when I push Nosewheel Stearing Button (STICK: PINKY SWITCH (DX SHIFT)) because any button or switch works afterward.
-
Everything is fine but I have a problem when I push Nosewheel Stearing Button (STICK: PINKY SWITCH (DX SHIFT)) because any button or switch works afterward.
Could you be more specific about your problem? Which version of the profile are you using and when are you having problems? Have u set up the devicesorting.txt as described on the first page?
-
Everything is fine but I have a problem when I push Nosewheel Stearing Button (STICK: PINKY SWITCH (DX SHIFT)) because any button or switch works afterward.
I had the same problem. In my case it was caused by an incorrect pinky shift magnitude setting. It was set to 96, which clashed with the keyfile’s assumption of a 256 jump.
Take a look at “Falcon BMS.cfg” in the config folder. At the very bottom, under Dev settings, check if there’s a line like:
set g_nHotasPinkyShiftMagnitude 96 // SETUP OVERRIDE
Removing that (or setting it to 256) fixed the issue for me. -
I had the same problem. In my case it was caused by an incorrect pinky shift magnitude setting. It was set to 96, which clashed with the keyfile’s assumption of a 256 jump.
Take a look at “Falcon BMS.cfg” in the config folder. At the very bottom, under Dev settings, check if there’s a line like:
set g_nHotasPinkyShiftMagnitude 96 // SETUP OVERRIDE
Removing that (or setting it to 256) fixed the issue for me.Could you paste here the last lines of Falcon BMS.cfg under Dev settings? Thanks you
Enviado desde mi Redmi Note 9 Pro mediante Tapatalk
-
Could you paste here the last lines of Falcon BMS.cfg under Dev settings? Thanks you
Enviado desde mi Redmi Note 9 Pro mediante Tapatalk
////////////////////////////////////////////////////
// Dev Settings (not available in the Config.exe) //
////////////////////////////////////////////////////// set g_sPathFlightModelManager “…\Flight Model Manager\Flight Model Manager.exe” // Allows to open acdata with FMM from editor. Uncomment and set to corresponding program folder to enable.
// set g_sPathMissileDataManager “…\Missile Data Manager\Missile Data Manager.exe” // Allows to open misdata with MDM from editor. Uncomment and set to corresponding program folder to enable.
// set g_sPathVehicleDataManager “…\Vehicle Data Manager\Vehicle Data Manager.exe” // Allows to open veh files with VDM from editor. Uncomment and set to corresponding program folder to enable.
set g_bLabelShowDistance 1 // When turned On, labels also display distance in nm
set g_nNearLabelLimit 100 // Sets the near label limit
set g_bSmartCombatAP 1 // Enables the Combat Autopilot to shoot AA missiles
set g_nNumberOfSubTitles 10 // Determines the maximum number of simultaneously displayed subtitles
set g_nSubTitleTTL 10000 // Governs the time a radio subtitle is drawn
set g_fSubtitleWrapWidth 0.6 // Radio subtitle text line width before it gets wrapped, 0.0 (nothing) to 2.0 (full view width)
set g_bRealisticMavTime 1 // Enables realistic Maverick seeker head gyro spool up time of 3 minutes
set g_fMavFOVLevel 4 // These variables control the amount of zoom of the EXP and FOV modes on the Maverick
set g_fMavEXPLevel 2.0 // These variables control the amount of zoom of the EXP and FOV modes on the Maverick
set g_bNoRPMOnHud 1 // Removes the RPM indication on your HUD, as in the real aircraft
set g_fAIRefuelSpeed 1 // Sets a multiplier factor so AI refuel faster on the boom
set g_bCanopyOpenForRampStarts 1 // Option to have the canopy open at mission start when you choose RAMP
set g_bUsePsTracers 1 // Uses the particle system for tracers
set g_bAnyWaypointTask 1 // Allows you to assign any task to any waypoint
set g_bAIGloc 1 // Toggles AI GLoc
set g_bAIjamLogic 0 // Changes to the AI jamming usage (no support)
set g_bScramble 1 // Allows scramble missions
set g_b3DClickableCursorChange 1 // Setting this enables the cursor to let the pilot know he is over a clickable area of the 3D pit
set g_sRadioStandardCol “0xFFFF0000” // Sets radio standard comm subtitles to bright blue
set g_sRadioTowerCol “0xFF00FF00” // Sets radio tower comm subtitles to bright green
set g_sRadioflightCol “0xFF0000FF” // Sets radio flight comm subtitles to bright red
set g_nTrackIRTimeout 1000 // The time (in ms) without input after which TrackIR deactivates itself and relinquishes control to alternative devices
set g_sThreatCircleColor_RadarHigh “0xFF0000” // The color of the UI map thread circle for “Radar High”, set as hex, “0xBBGGRR”
set g_sThreatCircleColor_RadarLow “0xFF0000” // The color of the UI map thread circle for “Radar Low”, set as hex, “0xBBGGRR”
set g_sThreatCircleColor_ADAHigh “0xFF00FF” // The color of the UI map thread circle for “ADA High”, set as hex, “0xBBGGRR”
set g_sThreatCircleColor_ADALow “0xFF00FF” // The color of the UI map thread circle for “ADA Low”, set as hex, “0xBBGGRR”
set g_nThreatCircleContrast_RadarHigh 40 // The strength of the color mixing if 2 or more threat circles of type “Radar High” overlap. Range 0-100
set g_nThreatCircleContrast_RadarLow 40 // The strength of the color mixing if 2 or more threat circles of type “Radar Low” overlap. Range 0-100
set g_nThreatCircleContrast_ADAHigh 40 // The strength of the color mixing if 2 or more threat circles of type “ADA High” overlap. Range 0-100
set g_nThreatCircleContrast_ADALow 40 // The strength of the color mixing if 2 or more threat circles of type “ADA Low” overlap. Range 0-100
set g_bSaveLegacyDb 0 // Synchronize the bin files to match the xml files when the game/editor is started
set g_bEnableTTS 1 // If set, globally enables the Text-To-Speech (TTS) functionality
set g_nTTSSpeedAdjust 0 // Sets the TTS talking speed, default speed is 0, range -10 to 10
set g_sPPTRingColor “0x0000FF” // The color of the UI map PPT rings, set as hex, “0xBBGGRR”
set g_nPPTRingWidth 1 // The width in pixels of the UI map PPT rings//////////////////////////////////////////////////////////
// Debug/Dev Settings (not available in the Config.exe) //
//////////////////////////////////////////////////////////set g_bActivateDebugStuff 0 // Debug Setting - Master setting for all subsequent settings, host controlled in MP
set g_nShowDebugLabels 0 // Debug Setting
set g_bCampLabels 0 // Debug Setting
set g_bAIprofile 0 // Debug Setting
set g_bShowMipUsage 0 // Debug Setting
set g_b3DClickableCockpitDebug 0 // Debug Setting
set g_bFake3dpit6DOF 0 // Debug Setting
set g_bDevelopmentCallbacks 0 // Dev Setting
set g_bEnableCombatAP 0 // Dev Setting
set g_bHotasDgftSelfCancel 0 // SETUP OVERRIDE
set g_b3DClickableCursorAnchored 1 // SETUP OVERRIDE(Already removed the shift magnitude here)
-
(Already removed the shift magnitude here)
Thanks, I had set g_nHotasPinkyShiftMagnitude 160 // SETUP OVERRIDE. I have changed 160 and put 256 and it’s working fine.
Enviado desde mi Redmi Note 9 Pro mediante Tapatalk