I did an update to the recently released 3.1-beta2 and then noticed that my mouse cursor was upside down and also had weird colors. I’m using inputManager.setMouseCursor(JmeCursor).
Tried different .cur files, and those who could load were all flipped.
Turned out it was LWJGL 3 that expects the image in a different format: RGBA instead of ARGB and, well, vertically flipped.
My guess is that the subset of folks who are using lwjgl3 probably don’t load cursors. Neither is all that common and the intersecting set is likely pretty small.
Yes, well, the cursor with LWJGL 2 was bugged for years with 3.0 and 3.1. So apparently the computer says no
To be be 100% accurate, it couldn’t handle too many changes. So if you had just one cursor, that would have been just fine. But even swapping between 2 would eventually crash your app.
@tonihele That’s good to know. From what I’ve gathered this was fixed for LWJGL3, right? (by using that HashMap)
@Empire_Phoenix That’s probably the reason why this wasn’t noticed. I also use a type of homegrown cursor to keep the “rotating icon” cursor at a fixed position when rotating a ChaseCamera.
Looks so hackish to mix this.
But it’s so much easier to use JmeCursor. Support for animated cursors in LWJGL3 would be nice though.