Posted by babor on Mar 27, 2018; 12:55pm
URL: https://forum.jogamp.org/How-to-run-Java-3D-1-6-under-old-Intel-processors-with-integrated-graphics-tp4038694p4038763.html

gouessej wrote

JogAmp APIs aren't to blame, we're not responsible for Intel's debatable choices and sometimes you have to tell your end users that they should use some hardware with more professional driver support.

True. I'm not blaming you guys, rather than letting know that many such issues exist.
Indeed our described case on Windows 10 was (surprisingly) solved by windows update, while MacOS will probably wait longer... On the other hand the variety of combinations of features, OSes, Java versions, Java3D versions and hardware makes it almost impossible to run properly everywhere.    

gouessej wrote

Moreover, switching from Java3D 1.6 to Java3D 1.7 only requires to update the package names in your code, it's not an unachievable change.

Finally, I cannot fix bugs that aren't in our APIs and bugs that nobody reports. "we cannot ultimately migrate to 1.6 or 1.7 due to a number of problems" doesn't help at all and I still highly discourage the use of Java3D 1.5. Several contributors have worked in fixing bugs, sticking to Java3D 1.5 only to go on supporting a very few Intel GPUs or deprecated Java versions is a nonsense.

I was intentionally not describing all the details in this thread. I'll post each problem separately as soon as we manage to extract them.