Which way is the easiest way to create or modify a key file?
-
Yes it’s definitely the full key which is loaded into AL. As for the X52 Pro profile, that’s no good to me, I have the non pro model. It would have been ideal to be able to test another profile out to see if it works as expected.
Dee Jay I read in lots of post that editing the key file inside of BMS is not recommended, it’s meant to screw up the key file. Are you saying this is not correct?
-
@warpig which version of Alternative Launcher are you using? Alt Launcher 1.6 modified BMS Full. Alt Launcher 2.0 modifies BMS Auto and has to be manually selected.
-
Its the latest version, ver 2.00
-
@warpig said in Which way is the easiest way to create or modify a key file?:
Dee Jay I read in lots of post that editing the key file inside of BMS is not recommended, it’s meant to screw up the key file. Are you saying this is not correct?
Did they explained why?
…
If you don’t need to do very specific things, and or add specific lines … etc … for pit-building for example or specific devices/needs … you don’t have to bother with alternate launcher or and kind of additional tools.
Do it if you like to … but it is not mandatory. (however, keep a clean copy or original files).
Save the profile with another name (to keep the original and to avoid overwriting it) because it is true that the save suppress some formatting.
If you like to better know what happens, simply save a copy of an existing original profile then compare with Win-merge. You will understand. -
@dee-jay said in Which way is the easiest way to create or modify a key file?:
Save the profile with another name (to keep the original and to avoid overwriting it) because it is true that the save suppress some formatting.
If you like to better know what happens, simply save a copy of an existing original profile then compare with Win-merge. You will understand.Just to expand on this comment – saving through the BMS Setup Controller screen will wipe any/all comments from the keyfile, including those used simply for separating sections to be easy on the eyes, which is not really an issue if you never intend to open a keyfile in a notepad for manual editing.
BUT if you do rely on comments in a keyfile, such as below, losing these (lines starting with ‘#’) could be a real problem:
ex.
FlightEchelonRight -1 0 0XFFFFFFFF 0 0 0 1 "FLIGHT: Go Echolon Left" FlightEchelonLeft -1 0 0XFFFFFFFF 0 0 0 1 "FLIGHT: Go Echolon Right" FlightDiamond -1 0 0XFFFFFFFF 0 0 0 1 "FLIGHT: Go Diamond" #=================================================================================== #X52 Pro: Falconeer v1 - HOTAS Section (X52 Pro as Device 1, using included .pr0) #=================================================================================== SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 "============================================" SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 "=== X52 PRO Falconeer v1 w/ ICP & MFDs ===" SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 "============================================" #=================================================================================== SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 "======== 9.01 UNSHIFTED BUTTONS ========" SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 "======== STICK ========" #== 1st Trigger Button (DX0) SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 "1st Trigger Button: First Trigger Detent" SimTriggerFirstDetent 0 -1 -2 0 0x0 -1 -1 #== 2nd Trigger Button (DX14) SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 "2nd Trigger Button: Second Trigger Detent" SimTriggerSecondDetent 14 -1 -2 0 0x0 -1 #== Safe Fire Button (DX1) SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 "Safe Fire Button: Weapon Release / Pickle" SimPickle 1 -1 -2 0 0x0 -1 #== Pinky (SHIFT) Button (DX5 and DX261) SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 "Pinky (SHIFT) Button: Stick Pinky Button" SimHotasPinkyShift 5 -1 -2 0 0x0 -1 SimPinkySwitch 5 -1 -2 0x42 0x0 -1 SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 "Pinky (SHIFT) Button: (HOLD to Shift)" SimHotasPinkyShift 261 -1 -2 0 0x0 -1 #== A - Button (DX2) SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 "A Button: NWS - A/R DISC - MSL STEP" SimMissileStep 2 -1 -2 0 0x0 -1 #== B - Button (DX3) SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 "B Button: TRIM Reset" AFResetTrim 3 -1 -2 0 0x0 -1 #== C - Button (DX4) SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 "C Button: FOV Look Closer - Toggle" FOVToggle 4 -1 -2 0 0x0 -1 #== MODE Roller Dial (DX27, DX28, DX29) SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 "MODE Roller Dial RED: DGFT Override Mode" SimSelectSRMOverride 27 -1 -2 0 0x0 -1 SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 "MODE Roller Dial MAG: DGFT/MRM Cancel" SimDeselectOverride 28 -1 -2 0 0x0 -1 SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 "MODE Roller Dial BLUE: MRM Override Mode" SimSelectMRMOverride 29 -1 -2 0 0x0 -1 #== STICK HAT 4-Way (DX19, DX20, DX21, DX22) (note Black) SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 "HAT (Black) 4-Way UP: TMS Up" SimTMSUp 19 -1 -2 0 0x0 -1 SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 "HAT (Black) 4-Way RIGHT: TMS Right" SimTMSRight 20 -1 -2 0 0x0 -1 SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 "HAT (Black) 4-Way DOWN: TMS Down" SimTMSDown 21 -1 -2 0 0x0 -1 SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 "HAT (Black) 4-Way LEFT: TMS Left" SimTMSLeft 22 -1 -2 0 0x0 -1
-
im going to give that a try just for lol’s ill back it up first, then assign some buttons see if it actually does anything. ill report back.
-
@warpig you said earlier you were using the BMS full key file, if so, you’re using the wrong key file for Alt Launcher 2.0.
-
it works. i think that should do it, BUT how do you program a button with 2 commands on the 1 button. one with the pinky and one without?
-
@warpig do you mean how to bind a mapping to a shifted button in AL? First, filter for “Stick: pinky switch (DX Shift)” and bind that to something you’re comfortable holding while pressing another button. Then, in the mapping you want to shift, hold that shift button (you’ll see the DX Shift box light up underneath the Awaiting Inputs prompt) and press the button you want shifted. Save that and you should be good to go.
-
@ghastlytt
First off i was using the Basic DX x52 profile but in AL it loads BMS Full and i cant find a way to load the Basic DX x52 key if there is a way.Second thing, if i bind a button to the shifted pinky like you say in your reply above then what happens if you need more than one? Like for example see the button map here.
https://forum.falcon-bms.com/topic/19461/blackhawk-s-saitek-x52-keyfile-dx-profile-for-bms-4-35
The big hat switch on the stick has TMS and Trim for up down left and right. I would like to remove the trim and replace it with viewgen rotate view up, down, left, and right. I can use trim on the keyboard.
But also it would be great to be able to use the AL for future use instead of asking all the time in the forum. -
@warpig I see. If you are going to use Alt Launcher, you’re pretty much committing yourself to setting up your own profile since Alt Launcher 2.0 only modifies the BMS Auto key file. To shift other buttons, you simply repeat the second step of my previous instructions, but with a different button.
If you’re trying to start with someone else’s profile, as you’ve linked, I think you’ll have to follow their instructions and edit their key file with the key file editor. I’m not sure if you could import it into AL to modify by overwriting BMS Auto with the profile you’re trying to use because I don’t know if AL uses the BMS Auto key file as its memory.
-
I may even try to create it from scratch and using the PDF as a guide for all the commands. Ill try that one. Im still a bit confused about the shifting but I haven’t tried it yet so it may make sense once i have a look at it.
Thanks for your everyone. If i run into any trouble, ill be back. -
I agree that using notepad++ or another editor that you’re familiar with is the best choice. The learning curve may be a bit steep at first, but it’ll pay dividends down the road once you’ve grasped the basic concept.
Don’t be scared of “shifted” functions, it just means adding 254 (that’s the standard shift offset minus one) to the button number that BMS shows you in the setup controller screen.
All the best,
uwe
-
One thing that has dawned on me while i was reading key editor manual from above.
Am I correct in saying that any method of key editing either via Notepad++ or AL or any other way is a way to edit the keys, as in the keyboard map? Correct? It has nothing to do with the joystick mapping?
If this is correct then im going about it the wrong way. The keyboard mapping is fine, ill just learn the keys for whatever functions i need. Its the joystick assignments which are killing me. Could someone please confirm? BTW i tried to Shift the POV 1 up button with the pinky but it aint working!
-
You can set set callbacks to controller buttons in the key file too. Look at one of the example key files that are already set up for a controller. The pre made key files have many remarks in them explaining what each line does. They even explain dx shifting. The only thing that is necessary for the pre made one to work is to make sure that your controllers are loading in windows in the correct order so the dx button numbers match up.
I just recently had to do this because I couldn’t get target to work in win 11. The dev folks did a great job on the key files.
-
A good way of going about this is to
a) create a working default file for your setup using Kolbe’s spreadsheet
b) save the resulting key file to your config folder under a new unique name (I use “hoover20220203v1.key” for example so I can always revert to older versions)
c) use notepad++ or any other decent editor like GNU emacs from then onwards to make your own customizations, saving them to a new file and testing them.
All the best,
Uwe -
@hoover
Ive had a go at that spreadsheet, its a bit confusing, there arnt any clear steps on how to use it. I really need something like
Step 1 do this
Step 2 do this
And so on.
I got to selecting my spreadsheet version and then selecting my controller in the dropdown then its like yeah now what? -
@warpig
Hi!
You should learn to use EXCEL, there you can do whatever you want! -
-
@hoover
Hoover, I only have Excel on my PC!
Yes it also works in LibreOffice!