A Guide to Morphine’s Profile for BMS 4.33 and Beyond
-
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
-
I am pulling my freaking hair out trying to run this script. It ran beautifully for a week and has now stopped functioning and has given me the dreaded “device root issue” I have reinstalled Target and the warthog drivers so many times over the past 3 days each time alternating the install order and USB ports trying to fix it and the only thing it accomplished is damaging my sanity. I went from “device root” no pedals detected, to “device root” only pedals detected, to “device root” nothing detected. I’m tapping out. Thank you for all you do Gastone, I truly appreciate your work, but Thrustmaster’s software is just too much of an unstable bag of excrement for me to deal with.
Edit: Now that I have smoked a cigarette and calmed down some, let me ask on last question before I pull the ejection handle. I currently use the Warthog with the TFRP Pedals. Here’s the one weird observation I made when installing the drivers multiple times. When I run the listed installer for the Warthog it says it is installing drivers for the TMWT-Pedals. When it’s done, the start menu icon for them is an icon of rudder pedals. Then I install the unified drivers package that’s listed for the pedals and then a new start menu icon of the joystick appears. WTF is this happening backwards? When I run joy.cpl the device order shows pedals at the top of the list lending evidence that some weird stuff is happening, but I don’t know if that’s anything conclusive.
Anyone see anything like this before? Or are there any Warthog+TFRP users out there that have some guidance on the install order and plug in order for the devices?
-
@Lennox:
I am pulling my freaking hair out trying to run this script. It ran beautifully for a week and has now stopped functioning and has given me the dreaded “device root issue” I have reinstalled Target and the warthog drivers so many times over the past 3 days each time alternating the install order and USB ports trying to fix it and the only thing it accomplished is damaging my sanity. I went from “device root” no pedals detected, to “device root” only pedals detected, to “device root” nothing detected. I’m tapping out. Thank you for all you do Gastone, I truly appreciate your work, but Thrustmaster’s software is just too much of an unstable bag of excrement for me to deal with.
Edit: Now that I have smoked a cigarette and calmed down some, let me ask on last question before I pull the ejection handle. I currently use the Warthog with the TFRP Pedals. Here’s the one weird observation I made when installing the drivers multiple times. When I run the listed installer for the Warthog it says it is installing drivers for the TMWT-Pedals. When it’s done, the start menu icon for them is an icon of rudder pedals. Then I install the unified drivers package that’s listed for the pedals and then a new start menu icon of the joystick appears. WTF is this happening backwards? When I run joy.cpl the device order shows pedals at the top of the list lending evidence that some weird stuff is happening, but I don’t know if that’s anything conclusive.
Anyone see anything like this before? Or are there any Warthog+TFRP users out there that have some guidance on the install order and plug in order for the devices?
The root issue is caused by something interfering with Target. It’s usually either the teamspeak joystick plugin or the Windows Store. You can remove the TS joystick plugin. You can no longer remove the windows store, however you can stop it from running in the background. In Win 10 press start, Type background Apps, disable anything you don’t need, Restart and try loading the profile again.
Also be sure to setup devicesorting.txt in the BMS config file per the instructions on the first page.
-
Added Updated keyfile, for U1. The new keyfile matches the changes in 435 U1. Nothing really effects the HOTAS here, but wanted to keep the profile synchronized with the default BMS keybinds. Unless your using the new windows commands there isn’t a reason to update the key file.
Per the patch notes the keybind changes are.- Alt+RETURN: Switch Windowed - Full Screen Ctrl+Return: Switch Windowed - Borderless, was Alt+Backspace before; Both are integrated into the key files (as a reminder) - Remapping of the following key combinations: -- Full / Basic / Minimum / Blank key files: Reset Trim from Alt+Return -> Alt+F1 Caution Reset from Ctrl+Return -> Alt+F2
-
-
Any plans to release an update for 4.35 U2 ?
Best regards.
Were there any key bind changes in U2? I’ve been using the profile and haven’t seen any issues. Are you having problems?
-
No problems here, it was just a general query.
Best regards.