Editing keyfiles directly… put my mind at rest please!
-
Say I wanted to use Pinky Shift and DMS Up to act as ICP Next button, would it simply be a case of adding the following line to the bottom of a *.key file (after ensuring relevant setting in falcon bms.cfg file are made)?
[size]SIMICPNext 266 -1 -2 0 0x0 0 [/size]
so, for example, the default BMS - Full.key file would like this at the bottom
... SimDoNothing 2 -1 -3 3 0x0 -1 AFElevatorTrimDown 2 -1 -3 4 0x0 -1 SimDoNothing 2 -1 -3 5 0x0 -1 AFAileronTrimLeft 2 -1 -3 6 0x0 -1 SimDoNothing 2 -1 -3 7 0x0 -1 [size]SIMICPNext 266 -1 -2 0 0x0 0[/size] ```TIA!
-
The 255 gets added to the DirectX mapping. I don’t have a key file in front of me, but it should be the numbers that are increasing in the 4th column (I think? Again I don’t have one to look at right now).
-
Say I wanted to use Pinky Shift and DMS Up to act as ICP Next button, would it simply be a case of adding the following line to the bottom of a *.key file (after ensuring relevant setting in falcon bms.cfg file are made)?
[size]SIMICPNext 266 -1 -2 0 0x0 0 [/size]
so, for example, the default BMS - Full.key file would like this at the bottom
... SimDoNothing 2 -1 -3 3 0x0 -1 AFElevatorTrimDown 2 -1 -3 4 0x0 -1 SimDoNothing 2 -1 -3 5 0x0 -1 AFAileronTrimLeft 2 -1 -3 6 0x0 -1 SimDoNothing 2 -1 -3 7 0x0 -1 [size]SIMICPNext 266 -1 -2 0 0x0 0[/size] ```TIA!
Maybe. What key is DMS UP command on? Which key(s) are the pinky shift on?
You must have the pinky shift command on a button. That command must exist, on that button, in both the unshifted and shifted state. See this link for an example: https://www.benchmarksims.org/forum/showthread.php?23661-Flounder-s-X52-Pro-Keyfile-DX-Profile-for-BMS-4-33&p=345909&viewfull=1#post345909
With regard to the relationship between DMS Up and ICP Next, the default is +256 ‘button numbers’. You show ICP Next on button #266. DMS Up would normally be on button #10 (?) …… is it?
May be better to post your whole keyfile, or least all the DX commands, so that we can see the pinky command is correct and then relationship between DMS Up and ICP Next is correct.
-
It’s a Warthog stick using completely stock DX assignments. In the falcon bms.cfg file I made sure the changes as per the documentation was made, also made sure the Pinky Button DX shift was on DX2 and DX258. The line I added was to a completely stock and unchanged BMS - FULL.KEY file.
Tried it last night quickly but no joy I’ll try again later after I get back in front of the PC, and post some of my configs and file contents.
My aim is to use a completely stock Warthog stick and TUSBA TQS using only DX assignments.
-
I think Kolbe’s key file editor would have a good starting setup for you as it supports the warthog natively.
Cheers, Uwe
-
I got it to work. In theory doing as I suggested above does/would work, but I didn’t take into account the DX button had been assigned earlier in the file (for whatever reason) and looking through the documentation deeper, I read that the first assignment is used with any further ones ignored. Armed with this info, I looked at the file in depth and found the earlier assignment.
I agree, hoover, the excel sheet would be a good starting point but me being me, I prefer to do things the hard way…
Edit - here is my BMS - FULL - CUSTOM.key as it stands now. These entries come at the end of the file, directly after all the Radio Commands. I will eventually assign SimDoNothing or ??? to the appropriate buttons as I decide what I want where.
### ### Stick Button DX Assignments ### SimTriggerFirstDetent 0 8 -2 0 0x0 -1 SimPickle 1 8 -2 0 0x0 -1 SimHotasPinkyShift 2 8 -2 0 0x0 -1 SimAPOverride 3 8 -2 0 0x0 -1 SimMissileStep 4 8 -2 0 0x0 -1 SimTriggerSecondDetent 5 8 -2 0 0x0 -1 SimTMSUp 6 8 -2 0 0x0 -1 SimTMSRight 7 8 -2 0 0x0 -1 SimTMSDown 8 8 -2 0 0x0 -1 SimTMSLeft 9 8 -2 0 0x0 -1 SimDMSUp 10 8 -2 0 0x0 -1 SimDMSRight 11 8 -2 0 0x0 -1 SimDMSDown 12 8 -2 0 0x0 -1 SimDMSLeft 13 8 -2 0 0x0 -1 SimCMSUp 14 8 -2 0 0x0 -1 SimCMSRight 15 8 -2 0 0x0 -1 SimCMSDown 16 8 -2 0 0x0 -1 SimCmsLeft 17 8 -2 0 0x0 -1 ### ### Throttle Button DX Assignments ### SimCursorEnable 18 8 -2 0 0x0 -1 SimSlapSwitch 19 8 -2 0 0x0 -1 SimToggleMissileCage 20 8 -2 0 0x0 -1 OTWSelectF3PadlockMode 21 8 -2 0 0x0 -1 SimCommsSwitchLeft 22 8 -2 0 0x0 -1 OTWSelect3DCockpitMode 23 8 -2 0 0x0 -1 SimCommsSwitchRight 24 8 -2 0 0x0 -1 SimCursorUp 26 8 -2 0 0x0 -1 SimCursorRight 27 8 -2 0 0x0 -1 SimCursorDown 28 8 -2 0 0x0 -1 SimCursorLeft 29 8 -2 0 0x0 -1 AFBrakesIn 30 8 -2 0 0x0 -1 AFBrakesOut 31 8 -2 0 0x0 -1 ### ### TM MFDs ### SimCBEOSB_1L 32 8 -2 0 0x0 -1 SimCBEOSB_2L 33 8 -2 0 0x0 126 SimCBEOSB_3L 34 8 -2 0 0x0 -1 SimCBEOSB_4L 35 8 -2 0 0x0 -1 SimCBEOSB_5L 36 8 -2 0 0x0 -1 SimCBEOSB_6L 37 8 -2 0 0x0 -1 SimCBEOSB_7L 38 8 -2 0 0x0 -1 SimCBEOSB_8L 39 8 -2 0 0x0 -1 SimCBEOSB_9L 40 8 -2 0 0x0 -1 SimCBEOSB_10L 41 8 -2 0 0x0 -1 SimCBEOSB_11L 42 8 -2 0 0x0 -1 SimCBEOSB_12L 43 8 -2 0 0x0 -1 SimCBEOSB_13L 44 8 -2 0 0x0 -1 SimCBEOSB_14L 45 8 -2 0 0x0 -1 SimCBEOSB_15L 46 8 -2 0 0x0 -1 SimCBEOSB_16L 47 8 -2 0 0x0 -1 SimCBEOSB_17L 48 8 -2 0 0x0 -1 SimCBEOSB_18L 49 8 -2 0 0x0 -1 SimCBEOSB_19L 50 8 -2 0 0x0 -1 SimCBEOSB_20L 51 8 -2 0 0x0 -1 SimDoNothing 52 8 -2 0 0x0 -1 SimDoNothing 53 8 -2 0 0x0 -1 SimDoNothing 54 8 -2 0 0x0 -1 SimDoNothing 55 8 -2 0 0x0 -1 SimCBEOSB_BRTUP_L 56 8 -2 0 0x0 -1 SimCBEOSB_BRTDOWN_L 57 8 -2 0 0x0 -1 SimRadarGainUp 58 8 -2 0 0x0 -1 SimRadarGainDown 59 8 -2 0 0x0 -1 SimCBEOSB_1R 64 8 -2 0 0x0 126 SimCBEOSB_2R 65 8 -2 0 0x0 126 SimCBEOSB_3R 66 8 -2 0 0x0 126 SimCBEOSB_4R 67 8 -2 0 0x0 126 SimCBEOSB_5R 68 8 -2 0 0x0 126 SimCBEOSB_6R 69 8 -2 0 0x0 126 SimCBEOSB_7R 70 8 -2 0 0x0 126 SimCBEOSB_8R 71 8 -2 0 0x0 126 SimCBEOSB_9R 72 8 -2 0 0x0 126 SimCBEOSB_10R 73 8 -2 0 0x0 126 SimCBEOSB_11R 74 8 -2 0 0x0 126 SimCBEOSB_12R 75 8 -2 0 0x0 126 SimCBEOSB_13R 76 8 -2 0 0x0 126 SimCBEOSB_14R 77 8 -2 0 0x0 126 SimCBEOSB_15R 78 8 -2 0 0x0 126 SimCBEOSB_16R 79 8 -2 0 0x0 126 SimCBEOSB_17R 80 8 -2 0 0x0 126 SimCBEOSB_18R 81 8 -2 0 0x0 126 SimCBEOSB_19R 82 8 -2 0 0x0 126 SimCBEOSB_20R 83 8 -2 0 0x0 126 SimDoNothing 84 8 -2 0 0x0 -1 SimDoNothing 85 8 -2 0 0x0 -1 SimDoNothing 86 8 -2 0 0x0 -1 SimDoNothing 87 8 -2 0 0x0 -1 SimCBEOSB_BRTUP_R 88 8 -2 0 0x0 126 SimCBEOSB_BRTDOWN_R 89 8 -2 0 0x0 126 SimRadarGainUp 90 8 -2 0 0x0 126 SimRadarGainDown 91 8 -2 0 0x0 126 ### ### Stick Button DX Assignments - SHIFTED LAYER ### SimDoNothing 256 8 -2 0 0x0 -1 AFResetTrim 257 8 -2 0 0x0 -1 SimHotasPinkyShift 258 8 -2 0 0x0 -1 SimEject 259 8 -2 0 0x0 117 SimFuelDoorToggle 260 8 -2 0 0x0 311 SimDoNothing 261 8 -2 0 0x0 -1 FOVToggle 262 8 -2 0 0x0 -1 SimHSIModeInc 263 8 -2 0 0x0 125 SimAVTRToggle 264 8 -2 0 0x0 115 SimHSIModeDec 265 8 -2 0 0x0 125 SimICPNext 266 8 -2 0 0x0 -1 OTWSelectOrbitMode 267 8 -2 0 0x0 -1 SimICPPrevious 268 8 -2 0 0x0 -1 OTWSelectHUDMode 269 8 -2 0 0x0 -1 SimHmsSymWheelUp 270 8 -2 0 0x0 116 SimExtlPower 271 8 -2 0 0x0 115 SimHmsSymWheelDn 272 8 -2 0 0x0 116 SimECMOn 273 8 -2 0 0x0 -1 ### ### Throttle Button DX Assignments - SHIFTED LAYER ### SimEmergencyJettison 274 8 -2 0 0x0 123 AWACSDeclare 275 8 -2 0 0x0 -1 AWACSRequestPicture 276 8 -2 0 0x0 -1 SimDoNothing 277 8 -2 0 0x0 -1 SimDoNothing 278 8 -2 0 0x0 -1 SimThrottleIdleDetent 279 8 -2 0 0x0 314 AFElevatorTrimUp 0 -1 -3 0 0x0 -1 AFAileronTrimRight 0 -1 -3 2 0x0 -1 AFElevatorTrimDown 0 -1 -3 4 0x0 -1 AFAileronTrimLeft 0 -1 -3 6 0x0 -1 AFElevatorTrimUp 2 -1 -3 0 0x0 -1 SimDoNothing 2 -1 -3 1 0x0 -1 AFAileronTrimRight 2 -1 -3 2 0x0 -1 SimDoNothing 2 -1 -3 3 0x0 -1 AFElevatorTrimDown 2 -1 -3 4 0x0 -1 SimDoNothing 2 -1 -3 5 0x0 -1 AFAileronTrimLeft 2 -1 -3 6 0x0 -1 SimDoNothing 2 -1 -3 7 0x0 -1
-
Right. Thanks. Looks right …. SimHOTASPinkyShift on 2 & 258 and DMS Up and ICP Next on 10 & 266. It’s not that I ‘doubted’ you or what you said, but about being able to see/visualize it in context of the whole DX part of the keyfile.
Also, as you probably know, the shift command you used (SimHOTASPinkyShift) is multi-function. On short press (default is ?0.250 seconds; user configurable in the Falcon BMS cfg file) it will change FOV on Mavs, TGP, FCR, etc., whichever is the SOI at the time. When held, you will be in the shifted layer. When the shift is engaged, it shifts all DX devices.
It may be useful to repeat select keys/commands in the shifted and un-shifted state. For example, UHF and VHF Comms so that you can use the radio when you have the shift depressed.
-
It may be useful to repeat select keys/commands in the shifted and un-shifted state. For example, UHF and VHF Comms so that you can use the radio when you have the shift depressed.
Hi, short press on the pinky defaults to 0.2 seconds and switches the NORM/EXP on radar, HSD, etc. as expected which is good
Funnily enough, you mention repeating commands for both shifted and unshifted states. I have found I need to basically repeat all commands that I want in both states where required, otherwise nothing happens in the shifted state. It makes the file just a little bit fuller than probably necessary, but it’s a small price to pay I suppose.
Working with the keyfile directly in conjunction with the manuals, I now have a far better understanding of how the file is constructed and the commands work, etc. so it’s been a worthwhile exercise. The excel tool is no doubt good, but I like to know how things work at the lowest levels and using tools such as this (Foxy and TARGET GUI are other examples - I was using TARGET script editor for a while) don’t always allow me to do that.
Happy I got here - now I should be able to configure my controllers exactly as I want to with the minimum of fuss.
Thanks all for your inputs!
-
Hey mate, why don’t you use numeric keypad from your keyboard for the ICP?
Check this out, here’s what have implemented for my squad;Now, you change your KEY file for these lines:
SimICPAA 1013 0 0X37 0 0 0 1 "ICP-A-A" SimICPAG 1014 0 0X4A 0 0 0 1 "ICP-A-G" SimICPALOW 1016 0 0X48 0 0 0 1 "ICP-2-ALOW" SimICPCLEAR -1 0 0X4E 0 0 0 1 "ICP-Reset" SimICPCom1 1011 0 0XD2 0 0 0 1 "ICP-COM1" SimICPCom2 1091 0 0XC7 0 0 0 1 "ICP-COM2" SimICPCrus 1019 0 0X4C 0 0 0 1 "ICP-5-CRUS" SimICPDEDDOWN 1114 0 0XD0 0 0 0 1 "ICP-DCS-Down" SimICPDEDSEQ 1115 0 0XCD 0 0 0 1 "ICP-DCS-Seq" SimICPDEDUP 1113 0 0XC8 0 0 0 1 "ICP-DCS-Up" SimICPEIGHT 1109 0 0X50 0 0 0 1 "ICP-8-FIX" SimICPEnter 1022 0 0X9C 0 0 0 1 "ICP-Enter" SimICPFAck 1017 0 0X21 2 0 0 1 "WARNING LIGHTS-F ACK" SimICPIFF 1105 0 0XFFFFFFFF 0 0 0 1 "ICP-IFF" SimICPLink 1020 0 0X20 2 0 0 1 "od- ICP-DLNK" SimICPLIST 1104 0 0XB5 0 0 0 1 "ICP-LIST" SimICPMark 1021 0 0X4F 0 0 0 1 "ICP-7-MARK" SimICPNav 1012 0 0XFFFFFFFF 0 0 0 1 "ICP-NAV" SimICPNext 1024 0 0XC9 0 0 0 1 "ICP-Next" SimICPNINE 1110 0 0X51 0 0 0 1 "ICP-9-A-CAL" SimICPPrevious 1023 0 0XD1 0 0 0 1 "ICP-Previous" SimICPResetDED 1112 0 0XCB 0 0 0 1 "ICP-DCS-Return" SimICPSIX 1108 0 0X4D 0 0 0 1 "ICP-6-TIME" SimICPStpt 1018 0 0X4B 0 0 0 1 "ICP-4-STPT" SimICPTHREE 1107 0 0X49 0 0 0 1 "ICP-3" SimICPTILS 1015 0 0X47 0 0 0 1 "ICP-1-ILS" SimICPZERO 1106 0 0X52 0 0 0 1 "ICP-0-M-SEL"
If you print that picture, using windows paint at 120%, it will be at keyboard dimensions and can even be used above those keys…
Cheers.
-
I got an X-Keys 20 legacy I use for the ICP.
Edit - sorry, I should expand that… The X-Keys covers most of the ICP, but I wanted the Next and Previous buttons on the shifted layer to let me keep Hands On for simple tasks such as inc/dec waypoint, things like that.