Controls set up in Launcher do not work in-game
-
Hi, I have a problem which someone may have an idea about.
In the launcher I can flick switches on my throttle and joystick and see the mapping in Keymapping happen. So for instance, I press TMS-Up on my Warthog stick and the Launcher jumps to that row and shows the mapping.
But when I enter BMS, in the Setup screen the keys show up as “Not assigned”. For instance, the TMS-Up which works in the Launcher shows up as “not assigned”. The active keyfile reads as “BMS - Auto”.
I have set “set g_nButtonsPerDevice 32” in the Falcon BMS User.cfg file. In the launcher I have 3 columns for my throttle and 1 column for the stick. The value is 128 in the Falcon BMS.cfg but the user value should override that, no?
Any help or pointers most welcome!
-
Ok, found something. From olden times, my keyfile is based on 32 keys per device. So I just comment out the value of 128 in Falcon BMS.cfg and set it to 32 in the Falcon BMS User.cfg, right?
Wrong!
Upon launch, the Falcon BMS.cfg reinstates the value of 128 (it removes my // comment). And my value of 32 in the User.cfg is ignored. That should supersede the other cfg, no? What gives ?
-
@jayb my understanding is that if using the New Launcher mappings, it defaults to 128 per device, you can’t change that (as you saw it gets overwritten). if you change your DX numbering to account for 128 per device you might have better luck.
-
@Zeus Thanks you may be right. I might be able to build the key file using the launcher (since I find that convenient) and then use the “no override” option. Will investigate
-
@jayb - that “should” work from what I understand. Just keep in mind that the AUTO key file gets overwritten when using the New Launcher mapper so if you make any manual changes there, keep a backup.
-
@jayb don’t edit your ‘falcon bms.cfg’ file. it will be overwritten by Launcher/Config tools … and maybe future updates
DO edit your ‘falcon bms user.cfg’ file, and put the
set g_nButtonsPerDevice 32 set g_nHotasPinkyShiftMagnitude 256
lines there. BUT you’ll have to avoid using the New Launcher… or always take care to click the “launch without overrides” checkbox
-
@airtex2019
what does launching without overrides do? -
I’m wondering if this can solve my problems too… But I’m not sure how to proceed.
VR zoom will not function when in 3d - key and hotas binds don’t work. -
@AWmk1 said in Controls set up in Launcher do not work in-game:
@airtex2019
what does launching without overrides do?it “just launches” BMS … doesn’t overwrite your key file and button bindings
but for VR players, I think it becomes a pain to go back and forth from VR to non-VR
-
DO edit your ‘falcon bms user.cfg’ file, and put the
set g_nButtonsPerDevice 32 set g_nHotasPinkyShiftMagnitude 256
lines there. BUT you’ll have to avoid using the New Launcher… or always take care to click the “launch without overrides” checkbox
Back with 4.36 I always used the AL since it could support both 32 and 128 keys per device. Now it seems it does not have that fidelity anymore, enforcing 128, too bad.
Previously, whatever you set up in AL would work in the game. Now you can have things seemingly working in the new AL, but it will mangle everything during launch if you are not 128 compliant
-
Started setting up devices from scratch. I would like to use the new launcher so rebinding seems like a tedious task that I am unable to avoid.
-
importing xml files from AL in 4.36 to 4.37 should work…
-
-
My experience suggests that you can indeed move .xml files from 4.36 to 4.37, but only if they are already 128-based from 4.36