Posted by gouessej on Jul 27, 2016; 9:34am
URL: https://forum.jogamp.org/Frame-briefly-opening-and-closing-during-Java3D-init-tp4036912p4036991.html

runiter wrote

1) What's an example of a scenario where AWT gets broken and causes Java3D to fail? AWT is supposed to be a mature library, I have a hard time imagining how it's broken.

AWT seems to be less actively maintained as Oracle focuses on OpenJFX and JavaFX. This is an example of broken AWT feature in Java 1.9:
https://bugs.openjdk.java.net/browse/JDK-8160421
Unfortunately, it affects JOGL too. I see sometimes some troubles with multiple monitors too under some operating systems. Moreover, the AWT fullscreen mode under GNU Linux is broken (it was already broken in 2006) and has never been fixed. Then, it's impossible to write a fullscreen software with Java3D working on all platforms supported by Java.

runiter wrote

2) Few of my customers report the following Java3D error:

javax.media.j3d.IllegalRenderingStateException: Java 3D ERROR : OpenGL 1.2 or better is required (GL_VERSION=1.1)

The version of Java3D is 1.6.0-pre9 which is before the new Frame() code was added.
Do you think this error is related to the broken AWT issue that is now fixed by using new Frame() code?

No it is related to another unfixed bug in JOGL, some ImageJ users reproduce it too. However, it may happen when no true OpenGL driver is available, then the Microsoft GDI renderer (supporting only OpenGL 1.1) is the only available driver :(