While I'm able to resolve my issue by simply restarting my computer, other people that have had similar issues were only able to resolve the issue after unplugging any additional monitors, and some people are unable to resolve the issue at all.Īlso possibly That's a similar error, but not the same - both fail at line 100 of Checks.java, but get there through different failing sections of LWJG元. Java Version: OpenJDK Runtime Environment 11.0.12+7-Ubuntu-0ubuntu3 Still, I'm intrigued, and would like to get to the bottom of it.Īt .glfwGetFramebufferSize(GLFW.java:4831)Īt .(NiceLwjgl3Application.java:439)Īt .(NiceLwjgl3Application.java:377)Īt .(NiceLwjgl3Application.java:363)Īt .lwjgl3.NiceLwjgl3Application.(NiceLwjgl3Application.java:77)Īt .main(LegacyDesktop.java:117)Īt .Main.launchGame(Main.java:70)Īt .Main.main(Main.java:38)Īt java.base/.invoke0(Native Method)Īt java.base/.invoke(NativeMethodAccessorImpl.java:62)Īt java.base/.invoke(DelegatingMethodAccessorImpl.java:43)Īt java.base/.invoke(Method.java:566)Īt .$0(WilderLauncherService.java:68)Īt .launch(LaunchServiceHandlerDecorator.java:37)Īt .launch(LaunchServiceHandler.java:54)Īt .launch(LaunchServiceHandler.java:72)Īt .run(Launcher.java:82)Īt .main(Launcher.java:66) Though I expect there are circumstances where a headless JRE wouldn't work with LWJG元, such as when using gdx-dialogs. I haven't and won't go testing that with every JRE on every OS. Point is, I think headless only matters for LWJGL2, where you get a Exception in thread "LWJGL Application" : Can't load library: /usr/lib/jvm/java-11-openjdk-amd64/lib/libawt_xawt.so or similar if using it. LWJG元 worked for me with openjdk11-jre-headless. We had offered that maybe he had a headless JRE, but I don't think that proved to be the case. If this is the case, perhaps LWJG元 could use the libraries from the JAR instead of first copying them (what is this reason for this - faster access speeds?) or simply give a warning if the user has less than, say, 10MB available on their C: drive or equivalent.Īt .(Lwjgl3Application.java:491)Īt .(Lwjgl3Application.java:415)Īt .(Lwjgl3Application.java:401)Īt .lwjgl3.Lwjgl3Application.(Lwjgl3Application.java:113)Īt .MainKt.main(main.kt:101)Īt .MainKt.main(main.kt) Stack traceĮxception in thread "main" Īt .check(Checks.java:100)Īt .nglfwGetMonitorWorkarea(GLFW.java:1127)Īt .glfwGetMonitorWorkarea(GLFW.java:1158)Īt .(Lwjgl3Application.java:482)Īt .(Lwjgl3Application.java:404)Īt .(Lwjgl3Application.java:390)Īt .lwjgl3.Lwjgl3Application.(Lwjgl3Application.java:111)Īt .DesktopLauncher.main(DesktopLauncher.java:10)ĪL lib: (EE) alc_cleanup: 1 device not closedĪfter resolving itself like magic, the new theory is this was caused by a lack of disk space. maybe every version of libGDX that supports LWJG元. Version of libGDX and/or relevant dependenciesġ.10.0, I think also 1.9.11. This was tested on both Corretto 14 and AdoptOpenJDK 14. It's unknown if non-libGDX LWJG元 stuff is also broken, but I think it's likely. I doubt anyone would manage to reproduce it intentionally). Run a LWJG元 libGDX application on his computer (yeah. Though it's basically our only lead.īoth gdx-setup's output project and gdx-liftoff (the tool itself - not its output, as the tool couldn't be run due to the same error) were tested, and LWJG元 was enabled for the project using the instructions on the website.
He was having issues installing(/updating?) GeForce Game Ready graphics drivers, but I'm uncertain that's related due to the fact LWJGL2 works and normally you'd also get Description : WGL : The driver does not appear to support OpenGL and a GdxRuntimeException: Couldn't create window if OpenGL is broken, neither of which happened here. But LWJGL2 does work, as do games, and I guess the rest of your usual everyday computer activities also work. I don't mind if this issue gets closed, so long as it remains available for viewing. It's possible his computer's just completely screwed, but I'd like to document the noteworthy parts here, mainly in case anyone in future has the same issue, at which point the Discord messages will have been lost to time (and they can't be viewed publicly anyway).
There's also an older "gdx-liftoff NullPointerException" thread in #help.
Last night we were speaking with Vince on Discord in #general.