Posted by Manu on Jan 22, 2015; 7:34pm
URL: https://forum.jogamp.org/Java3D-1-6-0-pre11-released-tp4032735p4033899.html

After a search in the source code of Java 3D, I think I found why antialiasing in 1.6.0-pre11 isn't the same as in 1.6.0-pre10.
In the change of JoglPipeline committed on Aug 5, 2014, a setNumSamples(4) call was removed in getBestConfiguration, and now there's only a setNumSamples(2) call, leading to some antialiasing of lower quality from the comments in JoglPipeline class.
How comes that the value passed to setNumSamples was reduced? Is it to ensure a better support of Java 3D?
Thanks for your help.