Building a fightstick with a Daemonbite. Works correctly with MiSTer but not with Windows. Analog axis shows correctly in the game controllers control panel, calibrated. DuckStation input overlay shows constantly pressing right + down. Multiple online gamepad testers show Axis0 and 1 to have a range of 0, 157, and 315. These websites use the "Windows gamepad API".
315 is weirdly specific. Found it being used for the PHYSICAL_MAXIMUM attribute of the HID descriptor.
Commented out the PHYSICAL_MINIMUM and PHYSICAL_MAXIMUM attributes from the descriptor, now the online testers are showing axis values of -1, 0, and 1.
Building a fightstick with a Daemonbite. Works correctly with MiSTer but not with Windows. Analog axis shows correctly in the game controllers control panel, calibrated. DuckStation input overlay shows constantly pressing right + down. Multiple online gamepad testers show Axis0 and 1 to have a range of 0, 157, and 315. These websites use the "Windows gamepad API".
315 is weirdly specific. Found it being used for the PHYSICAL_MAXIMUM attribute of the HID descriptor.
Commented out the PHYSICAL_MINIMUM and PHYSICAL_MAXIMUM attributes from the descriptor, now the online testers are showing axis values of -1, 0, and 1.