Button mapping gets lost 4.37
-
Hello,
Mapping of the buttons in the launcher keeps getting lost. Any suggestions?
Thanks! -
You need to select the correct saved file in the main game -> setup… ie Load… then select the same name as saved in the Launcher.
-
There are things that can cause this, but I would need more detail before spewing random advice. Is it something that happens occasionally, or every time you start, or what?
-
@Clutch said in Button mapping gets lost 4.37:
Hello,
Mapping of the buttons in the launcher keeps getting lost. Any suggestions?
Thanks!Hi, Clutch, what Airtex said However, if you are making settings inside the UI and the disappear when you use the 4.37 launcher, that is the way the Launcher works. It overwrites what is done in the UI. So, if you use the Launcher “keybinds” you should be good. However, if you are using the Launcher and still having problems, then Airtex is right. We need more info.
-
@drtbkj I’ve only been using the launcher and it happens occasionally, not 100% sure at the moment . I just recently set everything up. I searched for the functions I wanted in search and assigned buttons and that’s it. For instance LASER, autopilot modes.
-
My workaround:
Do your button mapping:
Save it
Alt tab to desktop en find the axismapping.cfg file
Right mouse click: Select properties: then mark the read only option.
Then apply.Not my idea, its an old workaround that works for many falcon versions.
-
@Clutch one thing to be aware, if unplugging/replugging your devices, they may get new IDs and the Alt Launcher will get confused and lose the mappings.
All you can do, is try to keep things plugged into the same physical USB ports.
And maybe try to plug them in, in consistent order? Idk… This seems to affect some PCs more than others. Some quirk of bios or usb controllers, perhaps.
-
@airtex2019 thank you. I completely forgot that I recently updated the firmware of my winwing F16Ex throttle. That’s probably the reason. Is it possible to make a backup of some file or after every update I will need to reassign all the buttons and switches? Perhaps only the switches on the base, since handle buttons were detected automatically.
-
@airtex2019 Indeed.
I am still building my cockpit and sometimes I have to disconnect one of the consoles to take it to another room or the garage to work on it. When connecting it again, settings can be lost.
Yesterday it happened again and assigning everything again is a real pain. Specially since the launcher keeps reverting to a “home” state when you assign one button of a device. E.g. assigning all buttons of the MFD’s then turns out to be a real pain with endless clicking for each button.
-
Yep, I’m having the same issue with the alternative launcher losing mappings from time to time. I’ve assigned everything using AL, but sometimes (usually when switching among BMS versions) it will lose some key file settings, mostly on my StreamDeck XL which I use as a poor man’s ICP.
I’ve taken to copying the latest BMS - Auto.key file somewhere safe and whenever AL screws up, I simply copy it back to my BMS instances after exiting AL and then usually all is well again.
Cheers, Uwe
-
@hoover your solution is the best, for the near term.
The way AL identifies each device, when saving its XML files, is different than the way BMS does… AL uses the “device instance guid” from the OS… which is subject to change. BMS uses the “productId+vendorId” which is very stable… but can be ambiguous if you have 2+ of same device.
I’ve been submitting a few bug fixes for AL but this would be a big one… and it’s probably too late for U3.
I’ll make sure an issue is filed…
…done
https://github.com/chihirobelmo/FalconBMS-Alternative-Launcher/issues/105 -
@Nurse said in Button mapping gets lost 4.37:
Not my idea, its an old workaround that works for many falcon versions.
I don’t know if it was always true, but AL is more aggressive than that – it overrides the ReadOnly flag for all the files it overwrites.
I’ve whined about that in the past here, I’m sure… but after working on the serialization code, I have a bit more empathy – the alternative would mean, bombing out after updating some of the files but not all of them, leaving them in a mutually-inconsistent state (and probably a crash, later).
Probably right thing to do would be a popup warning msg… “Hey this file is readonly, please fix that and try again, otherwise all bets are off and you’re on your own.”
-
@hoover Thanks!) I’m gonna try this solution.
-
@airtex2019 Thank you!