Can BMS support/see more than 32 DX buttons?
-
New knowledge (to me) is that Direct X now supports 128 DX assignments now (since what version, no idea), but BMS seems limited to 32. I can run a Target script to give my Warthog throttle full use (on/off/middle) of all 2 and 3 way switches with +32 buttons but BMS does not see them, is this a limitation of the software or something that can be changed? I currently use the “Release” function to get the same functionality but would “like” to run the same controller in all sims…
-
At this point, no. I’ve made the request a few times in the wishlist thread, but it just hasn’t gotten any traction so far. I’m thinking if it was an easy task, it probably would have been done already considering how many cockpit builders there are out there.
-
May I suggest you try RS Mapper? Worked like a charm for me, and manage to use switches with little to no problems in both BMS and DCS. Good luck.
-
May I suggest you try RS Mapper? Worked like a charm for me, and manage to use switches with little to no problems in both BMS and DCS. Good luck.
I may take a peek at that but as it stands I can just run the TARGET profile when i’m in IL-2 & DCS, stop it and run BMS. I have use of every switch position in BMS simply using the “Release” function of Alt Launcher, I would just like to run TARGET and use it for ALL sims but we can’t always get what we want…. i’m amazed IL-2 sees all the +32 DX presses, it’s pretty old also!
-
Would be a bit of a rewrite of the code, I would imagine… seeing as the button numbers are currently informative as to which device they came from: By definition currently, buttons 1-32 (numbered from 0 to 31) are from device 1 (numbered device zero). In integer math, the button number divided by 32 equals the device number.
Id imagine that most folks with devices less than 32 buttons would not care, so its likely been a low priority to date.
Perhaps this is worth adding as a feature request on https://bmsbugs.blu3wolf.com/
-
Doing it in a way that’s not a breaking-change for all the existing key files out there, would be the challenge.
Surely solvable… but I won’t say “easily” without looking at the code.
-
New knowledge (to me) is that Direct X now supports 128 DX assignments now (since what version, no idea), but BMS seems limited to 32. I can run a Target script to give my Warthog throttle full use (on/off/middle) of all 2 and 3 way switches with +32 buttons but BMS does not see them, is this a limitation of the software or something that can be changed? I currently use the “Release” function to get the same functionality but would “like” to run the same controller in all sims…
Can BMS support/see more than 32 DX buttons?
To my knowledge - and as i am using it YES. (Virpil Stick and Throttle, which is split by hardware-software into 4x 32DX devices).
-
@A.S:
Can BMS support/see more than 32 DX buttons?
To my knowledge - and as i am using it YES. (Virpil Stick and Throttle, which is split by hardware-software into 4x 32DX devices).
Unfortunately it’s not how many buttons it supports across virtual or physical devices (I have 5 32 button devices working in BMS), it’s BMS’s DirectInput not supporting DX33-128 that is the issue.
-
TARGET was a nightmare fore me, and felt I was asking for my devices to get bricked. It is a little work with RS Mapper, because you need map a keyboard combination for every command, then go in to BMS and put the same key combinations for every switch, but it doesn’t mess around at firmware level, and will work with empty switch positions that you can’t normally bind even in newer games like DCS for who knows what reason.
-
TARGET was a nightmare fore me, and felt I was asking for my devices to get bricked. It is a little work with RS Mapper, because you need map a keyboard combination for every command, then go in to BMS and put the same key combinations for every switch, but it doesn’t mess around at firmware level, and will work with empty switch positions that you can’t normally bind even in newer games like DCS for who knows what reason.
I hear ya, and I really wanted no part of TARGET and had heard of the nightmares but someone wrote this script up and I did not see anyone with issues with it so figured WTH… It only programs my Throttle, and when I stop the script Win10 immediately goes from the “Thrustmaster Combined DX128” name to the back to “Throttle - HOTAS Warthog” and all is well in BMS. I actually took a guess and added two buttons that were neglected (the Idle Cutoff would send (one for each throttle) a DX press when you went from Idle Cutoff to Idle but nothing going the other way. Added two lines with “OFF” where the ON was in the lines above, went to the next 2 DX #'s available, and it works perfectly!
Ex., what I guessed at in Red… and that is “48”, not 4Smiley…
MapKey(&Throttle, IDLELON, PULSE+DX48);
MapKey(&Throttle, IDLERON, PULSE+DX49);
MapKey(&Throttle, IDLELOFF, PULSE+DX50);
MapKey(&Throttle, IDLEROFF, PULSE+DX51) -
You can map the other buttons to virtual devices with Joystick Gremlin and vJoy.
-
My Cougar joystick does 43 assignments. All DX.
-
You can map the other buttons to virtual devices with Joystick Gremlin and vJoy.
Thanks Sungad, but the idea is NOT to use a 3rd party software if not fully necessary, and if I have to use one i’m perfectly happy with the TARGET profile I run now… BMS is the only sim I use that does not see above 32 buttons and ALT Launcher takes care of that with it’s RELEASE function (for me).
My Cougar joystick does 43 assignments. All DX.
Icarus, so for you BMS shows you pressing DX buttons 33-43? Please enlighten me on how that is done with or without 3rd party software!
-
Sorry I misunderstood. I said assignments not buttons on my Cougar. I forgot my Warthog had so many throttle buttons. I use my Warthog throttle for anything but BMS.
-
The optimal solution would be to upgrade BMS to allow the 128-button per device option, all without breaking old-school, working configurations using 3rd-party software.
-
You might want to give vJoy and Joystick gremlin another look, at least eventually. I used TARGET myself and vJoy/Joystick Gremlin is much easier to work with. With TARGET, sometimes I’d have to troubleshoot for 30 mins to figure out what was blocking the virtual device creation. I missed a 12 person 440VFW wing flight once because I couldn’t get my profile to start for over an hour and countless reboots. vJoy creates virtual devices that are always available. You configure it once and leave it until you need additional devices. You don’t have to worry about whether or not launching the target profile will work because the virtual device coexists with the actual device and then you use Joystick Gremlin to assign functions to your virtual device. There’s 56 dx buttons on my Winwing Combat Panel. I took everything after 32 and moved them to my virtual device. Now I can use all functions in BMS.
If you ever move away from or add non Thrustmaster devices, then you’ll have to find a new solution. vJoy and Joystick Gremlin works with everything. I could have hacked apart my warthog stick base to put the electronics in my FSSB Litening but destroying perfectly good hardware to use a frustrating software solution wasn’t sensical.
-
I found the TARGET script already finished and other than to add two lines the author didn’t need or think of for entering Idle Cutoff it works flawlessly so far. I click RUN, it loads and all is good, I click STOP and all is back where it was for BMS in Alt Launcher. It is ONLY for the Warthog throttle and its switches. Of course if it starts giving me headaches I will look elsewhere, but right now i’m good… Thanks for the input!
-
If I remember correctly I can assign all of the toggles and buttons for my warthog stick and throttle with the keyfile editor that is in the docs folder. Except for hat #2 on the throttle that has to be done with the BMS UI and idle detent which I added a couple lines in my keyfile to get to work.
Edit: Please disregard as I misunderstood that you are looking for an all in one solution for all of the sims you fly.
-
Unfortunately it’s not how many buttons it supports across virtual or physical devices (I have 5 32 button devices working in BMS), it’s BMS’s DirectInput not supporting DX33-128 that is the issue.
i see.
-
If I remember correctly I can assign all of the toggles and buttons for my warthog stick and throttle with the keyfile editor that is in the docs folder. Except for hat #2 on the throttle that has to be done with the BMS UI and idle detent which I added a couple lines in my keyfile to get to work.
Edit: Please disregard as I misunderstood that you are looking for an all in one solution for all of the sims you fly.
Exactly. While my current solution requires a 3rd party (TARGET) it is a s seamless as possible (until TARGET blows up or bricks my Warthog… :eek: ). Reality is I NEED Target for DCS and IL2 (no easy way to get the “off” toggle position to register) but do not need anything for BMS as it does indeed register the “release” of a switch. I would prefer not to run any “middleman” programs but gotta do what I gotta do…