Posted by gouessej on Aug 31, 2023; 7:50am
URL: https://forum.jogamp.org/Dealing-with-3D-crash-in-RHEL-8-4-with-mesa-driver-tp4042917p4042925.html

Don't advise people to use an obsolete unmaintained version of Java3D. I totally understand that some developers can have a different point of view but such "workarounds" have side effects that the JogAmp community doesn't have to handle. The errors whose message is "Profile GL2 is not available on null" are often but not always fixed by using a more recent driver or a more recent version of JOGL. Java3D 1.5.2 has many unfixed bugs, it's a matter of facts, what seems to work in a particular case will exhibit the bugs fixed in the meantime, I remember that Harvey (mostly) and some other contributors fixed numerous bugs even before I ported Java3D to JOGL 2.

Moreover, I remind you that Java3D 1.7 uses a different package namespace as we're not allowed to use the javax namespace (it's the same for Jakarta EE):
https://jogamp.org/deployment/java3d/1.7.0-pre1/javadoc/ (rather use the documentation in maven-java3d if you need something more recent). We use "org.jogamp" instead of "javax.media".

What you are doing is nonsensical, never mix several versions of Java3D, libj3dcore-ogl.so isn't used by JogAmp Java3D. Have you ever read my tutorial? I'll update it as soon as possible to be sure that it works as expected.

Keep in mind that there is a known problem with some Intel drivers under Windows with Java >= 9, it even affects Minecraft that doesn't use JOGL.

Finally I remind that the current release of Mesa is the version 23.1.6, the Mesa Amber release is the version 21.3.9. Please don't use an obsolete version of Mesa, we cannot handle bugs that affect terribly old version of Mesa (Mesa 20 had many minor releases between March 2020 and March 2021, i.e more than two years ago).

Sorry to be harsh. Thank you for the feedback anyway.

P.S: Please use official sources of information about JogAmp Java3D. The dirty kludges used outside will lead you nowhere.