Thanks for the update. I tried it with Sweet Home 3D successfully but like Andreas, I noticed some differences in antialiasing management. Antialiasing works but the filter (min/max values?) isn't as efficient as in previous versions, making rendered images less nice at screen.
I just tried it also with Sweet Home 3D applet, and I have to report an issue that reappeared and prevents from using its JCanvas instance.
Here's the stack trace:
Exception in thread "AWT-EventQueue-2" java.lang.NullPointerException: Canvas3D: null GraphicsConfiguration
at com.eteks.sweethome3d.swing.HomeComponent3D$3.layoutContainer(Unknown Source)
Those both bugs are probably caused by kavon's contribution, especially the code that picks the graphics configuration and manipulates the graphics configuration table within Canvas3D. I don't blame him as the original code was a real mess with this nasty QueryCanvas that I've ever wanted to remove from Java3D.
Any news about the java.lang.NullPointerException thrown in javax.media.j3d.Canvas3D.checkForValidGraphicsConfig?
Should I try with more recent versions of JOGL or this shouldn't change anything until a pre12 is out?
After a new try with JOGL 2.2.4 / Java 8u25 under Mac OS X, I noticed that antialiasing works but keep reporting that the filter (min/max values?) isn't as efficient as in previous versions, making rendered images less nice at screen. Could this issue be fixed? Or was this change made on purpose?
I also tried to use Canvas3D instances with applets (not JCanvas3D instances which are incredibly slow on a Retina display) and on this side, I've got good news: it works great under Mac OS X 10.10, even if a few stack traces like the following one appear in the Java console:
RunnableTask.run(): A caught exception occured on thread Repaint-OnAppContextTG:
RunnableTask[executed false, tTotal 0 ms, tExec 0 ms, tQueue 0 ms, attachment null, throwable java.lang.NullPointerException]
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.