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.

@sungad:

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:

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!

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.

@oakdesign:

No the newer implementations of Directnput API supports up to8 axis and 128 DX buttons per device.

This is what I’ve read, too. It can be done using various methods (e.g., lua, etc.).

@oakdesign:

But where is Gremlin vjoy setup buggy. I personal have a X65F which is a single device with 50 buttons.
Only splitted it up once into 2 virtual devices with 20 and 30 buttons. That a step that only has to be done once and never had to change it afterwards.

This is true for basic setups, and it worked for my X65F, too; however, if you buy a USB simulation device, such as the various Viper panels coming out, each must be split into 2-3 vjoy devices. This rapidly resulted in more complex configurations. And if you buy them one at a time to fit within a budget, Joystick Gremlin threw exceptions when modifying them after a certain point, at least for me.

The “shifting” capability is outstanding in BMS…but it doesn’t fix the example configuration above. Having integral support by the simulation, since there are solutions available, would avoid all the third-party software pain, IMHO.

Thanks for your time and effort, Icer and Oakdesign!

@oakdesign:

I suppose none. If you want to overcome the 32 button Limit per USB device I suggest to go split to multiple virtual devices with JoystickGremlin and vJoy route

Roger…been there, done that, got the t-shirt. Too buggy when making changes. Unfortunately for me, at this time, I’m off BMS until we get native support for above 32 buttons. Thanks for your reply.

What are the R&D plans to support beyond a 32-button limit per USB device?

Thanks in advance.

Best wishes, brother, for a speedy and full recovery.

@Gastone:

It was explained in one of the update notes a few patches back. At one point it was also described in the manuals, then omitted with the most recent update. Anyway, it’s explained below. You have to edit the flacon BMS .cfg file

POV MAPPING:

— Added possibility to override POVs mapping across different devices. (r19837)
  * New config vars (defaults shown here):
	set g_nNumOfPOVs -1 // Override number of POV hats. Should be in 0 - 2 range, -1 is override disabled (default)						
	set g_nPOV1DeviceID -1 // Override POV1 hat device ID, -1 is override disabled (default)
	set g_nPOV1ID 0 // Override POV1 hat ID. Should be in 0 - 1 range
	set g_nPOV2DeviceID -1 // Override POV2 hat device ID, -1 is override disabled (default)
	set g_nPOV2ID 0 // Override POV2 hat ID. Should be in 0 - 1 range
  * Example for a Warthog setup (sets joystick POV as POV1 and throttle POV as POV2):
	set g_nNumOfPOVs 2 						
	set g_nPOV1DeviceID 2
	set g_nPOV1ID 0
	set g_nPOV2DeviceID 3
	set g_nPOV2ID 0

Update…needed to flash the ICP with MMJoy2, and all is working as required. Sorry for the false alarm…POV shows as DX buttons for callbacks.
db

@Gastone:

It was explained in one of the update notes a few patches back. At one point it was also described in the manuals, then omitted with the most recent update. Anyway, it’s explained below. You have to edit the flacon BMS .cfg file

POV MAPPING:

— Added possibility to override POVs mapping across different devices. (r19837)
  * New config vars (defaults shown here):
	set g_nNumOfPOVs -1 // Override number of POV hats. Should be in 0 - 2 range, -1 is override disabled (default)						
	set g_nPOV1DeviceID -1 // Override POV1 hat device ID, -1 is override disabled (default)
	set g_nPOV1ID 0 // Override POV1 hat ID. Should be in 0 - 1 range
	set g_nPOV2DeviceID -1 // Override POV2 hat device ID, -1 is override disabled (default)
	set g_nPOV2ID 0 // Override POV2 hat ID. Should be in 0 - 1 range
  * Example for a Warthog setup (sets joystick POV as POV1 and throttle POV as POV2):
	set g_nNumOfPOVs 2 						
	set g_nPOV1DeviceID 2
	set g_nPOV1ID 0
	set g_nPOV2DeviceID 3
	set g_nPOV2ID 0

Roger…copy, Gastone, and I saw your post on the matter, which I followed your example. This is what is in my Falcon BMS.cfg file:
//////////////////
// POVs mapping //
//////////////////
set g_nHotasPinkyShiftMagnitude 352
set g_bHotasDgftSelfCancel 0
set g_b3DClickableCursorAnchored 1
set g_nNumOfPOVs 2
set g_nPOV1DeviceID 5
set g_nPOV1ID 0
set g_nPOV2DeviceID 2
set g_nPOV2ID 0

This is what is in my Falcon - BMS.key file for POV1 on my TM Warthog, which works:
#======== Joystick - HOTAS Warthog : POV ========
SimDMSUp 0 -1 -3 0 0x0 0
SimDMSRight 0 -1 -3 2 0x0 0
SimDMSDown 0 -1 -3 4 0x0 0
SimDMSLeft 0 -1 -3 6 0x0 0

Windows10 sees both devices, and when I go into the ICP device in the DEVICES/PRINTERS under Control Panel, the POV registers and shows me the proper positions. Further, when I do have Alternative Launcher in use, it too sees the movements of the DCS on the ICP, but I cannot assign a BMS DX callback.

What I think_think I need is a similar entry in my KEY file to the above, which would then allow me to assign BMS callbacks to POV2 on the USB ICP. Right?

Thanks in advance, and appreciate your time. I hope I made my predicament a bit more clear.
db