BMS Key File Help
-
Hi ertiyu,
please refer to my answer here:https://www.benchmarksims.org/forum/showthread.php?36084-Missing-callbacks
Apart from that I’d like to add that there was an internal discussion about these callbacks.
The consensus was that they are superfluous. Hence I did not integrated them to neither key files nor editor. -
Thanks for the explanation.
Effectively the toggle functions are sufficient -
Having difficulty changing keys.
Can I have a basic idea of the process?
1 open spreadsheet
2 select options for keys in the box?
3 save it?
4 try it in-game?Is this about right?
-
Please tell me, I was looking for it, but I could not find a combination on the keyboard that resets the capture from all sensors at once. Don’t TMS down. I know that.
Thank. -
I have a question that I cannot answer with the research I have tried.
I have my BMS - FULL key file opened for reference. I have built an encoder to increment and decrement the Altimeter pressure setting knob. It works great. I send an SHIFT+ALT+’ (Apostrophe) for increase and SHIFT+ALT+; (Semi colon) for decrement.
In trying to learn the key file complexities I find these entries for those two functions.SimAltPressIncBy1 116 0 0X28 5 0 0 1 “MAIN: Altimeter Pressure Knob - Incr. (1�)” The 5 behind the keycode tells us this is a SHIFT+ALT state
SimAltPressDecBy1 116 0 0X27 5 0 0 1 “MAIN: Altimeter Pressure Knob - Decr. (1�)”Then “TRYING” to learn and confirm what those code truly are I look up ANSI/ASCII codes for this and I find in several places, this is just one example…
(sections removed for brevity)
Character ANSI# Unicode# ANSI_Hex Unicode_Hex Unicode Name Unicode Range ! 33 33 0x21 U+0021 exclamation mark Basic Latin ' 39 39 0x27 U+0027 apostrophe Basic Latin - THIS APPEARS CORRECT ( 40 40 0x28 U+0028 left parenthesis Basic Latin - This is where I expected to see the Semi Colon, not Left Parenthesis ) 41 41 0x29 U+0029 right parenthesis Basic Latin ; 59 59 0x3B U+003B semicolon Basic Latin - THIS IS NOT WHAT IS IN BMS KEY (0x28 - Right Parenthesis) is what is there.
So, as I stated it works, but what is up with the wrong code display in the keyfile, yet it works?
My BMS FALCON setup looks like this as well, which is what assigns it to BMS-FULL.Key
Is there a different standard other than ANSI for the keystrokes? Why does everything I read say 0x28 is “(” but in BMS 0x28 is a semi-colon?
Thanks,
Nacman -
Please tell me, I was looking for it, but I could not find a combination on the keyboard that resets the capture from all sensors at once. Don’t TMS down. I know that.
Thank.Don’t know if I got your question.
Are you looking for Cursor Zero (CZ)? -
I have a question that I cannot answer with the research I have tried.
I have my BMS - FULL key file opened for reference. I have built an encoder to increment and decrement the Altimeter pressure setting knob. It works great. I send an SHIFT+ALT+’ (Apostrophe) for increase and SHIFT+ALT+; (Semi colon) for decrement.
In trying to learn the key file complexities I find these entries for those two functions.SimAltPressIncBy1 116 0 0X28 5 0 0 1 “MAIN: Altimeter Pressure Knob - Incr. (1�)” The 5 behind the keycode tells us this is a SHIFT+ALT state
SimAltPressDecBy1 116 0 0X27 5 0 0 1 “MAIN: Altimeter Pressure Knob - Decr. (1�)”Then “TRYING” to learn and confirm what those code truly are I look up ANSI/ASCII codes for this and I find in several places, this is just one example…
(sections removed for brevity)
Character ANSI# Unicode# ANSI_Hex Unicode_Hex Unicode Name Unicode Range ! 33 33 0x21 U+0021 exclamation mark Basic Latin ' 39 39 0x27 U+0027 apostrophe Basic Latin - THIS APPEARS CORRECT ( 40 40 0x28 U+0028 left parenthesis Basic Latin - This is where I expected to see the Semi Colon, not Left Parenthesis ) 41 41 0x29 U+0029 right parenthesis Basic Latin ; 59 59 0x3B U+003B semicolon Basic Latin - THIS IS NOT WHAT IS IN BMS KEY (0x28 - Right Parenthesis) is what is there.
So, as I stated it works, but what is up with the wrong code display in the keyfile, yet it works?
My BMS FALCON setup looks like this as well, which is what assigns it to BMS-FULL.Key
Is there a different standard other than ANSI for the keystrokes? Why does everything I read say 0x28 is “(” but in BMS 0x28 is a semi-colon?
Thanks,
NacmanHi Nacman,
Falcon uses scan codes (see here -> Set 1) which are usually all the same, no matter
which keyboard locale you use. What differs is the output, e.g.Scan Code “10” is “Q” on US keybords but “A” on French.
Scan Code “15” is “Y” on French keyboards but “Z” on German.The ui shows always the correct keys for your locale, no matter which keyboard layout is in use.
Please also refer to the Technical Manual (chapter 10) or …Falcon BMS 4.35\Docs\01 Input Devices\01 Keyboard Layouts, in specific the keyboard codes.Hard to tell what the issue is here without further information, like keyboard locale etc.
-
Post #1 updated with some known issues / how to solve it / status stuff for 4.35.
-
For some reason the lastest keyfile editor yeets my Excel to VBA editor and throws a syntax error at “oncursor.gotoStart()”. I never used any VBA stuff related to direct control of the cursor so I don’t even know how to fix it.
EDIT: Solved it by turning on compile on demand, once I realized this is code for Libre that should not even compile if I’m on Excel. That being said, conditional compilation like this is a really bad idea. That’s some cool code to detect which program it runs on but it would be both simpler and cause fewer issues if you simply kept the Libre and Excel versions as 2 separate files.
-
Can you tell me where this occured exactly?
I already found a bug but don’t know if that would fix the issue you described. -
In 4.34 using the key file editor I was able to assign, as an example CATI and CATIII, to a toggle on my warthog throttle. But now all of the “back from fwd” positions are not available. It will only register the “fwd” instance and not the “back from fwd instance.” Is there any way around this? I do not want to have to take up 2 switches for CATI and CATIII.
-
try restarting the PC
do you have 434 still installed?
-
Yes I have restarted and 4.34 is still installed. I tried to import my old keyfile but the keyfile editor does not update the controller assignments, TM warthog tab, to what the keyfile shows when I look at it with a text editor. I don’t remember having to do release commands to make it work.
-
In 4.34 using the key file editor I was able to assign, as an example CATI and CATIII, to a toggle on my warthog throttle. But now all of the “back from fwd” positions are not available. It will only register the “fwd” instance and not the “back from fwd instance.” Is there any way around this? I do not want to have to take up 2 switches for CATI and CATIII.
Let’s assume the swith you want to use is DX 4
SimCATI 4 -2 -2 0 0x0 0
SimCATIII 4 -2 -2 0x42 0x0 0where 0 is on press (fwd) and 0x42 is back from fwd
those lines go to your kkey file DX section
-
Thank you Oakdesign! Understood.
-
On later F16 models the AVTR panel has a three toggle switch with positions labels , EVENT MARK….RECORD…and UNTHRD.
Can anyone explain its use and what keystrokes it uses because I cannot find any in the BMS FULL keyfile -
On later F16 models the AVTR panel has a three toggle switch with positions labels , EVENT MARK….RECORD…and UNTHRD.
Can anyone explain its use and what keystrokes it uses because I cannot find any in the BMS FULL keyfilethese are the available AVTR callbacks
SimAVTRToggle
SimAVTRSwitch
SimAVTRSwitchUp
SimAVTRSwitchDown
SimAVTRSwitchOn
SimAVTRSwitchAuto
SimAVTRSwitchOffThe switch in pit doesn not follow the usual 3 way switchology all explained in the Dash -1
UNTHRD, RECORD & EVENT MARK.
UNTHRD means OFF and is the default position.
EVENT MARK is mislabelled in BMS as in real life this is used to mark a specific point on the tapes
(index) but in BMS it is the old AUTO position where the ACMI will turn ON for 30 seconds upon a
gun trigger or a weapon pickle action.
RECORD is the old ON position where the ACMI is turned ON manually.
The problem is that this 3-position switch does not follow the common logic of all the rest of the 3D
cockpit. To place the switch out of UNTHRD, you must click left as usual. But this action doesn’t move
the switch (as logic would dictate) to ON but straight to EVENT MARK. To move to record, you still
must left click with the switch on EVENT MARK to move the switch down to RECORD. Normally a
move down should be a right click.
So basically, to record an ACMI with the mouse, click twice with the left mouse button. And to place it
back to OFF, click twice with the right mouse button. -
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”