Buttons loosing assignments
-
Seems not. Grrr. Your fix sorted it. Until next time I booted up BMS. Same button, not recognised. I suppose all the technical shenanigans is part of the fun.:D
Strange. Are the axis kept and only the buttons not working anymore ?
Multiple keyfiles ? I only keep one so I am certain it does not switch.
Only one “profile” (logbook) ? Because switching logbook also affects the controls (keyfile IIRC) -
All as before. Throttle ( 22 buttons assigned including 3 with mode shift) and stick (16 buttons assigned including 2 with mode shift.Setup only used for BMS. Just one (same) button, responding in CH Manager(and map downloading to BMS) , but not being recognized in the GUI. Maybe I’m using too many buttons.
-
I have no idea about the “mode” function of your controller.
But, maybe, here is a guess :
Every time you change the mode, BMS sees it as a new controller, with a new ID.
This messes the bindings up.Other than that, I don’t know…
The important part is that the controllers always have the same order, dictated by the devicesorting.txt file.
That makes that even if windows reorganises the directx controllers, the buttons you have assigned to a specific controller stay bound and work.Can you post the content of the devicesorting.txt file ?
A simple “hack” is when everything works, you modify following files to have them read only in windows :
DeviceSorting.txt
axismapping.dat
joystick.cal
your keyfileThis will make that BMS cannot modify them anymore. But beware that you won’t be able to modify your controller in BMS anymore, and you will need to put them back in read/write in order to modify them
-
The CH throttle has three modes ( operated with a modifier switch) so in theory you can use each of 20 odd “buttons” in 3 different ways and therefore create about 60 buttons as well as triple the "buttons"on the Stick. I use this function sparingly, though, and only have 3 modified buttons on the throttle and 2 on the stick. Works like a shift function.
This is what my devicesorting.txt file looks like- after swapping stick and throttle lines, as you suggested:
{C0F4068E-0000-0000-0000-504944564944} “CH Combatstick USB”
{C0F1068E-0000-0000-0000-504944564944} “CH Pro Throttle USB”
{C010068E-0000-0000-0000-504944564944} “CH Control Manager Device 1”
{C011068E-0000-0000-0000-504944564944} “CH Control Manager Device 2”Once I have everything working, making those files as you recommend, read only, sounds like good advice.
-
In my opinion, the issue comes from those two devices :
{C010068E-0000-0000-0000-504944564944} “CH Control Manager Device 1”
{C011068E-0000-0000-0000-504944564944} “CH Control Manager Device 2”They must be those 3 modes (1 is the standard throttle, two other are those devices).
If you do not have your throttle in “mode 1” when starting BMS, it might screw the assigning.But I don’t know more.
-
I think “CH Control Manager Device 1” and "CH Control Manager Device 2"is the way CH software links devices and is nothing to do with modes. But the more I read on this forum the more I realize what I don’t know. Thanks for your kind ideas though!
-
I think “CH Control Manager Device 1” and "CH Control Manager Device 2"is the way CH software links devices and is nothing to do with modes. But the more I read on this forum the more I realize what I don’t know. Thanks for your kind ideas though!
Hi,
Watch this BurnerTactical video on your YouTube channel.
Maybe you can solve your problem !!!
Link:
Good flight !!!
Best Regardsmalpaso
-
Thanks Malpaso. The video was interesting, especially the piece about making the files read only- once all is working.I don’t know if you use a CH hotas. Mine has worked very well until now using DX assignments. My problem is that I now have one button that reacts in CH Manager, but has stopped responding in BMS so its not a hardware problem and doesn’t seem to be an assignment conflict. Yesterday I fixed it thanks to Flow32’s kind advice, or so I thought,and now its re appeared….
-
Thanks Malpaso. The video was interesting, especially the piece about making the files read only- once all is working. Same advice that Flow32 kindly gave.
i think my problem is solved. Went into CH Manager and simply gave the offending button a different random number. It now responds in BMS GUI although there was apparently no conflict before. And they say computers are logical….
So I’ve now made the relevant files read only.:D
-
Thanks Malpaso. The video was interesting, especially the piece about making the files read only- once all is working. Same advice that Flow32 kindly gave.
i think my problem is solved. Went into CH Manager and simply gave the offending button a different random number. It now responds in BMS GUI although there was apparently no conflict before. And they say computers are logical….
So I’ve now made the relevant files read only.:D
Very cool that you have been able to solve, danster.
My joystick is X52 PRO, but I’m going to buy a Fighterstick and a Pro CH Throttle.
Now just enjoy the BMS !!!
Good luck !!!
Good flight !!! :plane:malpaso