search

chihirobelmo / FalconBMS-Alternative-Launcher

Configure and save FalconBMS setup per Joysticks.
Other
130 stars 30 forks source link

POV hats don't work until you've bound Pitch/Roll or Throttle axes to that device #110

Open arithex opened 11 months ago

arithex commented 11 months ago

Latest v2.4.x (currently in develop branch)..

Because BMS is limited to 2x pov (8-way) hats.. the POV-hat biz logic in AL was written to look exclusively at the device(s) bound to the pitch/roll- and throttle-axes. (This seems like a reasonable compromise, to cover the vast majority of setups.)

Testing and debugging the latest AL build (2.4.0.1), the pov-hat inputs don't show up at all (either preexisting bindings in the grid-view, or attempting to define new bindings) until you've defined either roll- or throttle-axes on that particular device.

It appears AL does actually accept the pov-input, invisibly, and record it in the XML data model .. but no visual feedback for the pov input appears in the keymapping dialog, or the datagrid .. and no pov lines are written out to BMS-Auto.key.

But, if you tab over to the AxisMapping screen, then map pitch, roll or throttle to your device, suddenly your POV mappings will appear.

This is a difficult UX problem, considering BMS limitation of 2 pov hats.. need to think about how this should work, if we need/want to support 8-way hats on devices that are not the primary stick or throttle. (How common is this? not sure)

arithex commented 11 months ago

related: https://github.com/chihirobelmo/FalconBMS-Alternative-Launcher/issues/102

arithex commented 11 months ago

I guess this is a very old issue, not a recent regression.. that's both the good-and-bad-news. related: https://github.com/chihirobelmo/FalconBMS-Alternative-Launcher/issues/41