Question about Kolbe DX-generator and 4.33
-
The Joystick/Generic/Kolbe/BMS-Dx Generator is not included in this update. So my question is should I be able to take my Key file from 4.32 and put it into 4.33? I tried but the results were problematic. I have the CH hotas setup and It may of been that my device numbering has changed.
I read in the manual section 3.2.2 restoring 4.32 files “4.32 key files can be used, but if you do so you will have to manually add in/change the new 4.33
callbacks. It is therefore strongly advised to start with a new 4.33 key file and customise it as desired” Does this mean the BMS-Dx Generator will not work in 4.33?I cant wait to do some flying with 4.33 but got to get the stick straightened out first. Thank you!
-
The Joystick/Generic/Kolbe/BMS-Dx Generator is not included in this update. So my question is should I be able to take my Key file from 4.32 and put it into 4.33? I tried but the results were problematic. I have the CH hotas setup and It may of been that my device numbering has changed.
I read in the manual section 3.2.2 restoring 4.32 files “4.32 key files can be used, but if you do so you will have to manually add in/change the new 4.33
callbacks. It is therefore strongly advised to start with a new 4.33 key file and customise it as desired” Does this mean the BMS-Dx Generator will not work in 4.33?I cant wait to do some flying with 4.33 but got to get the stick straightened out first. Thank you!
It is included in this update
In Docs/Keyfile and Inputs/, keyfile generator and Dx generator have been merged into a single xls. Plus you have a pdf “BMS Callback update” listing all callback changes that have been made between 4.32 & 4.33.
-
The Joystick/Generic/Kolbe/BMS-Dx Generator is not included in this update. So my question is should I be able to take my Key file from 4.32 and put it into 4.33? I tried but the results were problematic. I have the CH hotas setup and It may of been that my device numbering has changed.
I read in the manual section 3.2.2 restoring 4.32 files “4.32 key files can be used, but if you do so you will have to manually add in/change the new 4.33
callbacks. It is therefore strongly advised to start with a new 4.33 key file and customise it as desired” Does this mean the BMS-Dx Generator will not work in 4.33?I cant wait to do some flying with 4.33 but got to get the stick straightened out first. Thank you!
You are definetly referring to an old an outdated tool.
Just take a look at your …/Docs/Key Files & Input/… folder and you will get all the answers.
I’ve created a new tool to make it a bit easier for you to convert from 4.32 to 4.33 standards.Besindes of that:
Yes, you can use your old key files. Without ANY side effects.But be warned:
First you will miss a lot of new stuff.
Second the input system will be revised completely in the future.So it is a good practice to bring them up to new standards now to have it a bit easier in the future.
-
Well there you go!
Thanks guys.
-
I checked through both generators, and with a really really few exceptions (you can count it with one hand), all callbacks from 4.32 are still here. 4.33 have quite a number of new callbacks. Some are for new features like FLIR, some are for specific state in a multi-position switch. So if you’d like to go for a spin, 4.32 keystrokes will work all right.
There is an import function in the new keystroke generator. I have not tried it… well actually I didn’t quite realise it is there until I am half-way through re-entering my old keystrokes into the new generator… :oops: oh well, at least it gave me a chance to see what had changed.
-
Brilliant - I did wonder about this. I copied my 4.32 key file into 4.33 and some of it didn’t work.
I’ll run it through the latest key gen.
Thanks Kolbe!
EDIT: Actually, this could be more due to the fact that recently my stick IDs changed in Windows and I’ve not run the keygen again to update them!!
-
I used the new tool and got the HOTAS working, But my keyboard presses are porked? The only key presses that seem to work are the wingman/flight/tower/etc commands menus. Kind of lost on what to do…No keys assigned when i hit the keyboard keys, but all good on the HOTAS.
-
Check out the keyboard section of the DX gen. Have you assigned the correct keyboard? Did you then use the DX gen to export all settings to a keyfile?
-
Check out the keyboard section of the DX gen. Have you assigned the correct keyboard? Did you then use the DX gen to export all settings to a keyfile?
If you are referring to the Keyboard Layout (locale), then yes i set it to US international.
-
Did you then export the whole file to a key file - or did you copy the relevant stick and throttle stuff and paste it into an old key file?
-
The Keystrokes Editor tab shows a full key file (all callbacks are in) with no assignements aka Blank key file (with some exceptions like hardcoded stuff).
This is by purpose because the supported three different locales have partly a different keyboard layount. As this tool doesn’t update the the key asignments
when a locale is changed (this would require macro functions which can not be used by all users) it is pointless to set default assignments for let’s say
US. If a user changes the lovale to French the assignments will not be updated an the tool gives a couple of warnings. So in this case (unfortunately) it is
better to start with a blank file and let the user import his stuff (own key file or default settings).So, after chosing a locale, you first have to import either your own key file via the import function or load the default assignments.
You can either use the macro functions for it or (in case you can’t use them) do it manually.How that works is all described in the Key File Editor manual.
-
Did you then export the whole file to a key file - or did you copy the relevant stick and throttle stuff and paste it into an old key file?
I used the output option and then copied/pasted the entire string into the key file.
-
My stupid excel macros were disabled. Using the macros way works but manually I had no joy!
-
Copy.
Considering you have read the manual about the editor:
If you still think there is a bug or you have other suggestions, feel free to leave your comments here.
Thanks.
-
One issue using “BMS Key File Editor.xls” in 4.33.
Imported callbacks from existing .key for X-52 POV Hat 1 doesn’t appear properly in the “Saitek X-52” tab.
I have tried exporting with default callbacks and then re-import created .key file, same thing, doesn’t appear.
I think there is a pb with the search formula in colomun Q, not looking for the correct sentence : “0 0”, “0 1”, “0 2”, …CheckPoint
