BMS Key File Help
-
So I have found that if I setup my warthog with the POV hat on the throttle active, and try to program key presses to it, then my release commands do not work.
This is the code I added to my BMS config file to activate the POV on the throttle.set g_nNumOfPOVs 2
set g_nPOV1DeviceID 2
set g_nPOV1ID 0
set g_nPOV2DeviceID 3
set g_nPOV2ID 0I have to program the hat switch through the BMS UI. I can not do it with the keyfile editor. After I program the POV on the throttle and open the keyfile with a text editor the keyfile looks different from the one that the keyfile editor exports.
I have tried just adding the commands to the keyfile manually but the same behavior happens.These are the commands that I am adding to the keyfile.
SimRadarRangeStepDown 1 -1 -3 0 0x0 -1
SimRangeKnobUp 1 -1 -3 2 0x0 -1
SimRadarRangeStepUp 1 -1 -3 4 0x0 -1
SimRangeKnobDown 1 -1 -3 6 0x0 -1I’m guessing it has something to do with the BMS config file but I do not know.
Edit: By adding the “SimDoNothing” commands in-between the keypress commands solved the problem.
SimRadarRangeStepDown 1 -1 -3 0 0x0 -1
SimDoNothing 1 -1 -3 1 0x0 -1
SimRangeKnobUp 1 -1 -3 2 0x0 -1
SimDoNothing 1 -1 -3 3 0x0 -1
SimRadarRangeStepUp 1 -1 -3 4 0x0 -1
SimDoNothing 1 -1 -3 5 0x0 -1
SimRangeKnobDown 1 -1 -3 6 0x0 -1
SimDoNothing 1 -1 -3 7 0x0 -1 -
Carbide,
So I have found that if I setup my warthog with the POV hat on the throttle active, and try to program key presses to it, then my release commands do not work……
Can you post the contents of your DeviceSorting.txt file please…
-
Fish44 here is my DeviceSorting.txt
{0402044F-0000-0000-0000-504944564944} “Joystick - HOTAS Warthog”
{0404044F-0000-0000-0000-504944564944} “Throttle - HOTAS Warthog”
{B351044F-0000-0000-0000-504944564944} “F16 MFD 1”
{B352044F-0000-0000-0000-504944564944} “F16 MFD 2”
{076306A3-0000-0000-0000-504944564944} “Saitek Pro Flight Rudder Pedals (USB)”
{C2AB046D-0000-0000-0000-504944564944} “Logitech G13 Joystick” -
……By adding the “SimDoNothing” commands in-between the keypress commands solved the problem…
Solved my issue also. Here’s my scripts for using 2 POV hats.```
//****** JOYSTICK POV FOR TRIM ******//
AFElevatorTrimDown 0 -1 -3 0 0x0 -1
SimDoNothing 0 -1 -3 1 0x0 -1
AFAileronTrimRight 0 -1 -3 2 0x0 -1
SimDoNothing 0 -1 -3 3 0x0 -1
AFElevatorTrimUp 0 -1 -3 4 0x0 -1
SimDoNothing 0 -1 -3 5 0x0 -1
AFAileronTrimLeft 0 -1 -3 6 0x0 -10
SimDoNothing 0 -1 -3 7 0x0 -1//****** JOYSTICK POV SHIFTED, VARIOUS ******//
SimICPNext 2 1099 -3 0 0x0 120
SimDoNothing 2 -1 -3 1 0x0 0
SimTrimYawRight 2 -1 -3 2 0x0 0
SimDoNothing 2 -1 -3 3 0x0 0
SimICPPrevious 2 1099 -3 4 0x0 120
SimDoNothing 2 -1 -3 5 0x0 0
SimTrimYawLeft 2 -1 -3 6 0x0 0
SimDoNothing 2 -1 -3 7 0x0 0//****** BUTTON BOX POV 2 BUTTONS ******//
SimHsiCourseInc 1 -1 -3 4 0x0 -1
SimHsiHeadingInc 1 -1 -3 6 0x0 -1
and the device order…..
{0402044F-0000-0000-0000-504944564944} “Joystick - HOTAS Warthog”
{0404044F-0000-0000-0000-504944564944} “Throttle - HOTAS Warthog”
{0A3816D0-0000-0000-0000-504944564944} “MFG Crosswind V2”
{100312E0-0000-0000-0000-504944564944} “TQSUSBA_R1”
{05BA16C0-0000-0000-0000-504944564944} “BU0836A Interface”
{02FF045E-0000-0000-0000-504944564944} “Controller (Xbox One For Windows)”
And here's the lines in the falcon bms.cfg file for completeness
//////////////////////////////////////////////////////////
// Added for BMS 4.35 //
//////////////////////////////////////////////////////////
set g_nNumOfPOVs 2
set g_nPOV1DeviceID 2
set g_nPOV1ID 0
set g_nPOV2DeviceID 6
set g_nPOV2ID 0Strange how the 'donothing' scripts needed for the first POV and shifted POV, but not the second.
-
I am using key file editor version 4.35.2 (25th of February 2021). Unlike a previous version, this one does not show the throttle section of the Saitek X52. I must be doing something wrong …
See the key file that I import from 4.34 here, via Tresorit. (But the error occurs even without having imported a key file).
SOLVED: It turns out that my version of Excel fails to diplay text, lables, and fonts correctly(!) This is weird, given that I am running the latest version of Excel 365
Please ignore the exchange below, it does not solve the problem.
-
I am using key file editor version 4.35.2 (25th of February 2021). Unlike a previous version, this one does not show the throttle section of the Saitek X52. I must be doing something wrong …
could you provide the your keyfile you are importing to keyfile editor to be able to check it
-
See the updated post, and this link.
-
See the updated post, and this link.
Ok first of all you shouldn’t carry over a key file from 4.34 to 4.35 as there a quite some callbacks that have been changed from 4.34 -> 4.35. Use the keyfile editor import tab the for all listed Falcon BMS technical Manual chapter 15.2 callbacks to be changed from 4.34 to 4.35 as in your keyfile you still have the 4.34 ones
example
SimJfsStart 319 0 0x24 1 0 0 1 “ENG: JFS Switch - Toggle! START 2 / OFF”
doesn’t exist in BMS 4.35 anymore and has to be changed to
SimJfsStartCycle
other than that your DX callbacks for a X52 import at least on here with your keyfile
on the import tab you have a listing of all non 4.35 compatible callbacks in your keyfile
-
Thanks for alerting me about the risks of using a 4.34 key file for 4.35, much appreciated!
However, my initial problem was that the throttle section of the Saitek X52 does not get populated, which happens even without importing a key file.
Can you explain what you intend to say with: “other than that your DX callbacks for a X52 import at least on here with your keyfile” and the role of the graphs you included? Perhaps in your own language?
Many thanks!
-
I’m just saying that if I use your key file with the KeyfileEditor I have on my PC delivered with BMS 4.35, the throttle settings you have in your key file show correctly up on the Tab for the X52
Gesendet von meinem SM-G930F mit Tapatalk
-
Well, no, the Excel file that comes with 4.35 does not show the throttle section - that is the reason I post this problem on the forum!
-
This post is deleted! -
Hello
In the excel file provided with 4.37 I can’t find the new additions concerning the ECM.
Has the file been updated? -
@ertiyu idk about the Excel file, probably deprecated in favor of the new Alt Launcher integratio … err, umm, the Launcher-formerly-known-as-Alternative?
If it helps, the new ECM-related callback section in BMS-Full.key looks like this:
#=================================================================================== SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 "======== 2.11 ECM PANEL ========" SimXMTASPISOper 116 0 0XFFFFFFFF 0 0 0 1 "ECM: XMTASPIS Knob - Operate" SimXMTASPISStdby 116 0 0XFFFFFFFF 0 0 0 1 "ECM: XMTASPIS Knob - Standby" SimXMTASPISToggle 116 0 0XFFFFFFFF 0 0 0 1 "ECM: XMTASPIS Knob - Toggle" SimEcmPowerOn 116 0 0XFFFFFFFF 0 0 0 1 "ECM: Power Knob - On" SimEcmPowerOff 116 0 0XFFFFFFFF 0 0 0 1 "ECM: Power Knob - On" SimXMitInc 116 0 0XFFFFFFFF 0 0 0 1 "ECM: XMT Knob - Increase" SimXMitDec 116 0 0XFFFFFFFF 0 0 0 1 "ECM: XMT Knob - Decrease" SimECMBit 116 0 0XFFFFFFFF 0 0 0 1 "ECM: Bit Test - Test" SimEcmMode1 116 0 0XFFFFFFFF 0 0 0 1 "ECM: Mode 1 - Toggle" SimEcmMode2 116 0 0XFFFFFFFF 0 0 0 1 "ECM: Mode 2 - Toggle" SimEcmMode3 116 0 0XFFFFFFFF 0 0 0 1 "ECM: Mode 3 - Toggle" SimEcmMode4 116 0 0XFFFFFFFF 0 0 0 1 "ECM: Mode 4 - Toggle" SimEcmMode5 116 0 0XFFFFFFFF 0 0 0 1 "ECM: Mode 5 - Toggle"
-
thank you for the answer airtex2019
I find the excel file very useful,
I hope that an updated version for 4.37 will exist.
I will look to add them to my key file. -
Here is a modified excel file,
https://www.dropbox.com/s/6m7ka929dtonldu/Excel BMS_437.zip?dl=0
It features the addition of ECM functions
SimXMTASPISOper 116 0 0XFFFFFFFF 0 0 0 1 "ECM: XMTASPIS Knob - Operate" SimXMTASPISStdby 116 0 0XFFFFFFFF 0 0 0 1 "ECM: XMTASPIS Knob - Standby" SimXMTASPISToggle 116 0 0XFFFFFFFF 0 0 0 1 "ECM: XMTASPIS Knob - Toggle" SimEcmPowerOn 116 0 0XFFFFFFFF 0 0 0 1 "ECM: Power Knob - On" SimEcmPowerOff 116 0 0XFFFFFFFF 0 0 0 1 "ECM: Power Knob - On" SimXMitInc 116 0 0XFFFFFFFF 0 0 0 1 "ECM: XMT Knob - Increase" SimXMitDec 116 0 0XFFFFFFFF 0 0 0 1 "ECM: XMT Knob - Decrease" SimECMBit 116 0 0XFFFFFFFF 0 0 0 1 "ECM: Bit Test - Test" SimEcmMode1 116 0 0XFFFFFFFF 0 0 0 1 "ECM: Mode 1 - Toggle" SimEcmMode2 116 0 0XFFFFFFFF 0 0 0 1 "ECM: Mode 2 - Toggle" SimEcmMode3 116 0 0XFFFFFFFF 0 0 0 1 "ECM: Mode 3 - Toggle" SimEcmMode4 116 0 0XFFFFFFFF 0 0 0 1 "ECM: Mode 4 - Toggle" SimEcmMode5 116 0 0XFFFFFFFF 0 0 0 1 "ECM: Mode 5 - Toggle"
and adding
SimExtlMasterCycleUp 116 0 0XFFFFFFFF 0 0 0 1 "EXT: MASTER Knob - Cycle up" SimAntiColCycleUp 116 0 0XFFFFFFFF 0 0 0 1 "EXT: ANTI COLLISION Switch - Cycle up" SimIFFMasterCycleUp 116 0 0XFFFFFFFF 0 0 0 1 "AUX: MASTER Knob - Cycle up"
I did not add the functions for VR and for the radar cursor.
Thanks again to Kolbe for this spreadsheet.
-
-
@ertiyu @Rouge1512
I am using the modified excel and generated all the keys, including DX ones.
The DX are not working for me. For some reason they are all shifted (related to the launcher mapping) by 96.
The launces seams to use device 4/5 in my case unlike 1/2 which I always set:
I can set the devise to 4&5 in the excel to adjust the launcher shift but what causes this?
In addition the pinky shift is not working at all.
The launcher sets the pinkyshift, in my case, to 4 & 260SimHotasPinkyShift 4 -1 -2 0 0x0 0 SimHotasPinkyShift 260 -1 -2 0 0x0 0
These are the same value the excel uses but for devices 1&2. (not 4/5)
In addition I checked the DX values in BMS and they appear to reflect device 1&2, not 4&5 as the launcher suggests.
How come the launcher, shifted buttons do works then?
(Apast from the pinkey as I wrote)
Any idea what causes this? -
Sorry, but I can’t help you : I juste use the sheet Keystrokes editor to generate the Keyboard combinations required to operate TARGET from Thrustmaster.
Also this file is already much transformed compared to Bms_full.key. I think you have to load this one in the editor (or your old 4.36 keyfile) if you haven’t already done ) into the original @ertiyu file.
-
-
Hello
Actually I had this problem too.
This comes from the fact that in the Falcon BMS.cfg file there is a command which increases the number of buttons per joystick from 32 to 128.set g_nButtonsPerDevice 32
I put 32 and everything is back to normal.