You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to get the version in code, by calling : System.out.println("OpenGL version : " + gl.glGetString(GL2.GL_VERSION));
And I got : OpenGL version : 1.1.0
This kind of surprises me, since it seems that the maximum valid version of OpenGL is 3.1 in my computer... And also this computer isn't that old
OS : Windows 10, 32 bits
GPU : Intel(R) HD Graphics 3000 with drivers up to date (I verified them so they should be)
Java : jre1.8.0_261
As stated on the original bugzilla ticket, the bug is due to intel drivers.
Instead of providing no OpenGL driver for Windows 10, Intel provides a driver that fails to load for its discontinued hardware. When a signed software claims to support Windows 10 which is the case of Oracle Java and OpenJDK 1.8.0 update 60 and later, the driver loads to load and Microsoft GDI Generic driver is used instead.
I fear that Java Webstart will follow the same route than applets (deprecated in Java 1.9, removed from Java 1.10). I remind that Java Webstart is mostly unusable without paying for a "trusted" certificate or tinkering the JRE. I don't advise to use an old version of Java as it exposes to vulnerabilities. Therefore, there is no acceptable workaround (Java Webstart or downgrading to OpenJDK 1.8.0 update 55).
If we lied to the the driver somehow, it would "work" but as it's not maintained, the bugs would remain unfixed. Intel is to blame here, there is nothing that we can do.
https://forum.jogamp.org/JOGL-project-does-not-work-in-a-different-computer-td4041404.html
https://jogamp.org/bugzilla/show_bug.cgi?id=1278
I tried to get the version in code, by calling :
System.out.println("OpenGL version : " + gl.glGetString(GL2.GL_VERSION));
And I got :
OpenGL version : 1.1.0
This kind of surprises me, since it seems that the maximum valid version of OpenGL is 3.1 in my computer... And also this computer isn't that old
As stated on the original bugzilla ticket, the bug is due to intel drivers.
The text was updated successfully, but these errors were encountered: