key files (say, the minimum one which is nice and short and you can always add to it) and make a copy and name it JFlight1.key or similar. Very first thing I’d recommend is take one of the default. I get what you have to do but I don’t know how. Now I want to try to set up my own profile and have no idea where to start. If that doesn’t make sense, this post may also be sure if this adds any clarity to the DX numbering or BlueRaven, that example you provided worked great and helped me to understand how it works. The shift layer will be buttons 257 - 266, with the shift command duplicated on button 258.īuttons from 11 - 32 and 266 - 287 will be unused since your device doesn’t have that many buttons. The unshifted layer will map buttons 1 - 10. Say your HOTAS X is your first device and has 10 buttons and the shift command is on button #2. So the shift layer for the 1st device covers buttons 257 - 288 (DX numbers 256 - 287). The shift layers are ‘new, virtual’ buttons offset by +256. 2nd device is 33 - 64 (DX numbers 32 - 63), and so on. it occurs twice in the keyfile.īeyond that, the next most important thing to understand is that the 1st device, unshifted DX layer covers buttons 1-32 (DX numbers 0-31). That command must be on the same button in both the unshifted and shifted layer …. When held it allows access to the shifted function. (and in the Hornet calls for a G-Limit increase of 1.33x). On short press, it changes the FOV on the FCR, HSD, Mavs, TGP, etc. It’s in the manuals in this folder: x:\Falcon BMS 4.33 U1\Docs\Key Files & Inputīasically you’ll add the command SimHotasPinkyShift to your keyfile.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |