Posted by Gene on Jan 26, 2012; 12:18am
URL: https://forum.jogamp.org/Cross-platform-DLL-selection-tp3667506p3689424.html

Just a note here to close out this discussion.  This turned out not to be that the DLLs weren't loading but that the call to GLCapabilities was generating a memory access error inside the graphics driver.  The user wasn't furnishing enough of the stack trace to see the final lines indicating this as the problem.

As my app now has both OpenGL and vanilla Swing rendering paths, I was able to work around this by providing a limited graphics mode where the JOGL API is never touched at all.

Given the bug report frequency we are seeing, JOGL 2 seems more likely to manifest driver bugs during initialization than JOGL 1.  I suppose this is because it's making a more thorough probe of supported features.

Thanks again for all the help.