Thanks for the reply! Good to know that I don't have some brainfart regarding this issue.
I haven't solved the issue yet but it turns out that creating a device that registers itself as joystick (6 analog axis with 4 buttons) AND as keyboard is more flexible for what I want to do: That'd allow me to map the many buttons to actual keypresses, rather than relying on the receiving software (games mostly) being able to handle 30+ joystick buttons (some will, some won't). At the moment I have both reports working independently (seperate .hex files) but combining them into a single device causes Win to fail to register the device - more debugging![:)]( "Smile")
Thanks for the tip about sending multiple reports for > 8 byte, I didn't even think about that as an option. Definitely good to know.
Once the whole thing works I'll put up another community project.
I haven't solved the issue yet but it turns out that creating a device that registers itself as joystick (6 analog axis with 4 buttons) AND as keyboard is more flexible for what I want to do: That'd allow me to map the many buttons to actual keypresses, rather than relying on the receiving software (games mostly) being able to handle 30+ joystick buttons (some will, some won't). At the moment I have both reports working independently (seperate .hex files) but combining them into a single device causes Win to fail to register the device - more debugging
Thanks for the tip about sending multiple reports for > 8 byte, I didn't even think about that as an option. Definitely good to know.
Once the whole thing works I'll put up another community project.