Key File Subsitution help
-
DEV’s I guess it is my bad luck I do not script, but using TARGET software and BMS key file it’s not needed. Anyway I read the above threads about (the Num Lock in 2d and 3d UI)just a tad of confusion remains. I wanted a ON/OFF command for my warthog, the RDR ALTM key with my program is used for Laser ON/Off. In BMS4.33 key substitution worked fine, but in this BMS 4.33U1 key substitution is strange. I substituted/moved Crtl L for Laser on, then tried numerous other keys, this to avoid the Toggle effect apparently, called now cycle effect in the key file and nothing works, the same problem with Air Refueling door. Opening is OK but closing the doors does not work. The object is one key one action so I don’t have to look in the cockpit to make sure the A/R door is closed or the Laser is OFF. With the Number lock on or off there is no movement of the key to the off position. If you use the individual key/ keys for OFF or Closed it works, Num Lock on or off. I’ve tried Crtl L for Off mode I’ve tried Keypad (KP) 5 (num lock on and off) I’ve tried KP 8, does key substitution work at all? By chance I discovered that Shift KP really needs to have a shift KP(#) to work rather than the normal Num LOCK on and KP (#) applied, you really have to put a “Shift” KP (#) to make the key work. DEV’s if you wish to move this to another forum Please do I’m totally confused any help would be welcomed. If you substitute a key in the BMS Full key file the new key shows up in the correct slot (most of the time) but does not work in the 3d world.
-
The radar altimeter switch is 3-position but if one only uses the standby and on positions it’s effectively on/off. The Warthog naturally provides a button held input when the switch is on and null when the switch is off. It is possible to code into your .key file a particular callback with the “press” context and one for the “release” context which is more or less what I’ve done here:
SimRALTON 53 -2 -2 0 0x0 -1
SimRALTSTDBY 53 -2 -2 0x42 0x0 -1The “0” is the normal press context and the “0x42” is the release context, both for button 53.
-
Frederf Thank you, but i DON’T SCRIPT. my profiles are designed like the old Saitek programs, pick a key in the Key file and select the controller key to assign it to. But you have helped me several times in the past and I owe you thanks for that. But I looking for a solution for a TARGET GUI profile to solve my problem.
-
iam also interested in a fix or solution for this….:(
-
I haven’t looked through all of the key files but the BMS Full file most of the programming is set up to toggles or cycles and not to on/off. You CAN change it but sorry you won’t be able to simply do it through TARGET. It could be mostly done via BMS itself and DX but the WH has a few positions that do not send DX commands hence that wouldn’t work with a few through BMS either as it won’t see a command for some of the WH switch positions.
I have it set up working fully just like with 4.32 or 4.33 but that is because I like digging into the code and I manually set up my TARGET script files and my BMS key files.
Your choice is to set up via DX and miss out on some switch positions or live with toggles if you cannot be bothered to learn how it works and modify it if there are no pre-set up key files that are using on/off versus toggles.
-
guys the fix will be in next update it is a code change so nothing you can do manually for the ui keyfile programming
all I can suggest for now is use keyfile editor https://sourceforge.net/projects/keyfileeditor/
-
Frederf Thank you, but i DON’T SCRIPT. my profiles are designed like the old Saitek programs, pick a key in the Key file and select the controller key to assign it to. But you have helped me several times in the past and I owe you thanks for that. But I looking for a solution for a TARGET GUI profile to solve my problem.
What I mentioned is only a change to the .key file for BMS, no TARGET scripting required. I’m telling you what the Warthog controllers output when used without TARGET at all. The throttle RDR ALTM switch outputs BUTTON 25:ON when in NRM position and BUTTON 25:OFF when in DIS position.
I also must tell you that if you use a TARGET GUI profile, you are using a TARGET script. That is what the GUI does, write a script for you in a wizard type format. But no matter. The GUI or directly writing the script is very flexible too.
I guess I should ask what behavior do you want because the RDR ALTM switch on the Warthog is a 2-position switch and the one in the F-16 is a 3-position switch. Some creativity is needed. Personally I have switch up, on, switch down, standby and I use the mouse to access the off position. If you can imagine it and describe it in words, I can think of a way to get TARGET GUI to achieve it.
-
Hey virtualtwenthe, and Frederf, I finally figured it out. To answer a few questions, to use TARGET GUI I put the Laser key (Crlt L ) and the A/R key (Shift R) in the toggle key position of the BMS Full key file. Entered the TARGET GUI and using the two position switch on the warthog RDRNRM (up position) for Laser ON, Normal layer and (O,U,M, positions). For the A/R door open the upper layer (I) with M position to open only. The key is use HOLD for TYPE of key action. A press to activate the key with HOLD as the key action and use the same key RDRNRM with a release action, (key position back) which will put the key(s) in the OFF position in the 3d world. So the toggle key can be managed by the HOLD type action in the Target GUI and keep all functions in sequence even though the real action should be a pulse action for that key.