lazycow wrote on Friday, March 20, 2015:
hi, seems like on Mac OS and Linux the (usb) joysticks are only detected if they are already plugged in when starting the program. (on windows, a joystick is detected after that, somehow)
But it’s on the “fixed” list for 3.1.1. Did I do something wrong or is it only fixed for Windows?
lazycow wrote on Saturday, March 21, 2015:
Hm, you’re right. the joystick test program in the test folder of glfw detects a new joypad on Linux. There must be a problem in my code somewhere. Thanks for the info!
But on Mac, this still does not work. The 3.1.1 even changed the axis layout of my joypads. (not a big deal, but I wonder why)
snowgoon88 wrote on Thursday, June 25, 2015:
Hi, I have the “reverse” problem sometimes :o)
I’ve tried two different kind of Xbox pads, one of them can only be recognised if plugged /after/ glfwJoystickPresent() is repeatedly polling for its presence. If I plug it before glfwInit() or between glfwInit() and the first glfwJoystickPresent(), it is recognised as present (its type is found) but buttons and axes can not be read => set to a fixed value.
It’s an “ACRUX HAMA X-Style Pad”
No problem with a “Generic X-Box pad” from Logitec.
Any ideas of the hidden reasons behind this strange behavior ?