-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exception with old version of jogl library on ARM Mac #18
Comments
It does indeed, however it also drops support for 32-bit Windows, which is used by far more people than MacOS, so it is not used by default by the client. It can be used manually, however. The official client has a separate launcher for it available at https://www.havenandhearth.com/java/hafen-jogl-2.5.0-launcher.jar. For building it from source, you can remove the The JOGL guys have said that they will bring 32-bit Windows support back with 2.6.0, so at that point I expect to be able to upgrade the JOGL version used by default. |
You might also want to try whether the LWJGL renderer works for you on MacOS. To do so, set the |
I see. I didn't know that 2.5.0 dropped Win32 support and that there're still some Win32 users out there! I'll try LWJGL to see if that works, but building with a local copy of 2.5.0 works too, I was mostly concerned about other users encountering same problems, like this or this. They're not numerous, but still. |
Yes, I agree, and it would be very nice to fix it, but for now I think it is what it is, unfortunately. I'm hoping it won't be too long until 2.6.0 is released, but JOGL's release pace has been up lately, so I think there's a good chance.
Just FYI, it's not so much that people use 32-bit Windows, as it is that they're using a 32-bit JVM on 64-bit Windows. Apparently, java.com still distributes 32-bit JVMs by default for whatever reason. |
Issue
Locally built client on ARM Mac produces an Exception:
Repro steps
ant bin
commandant run
commandSystem specs
java --version
:javac --version
:ant -version
:Proposed solution
Latest release of jogamp library fixes this issue, so it can be beneficial to update jogamp library fetched from the website to the new version.
When
.jar
files are replaced inlib/ext/jogl
directory with the new release (https://jogamp.org/deployment/v2.5.0/archive/) this error goes away.The text was updated successfully, but these errors were encountered: