Posted by gouessej on Jul 10, 2018; 2:54pm
URL: https://forum.jogamp.org/Ardor3D-JOGL-problems-tp4038988p4038998.html

Sorry, Joshua fixed some bugs mostly in ardor3d-ui but not this bug.

I'm currently talking only about this bug. The symptom exhibited in the stack trace clearly shows that the OpenGL driver is unable to recognize an enumerant and the root cause affects other engines too:
http://forum.jogamp.org/How-to-run-Java-3D-1-6-under-old-Intel-processors-with-integrated-graphics-td4038694.html

charxie wrote

I suspect that not all bugs can be attributed to driver incompatibility.

Which bugs are you talking about? Please try to run the program using JogAmp's Ardor3D Continuation with an older OpenGL driver or an older version of Java. I don't try to find a false excuse not to look for a fix, there's just nothing to fix in JOGL and JogAmp's Ardor3D Continuation as they aren't to blame. You wrote "The software worked fine just a couple of weeks ago on the same computers", that's why I suggest you to use an older OpenGL driver or an older version of Java, in order to put yourself into the same conditions than a couple of weeks ago when it was working. I know that some end users don't like to change such things but there is nothing to fix in our APIs, the bug is elsewhere.

N.B: Reminder: Ardor3D != JogAmp's Ardor3D Continuation
I'm not responsible for Ardor3D, I'm responsible for JogAmp's Ardor3D Continuation.