Posted by gouessej on Feb 10, 2016; 10:27am
URL: https://forum.jogamp.org/Java3d-pushing-the-limits-tp4035814p4036143.html

I don't want to be harsh.

We can work together in order to find a way of integrating your changes without breaking the existing API or we can do those breaking changes in Java3D 1.7.0 (not in Java3D 1.6.0). By default, Java3D will use the fixed pipeline except in cases where it has no chance to work but a pipeline option is a good idea to me.

Why do you mean by "the non rt.jar side"?

The problem is that the new pipeline will require some maintenance on the long term. Your changes will be helpful but it won't eliminate all design flaws of Java3D.