BMS Key File Help
-
I’m using the Saitek X52 pro. Shift mode does not work why?
-
Kolbe-49th, after several days of mapping different joystick combo’s I believe I have remapped my original bms full key file. Is there a link to the original bms full key file without doing a complete bms 4.33 install.
I’m sorry. I completely missed your post. Shame on me… :oops:
Yes. Take a look at the Docs\Key Files & Input folder. All key files are stored there as a backup.I’m using the Saitek X52 pro. Shift mode does not work why?
This is hard to say without further details.
Wrong callback implementation in conjunction with wrong DX button numbers comes to mind.
But your specific problem could be completely different.
I suggest reading the Key File Manual and take also a look at the Saitek X52 - DX Setup Guide.
Both are in the Docs\Key Files & Input folder too. -
I have a problem, if i imported a key file, the cougar “edit column” is not updated with the imported key file. It remain the old callback or the default .
I have set the right devices sequences in DX Setting tab and macro are active.
The keyboard editor tab is correctly updated with imported data.
-
Sorry,
I completely missed your postFirst, set the DX devices on the DX Settings sheet first before you import a key file.
Then you have two options:
1. Go to the Cougar sheet and make sure it is set to “Show imported callbacks”. You can
manually copy paste the content to the “edit” column.Or
Use the macro functions (Options on DX Settings sheet) and select your device in “Apply imported data” section and hit “Import Selected”.
Hope this helps (if not solved meanwhile).
-
Yes thanks, i already did as in point 1 and now my xls is aligned with key file of course for next change i can start from xls
-
Hello I was wondering where the Most Wanted tab went to in the BMS Keystroke Editor. It was very useful for me and now all of a sudden all of my .key files have disappeared. so really could use it.
-
Hi Pinefang,
I am really not sure after that long time, why exactly I removed that tab.
Probably it was because that you have the filtering options in the keystrokes editor tab.However, I extracted the “Most wanted” tab from an old version.
Note:
I have not checked for updated / removed callbacks.If I don’t forget I will reimplement it into the next editor version in 4.34.
-
Hello
I found a “bug”, finally I think.
SimStepMissileVolumeUp 116 3 0x11 7 0 0 1 “AUDIO1: MSL Knob - Incr. Volume” from the Excel sheet
SimStepMissileVolumeUp 116 0 0X28 1 0 0 1 “AUDIO1: MSL Knob - Incr. Volume” from Waichou’s profile
The 3 tells Helios that there is a mouse event so do not show it the possible choices.
The 0 indicates a keyboard event so it becomes available.
There are more than zero digits in the X column of the Keystroke Editor
SimStepMissileVolumeUp
SimStepMissileVolumeDown
SimAud1Com1
SimAud1Com1Sql
SimAud1Com1Gd
SimAud1Com2
SimAud1Com2Sql
SimAud1Com2Gd
SimStepThreatVolumeUp
SimStepThreatVolumeDownThanks again Kolbe for the Excel sheet!
Sorry for English
I am French.
I go through google translation -
Hi ertiyu,
thanks for reporting.
The third part of a keyboard code line is not used. So, this is not an issue although it should be zero.
But seems third party software has problems with it. I will address this for U1.Good catch.
-
Looking forward to help
-
Hello
I did not find in the Keyfile the following lines :_SimIFFBackupM1Digit1_0
SimIFFBackupM1Digit1_1
SimIFFBackupM1Digit1_2
SimIFFBackupM1Digit1_3
SimIFFBackupM1Digit1_4
SimIFFBackupM1Digit1_5
SimIFFBackupM1Digit1_6
SimIFFBackupM1Digit1_7SimIFFBackupM1Digit2_0
SimIFFBackupM1Digit2_1
SimIFFBackupM1Digit2_2
SimIFFBackupM1Digit2_3SimIFFBackupM3Digit1_0
SimIFFBackupM3Digit1_1
SimIFFBackupM3Digit1_2
SimIFFBackupM3Digit1_3
SimIFFBackupM3Digit1_4
SimIFFBackupM3Digit1_5
SimIFFBackupM3Digit1_6
SimIFFBackupM3Digit1_7SimIFFBackupM3Digit2_0
SimIFFBackupM3Digit2_1
SimIFFBackupM3Digit2_2
SimIFFBackupM3Digit2_3
SimIFFBackupM3Digit2_4
SimIFFBackupM3Digit2_5
SimIFFBackupM3Digit2_6
SimIFFBackupM3Digit2_7_Bad manipulation of me?
Should you add them yourself?
Unfortunately I do not know how to do it.:(
Possible to have them in the next release?Thank you again for the work provided!
I can not live without it!sorry for the translation I go through google translate
-
err : sorry the heat is to much for me…misinterpretation from my side
-
Thank you snelle.
I just watched but the lines are not present in the 2 files.
So you have to add them manually.:(And since I’m sluggish, I like it when IT does everything.:razz:
-
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.