Solved Cockpit wheel brakes not working in 4.37
-
?
-
@airtex2019 still no difference, still doesn’t work
-
You could try clearing out any mapping from “CKPIT: Wheel Brakes - Hold”: Use Clear DX, Clear Key, then Save. Then launch BMS once just to make the empty keymapping stick.
Then leave BMS, re-assign the K key to that mapping. It should work then. If not, last resort is chihirobelmo
-JayB
-
@jayb Tried it, no joy. BMS recognizes it being assigned and not assigned just doesn’t work. I’ve also tried different keybindings and such
-
@WPNS24 try deleting your axisMapping.dat and joystick.cal files… let the Launcher recreate them.
If there’s a file with name like ‘Setup.v100.*.xml’ that referneces your “wireless controller” delete that too.
Start the launcher, with just stick and throttle plugged in … no wireless controller. Verify the axis assignments are the way they should be. Save, and launch BMS.
-
@WPNS24 look for the following on ALT launcher. Make sure no axis is assigned to toe brakes. https://forum.falcon-bms.com/post/347057
-
@danaos75 will check both of these. but if i pull up alt launcher and it shows 4.36 and 4.37 together wouldn’t there be an issue with both versions of BMS? I’m not a computer code guy but just seems weird 2 different games in the same launcher aren’t coorealting together but I do know simple little things can mess up a coded line. will try these 2 suggestions tonight
-
@WPNS24 different versions can (and do) have different features… eg. the new ECM stuff in 4.37. and commands to recenter-VR headset, etc. so there definitely must be room to have different key/button bindings, across different versions
less likely for device->axis mappings to differ, across versions, but possible.
-
@airtex2019 Tried it, nogo
-
@danaos75 YESSIR!!! For some reason it was assigned in 4.37 and since I never ever use it I never thought about “unassigning” that axis. Crazy but it works perfect now, just going in and unassigning those controls. Amazing support you guys, thanks!!
-
@airtex2019 all good now, TY very much for your assistance. In 4.37 alt lx the toe brakes got assigned somehow, remove the designation and works as advertised
-
@WPNS24 excellent, glad we got that sorted …
if ever in doubt, check the in-game Setup screen (Setup / Controllers / Advanced / Flight) … it will show “Keyboard” as the axis for left- and right-toebrakes.
Meaning, essentially “no axis just buttons/keybd” for this flight function.
-
@airtex2019 Yessir, I’m going through and screenshotting all assignments as well as updating my excel button spreadsheet. Just another thing that is such a small detail can derail the whole operation!
-
-
@WPNS24 I think there is valuable feedback in this thread… the UI within the new launcher could be more clear, which axes are bound and which are not – especially if it’s an axis that’s currently at zero value… eg. an unused vJoy axis.
Here is mine… I have a single axis assigned to “Toe Brake” but none assigned to “Toe Brake Right”. Ok, there is a grey text label “JOY 0 : Z” but it’s easy to overlook – the button label is brighter and bolder, and says “Assign” implying there’s nothing assigned there yet.
-
@airtex2019 Yeah before Alt lx I had to use Target Script and that was a nightmare, Alt Lx is awesome but every time something updates, I need to be more careful and go over every input
-
@WPNS24 Once you get things exactly the way you like, it helps to make a little “last-known-good” backup folder for your User/Config directory.
Else sometimes you may start up with an extra device plugged in … or your hotas unplugged … and things end up scrambled.