Kolbe's Key File Editor issues
-
Hello!
I’m creating a .key file that is a mix between the Full.key and Pitbuilder.key and the idea here is to have all the switch state callbacks from Pitbuilder but also have the toggle callbacks from Full. I have tried to keep as much key bindings from Pitbuilder as I can and have cleared all the toggle callback key bindings. My .key file is intended to be used alongside my Helios profile, hence the preference for switch state callbacks. I incorporated the toggle callbacks “just in case.”
While doing this, I have used Kolbe’s excel file a number of times to visualize where I can map certain callbacks and have noticed it does not display some callbacks.
For instance, I have mapped the AFGearUp and AFGearDown as follows:
AFGearUp 119 0 0x0D 3 0 0 1 “GEAR: LG Handle - UP”
AFGearDown 118 0 0x0D 5 0 0 1 “GEAR: LG Handle - DN”That is “CTRL + SHIFT + =” for gear up and “ALT + SHIFT + =” for gear down but is not displayed on the Keyboard Layout (Keyboard tab) page.
I am using MS Excel 2007 on Win 7 64bit.
-
It’s working fine here.
Can you upload a copy of your tool please.
I’ll have a look. -
I assume by “tool,” you mean my .key file?
-
No,
I’d like to see the tool you will probably have saved during your reconstruction of the key file.
You can send me the key file as well, of course -
I did this semi-automatically via my own Excel file. Please note that the tool itself is not the issue. Importing my .key file into your BMS Key File Editor results in the stated keys not showing up.
Please refer to my Helios profile thread for the key file.
-
Those are showing up as:
And output by Koble’s sheet as:
@KolbesOutput:
AFGearUp 119 0 0x1B 2 0 0 1 “GEAR: LG Handle - UP”
AFGearDown 118 0 0x1B 4 0 0 1 “GEAR: LG Handle - DN”They are importing as:
@KolbesImport:
AFGearUp 119 0 0x1B 2 0 0 1 “GEAR: LG Handle - UP”
AFGearDown 118 0 0x1B 4 0 0 1 “GEAR: LG Handle - DN”This keyfile (http://ihpff4bms.blogspot.co.uk/2015/11/bms-433-key-file-beta.html) shows:
@-IceBetaKeyfile:
AFGearUp 119 0 0x1B 2 0 0 1 “GEAR: LG Handle - UP”
AFGearDown 118 0 0x1B 4 0 0 1 “GEAR: LG Handle - DN”Which is the same as the import and the same as the output. Kolbe’s Sheet is working as far as I can see.
-
You are using an older version of my .key file.
Try changing that to
AFGearUp 119 0 0x0D 3 0 0 1 “GEAR: LG Handle - UP”
AFGearDown 118 0 0x0D 5 0 0 1 “GEAR: LG Handle - DN” -
You are using an older version of my .key file.
Try changing that to
AFGearUp 119 0 0x0D 3 0 0 1 “GEAR: LG Handle - UP”
AFGearDown 118 0 0x0D 5 0 0 1 “GEAR: LG Handle - DN”I chased it down once …. post a link to the current full keyfile and I’ll be happy to see what I come up with here.
-
You got the blog… you were just looking at an old post/page
Still, no need to download anything. Replace the lines in that .key file with what I pasted. That should show you what I mean.
-
0x0D is wrong.
It has to be 0xD (= on US Int locale)
-
Maybe I should add a couple of explanations:
Like in the example above code lines which contain a wrong value (in this case 0x0D) will be ignored without warning.
Maybe I should add a feature to make the user aware of such issues while importing a key file and pointing them to the wrong code line (noted in my to do list).
As the tool sorts them out automatically this will not be too hard to add. -
Ah, please do! In fact, can I request that you make it so that I can just plug in my .key file and Excel will “fix” those for me?
I do understand what you’re saying though. The backspace key is written as 0xE which at first confused me but then realized what it was. What I don’t know is which ones should be 0x and which ones should be 0x0.
-
Just take a look at …/Docs/Key Files & Input/Keyboard Layout Files/…
This folder contains Keyboard Codes .pdf files where you can see which codes are safe to use.
It shows 0xE is indeed Backspace.
Of course this is not a complete set of all available scan codes. But be careful: Some may not
be compatible with all different keyboard locales. Please refer to page 9-40 of the key file manual
(9.1 WHY DOES BMS CRASH WHEN LOADING A KEY FILE?).0x0 is a specific DX related value. It is simply 0.
I don’t think it will be possible to fix wrong values automatically. But maybe I can point out which part
of the code line returns an error. -
0x0 is a specific DX related value. It is simply 0.
No, what I meant is which keys should be “0x” as in “0xE” and which ones should be “0x0” as in “0x06”
Having said that, my gear callbacks are mapped to “0x0D” (= key)which WORK in the game, they just don’t show up in your Excel file. My CAT callbacks are mapped to “0x06” (5 key) which WORK in the game, AND they show up on your Excel file. Maybe just make your Excel file recognize both “0xD” and “0x0D”?
I’ve “fixed” my key file to remove all “0x0?” entries and changed it to “0x?” instead.
-
I don’t know.
Just use 0x instead of 0x0.
-
Yep, done it! So that issue’s solved!
Kolbe, while I have your attention, is there any way that the Excel file retains it’s permissions and also remembers where my .key files are stored? It’s annoying having to grant permission every time and also to navigate to my BMS folder all the time (it defaults to opening my Documents folder)… thanks!
-
Well, “I don’t know” was not correct.
I should have used the statement “I have forgotten…”Here is a list of the scan codes BMS uses. In most cases it’s the “Make” code, sometimes the “Break” code (e.g. ENTER = Make, NUM ENTER = Break).
And here you can see which of the keys have a leading “0”.
So yes, some keys do work with 0x0.I will think about implementing additional checks for the 0x0 stuff. Shouldn’t be too hard.
Regarding your request:
I will add a function to set an import and export folder.Thanks for your input. Well appreciated!
-
That Make or Break bit just went over my head…
You mentioned ENTER and NUM ENTER — ENTER is “0x1C” and NUM ENTER is “0x9C”… is that what you mean? Still don’t understand how that’s relevant.
As for the “=” key, it is listed as “0D” so my “0x0D” should work.
The “5” key is listed as “06” so my “0x06” works, but “0x6” works as well. I’m so confused! -
I assume the leading “0” is just a “placeholder” as all other scan codes have two characters.
But I can’t tell you the inner logic behind.IMO it is completely irrelevant, because you could use it either way. On the other hand, if both
are possible, the toll should support both methods…
However, I can’t remember why I decided to use 0x1 instead of 0x01 for example.
Too long ago -
Time to update the Excel file!