Posted by Alexei A. Morozov on Dec 03, 2012; 4:19pm
URL: https://forum.jogamp.org/Why-antialiasing-does-not-operate-tp4027215p4027385.html

Thank you a lot, InteractiveMesh!

Well, it seems your idea does work. Here are results of my investigation:

Java3D 1.6.0-pre5:

GraphicsConfigTemplate3D gct3D= new GraphicsConfigTemplate3D();
gct3D.setSceneAntialiasing(GraphicsConfigTemplate3D.REQUIRED);
GraphicsConfiguration gc= java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment().getDefaultScreenDevice().getBestConfiguration(gct3D);



GraphicsConfiguration gc= SimpleUniverse.getPreferredConfiguration(); // old version



Java3D 1.5.2:

GraphicsConfigTemplate3D gct3D= new GraphicsConfigTemplate3D();
gct3D.setSceneAntialiasing(GraphicsConfigTemplate3D.REQUIRED);
GraphicsConfiguration gc= java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment().getDefaultScreenDevice().getBestConfiguration(gct3D);



GraphicsConfiguration gc= SimpleUniverse.getPreferredConfiguration(); // old version



There are interesting details:

The cv.queryProperties().get("sceneAntialiasingNumPasses") function returns 1 when GraphicsConfigTemplate3D is used both in Java3D 1.6.0.pre5 and Java3D 1.5.2 cases. However, this function returns 0 and 8 correspondingly when SimpleUniverse.getPreferredConfiguration() is used. The results of antialiasing are different a bit. One can see on the figures that 1.5.2 + SimpleUniverse.getPreferredConfiguration() gives the best result still. The GraphicsConfigTemplate3D method gives different results for Java3D 1.6.0.pre5 and Java3D 1.5.2 too. The best result gives Java3D 1.5.2 still IMHO.

Here is improved test program: t82.java. All tests were performed under Windows XP, JDK 1.7.0_09-b05.

I would very much appreciate your further comments on how to improve the results of antialiasing under Java3D 1.6.0.

Thank you once again,

A.M.