Posted by gouessej on Jun 04, 2016; 9:06pm
URL: https://forum.jogamp.org/J3D-JOGL-good-within-Eclipse-but-UnsatisfiedLinkError-as-standalone-tp4036783p4036794.html

It's explained in the Java3D user's guide I wrote, you MUST use Java3D 1.6.0-pre12 with JOGL 2.3.2. There is no DLL in Java3D itself since I removed the crappy unmaintained native renderers not based on JOGL.

P.S: Actually, if you really want to build Java3D, you should use my repository but ... it's Java3D 1.7.0, the imports aren't the same...

P.S: Please don't use the extension mechanism, it's only a source of trouble. Ensure that there is no library elsewhere that could cause a conflict, look at your path and your classpath. There is no complicated surgery to do, you can merge all JARs into one but having to handle the native libraries separately because of a corporate policy that blocks the automated native library loading drives things less simple.

Relying on the extension mechanism is a really poor decision, I wrote that it's going to be completely removed from Java. It has been an endless source of version conflicts, it can break applets and applications that require different versions...