Can BMS support/see more than 32 DX buttons?
-
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…
-
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.
JG can do a lot of things. If you want to do any crazy shit with your HOTAS, there’s a good chance JG can do it.
-
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/
Blu3wolf…is your site recognized by the BMS Devs as authoritative? I’m not casting stones…just wondering if I do this, will it matter? Thanks!
-
JG can do a lot of things. If you want to do any crazy shit with your HOTAS, there’s a good chance JG can do it.
I agree with you…for HOTAS only; however, if you are running a bunch of >32-button custom left/right panels, JG and Vjoy is not scalable…starts throwing exceptions, etc.
-
Blu3wolf…is your site recognized by the BMS Devs as authoritative? I’m not casting stones…just wondering if I do this, will it matter? Thanks!
Authoritative?? No. But some of us do try and pay attention. Actually the biggest issue with that bug DB is the dump-and-run behavior…we’ve seen a lot of people put reports in there and then abandon the discussion, no reply to follow up questions etc. This makes it a lot less useful for us to spend time on as you can probably imagine.
-
Blu3wolf…is your site recognized by the BMS Devs as authoritative? I’m not casting stones…just wondering if I do this, will it matter? Thanks!
Authoritative?? No. But some of us do try and pay attention. Actually the biggest issue with that bug DB is the dump-and-run behavior…we’ve seen a lot of people put reports in there and then abandon the discussion, no reply to follow up questions etc. This makes it a lot less useful for us to spend time on as you can probably imagine.
Perfectly sums it up I think.
Ill add a little: Its not intended to be authoritative - BMS already has a bug tracker. This is intended to be a community bug tracker. Like with any community effort, it depends on its users to put effort in - its only as useful as we make it. This is also a limitation of bugs posted to the support forum, which are not always followed up on by users.
The tracker is intended to be an easier alternative to posting a forum thread in the support forum. Those work… but keeping track of those issues, as a user, is a pain. Trying to see if your issue has already been reported could be much easier, and that is what the community bugtracker is intended to address.
As far as will it matter… I like to think it matters, but bmsbugs is not a guarantee of any support on the part of the BMS devs. It is an opportunity for community members to make devs and the community aware of issues you are experiencing, and it is an opportunity to seek support in the form of workarounds, and hopefully fixes in future BMS versions. I am very grateful to the BMS team for their efforts in bug fixing and especially to those who have spent time triaging bugs on the public tracker.
In other words… I dont see the tracker as directive, but informative.
-
Folks, I added this to the requested/referenced web site. https://bmsbugs.blu3wolf.com/view.php?id=188
Thanks for your time and attention. I hope this makes the cut for a future near-term release.