Solved Cockpit wheel brakes not working in 4.37
-
4.36 had no problems using “k” or a DX command using alt launcher. I have alt launcher 2.20 the latest version and 4.37 recognizes the command, inside BMS it recognizes the command, but in the sim it won’t wheel brake. I go right to 4.36 to test and everything works fine. Weird, need insight please!
-
@WPNS24 if you have an analog axis mapped to the toebrakes (left, right or both) then the ‘k’ key callback won’t do anything
look at Setup/Controllers/Advanced/Flight to check
-
@airtex2019 no, I have the 16000TM and I don’t use the toe brake z axison my throttle, all these years I have only used the k command or the DX3 on my stick. alt lx and BMS both read and display that I am hitting that exact key but doesn’t work in sim
-
@WPNS24 I hear you, but that’s the only thing I can think of.
eg. do you have, or did you ever, any game controllers or other devices plugged in, that the Launcher might have auto-assigned as a brake axis, without your knowing?
-
@airtex2019 no sir, that’s the weird thing, there has been no changes or additions to my PC, but i do appreciate the help tho
-
I had to map “CKPIT: Wheel Brakes - Hold” to “k” (in Falcon BMS Launcher v2.2.0) and it works OK for me
-
@steve6 same, but it doesn’t work in-game
-
This post is deleted! -
?
-
@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.