[BUG] Wiimote won't work despite being detected by GLFW
Like I said in the title, a Wiimote can't be used despite being meant to work. I can confirm that it works using MidnightControls without any configuration change.
I read the source code, and saw a potential flaw :
In InterfaceInput.java, line 88, The function glfwGetJoystickName is used instead of glfwIsJoystickPresent, which is able to determine more than a absent/present state. This, in turn, could allow more advanced error detection. The failing detection may be the reason of why it will not work according to the logs (since the following call returns null and throws an exception).
Also, the GLFW documentation states that these functions MUST be called from the main thread, but is run into its own thread instead, and I don't know if it's the same for its Java implementation.
As a final note, I'm using Linux Mint 22.1 'Xia' x86_64, if that helps.
Here are the logs : https://mclo.gs/fQGScQr
Anyone can help me ?
Can you join the Discord and ping me there? I can make a thread and send you some betas for testing.
I actually am in Discord already, I am the one who found out where the threading issue in the radio system was
Well, looks like I've been banned from your server, I got no reason mentioned either the first time or second time. What in the actual f is happening @DonBruce64, I can't work on either this issue or the french translation if I don't even have a way to talk to you (and when I say no reason was provided to me, it's really that I got permabanned with no DM or anything)
Addressed in 23.0.0.
It... Uhhhh... Didn't work sadly... It still throws the same error, I wonder if that's not caused by the Wiimote-2022 driver I'm currently using or an implementation bug in GLFW. Either way I'm surely going to report this to GLFW instead as I think the NULL value was sent due to GLFW_PLATFORM_ERROR (a generic error that could involve the OS, drivers or a bad GLFW configuration, this error being the most likely). I will try building a local version with GLFW error debugging and I'll tell you if that was the issue.