Posted by gouessej on Sep 19, 2014; 2:05pm
URL: https://forum.jogamp.org/Problem-since-Jogl-2-2-1-tp4033169p4033170.html

Hi

It has nothing to do with JOGL. Your customer should update its driver, it just worked today for one of mine. Please use the graphical card's manufacturer's driver, neither the driver provided by the OEM nor the driver provided by Microsoft.

"javax.media.opengl.GLException: pbuffer creation error: Couldn't find a suitable pixel format" often appears when the customer uses the default Microsoft Corporation's driver "GDI renderer". It supports 32 bits for the precision of the depth buffer. If Java3D passes a GLCapabilities object with depthBits = 24, JOGL uses a requested GLCapabilities with 32 bits for the precision of the depth buffer but the creation of the pbuffer fails. As the crappy Microsoft Corporation's driver only supports OpenGL 1.1.0, it has no chance to work with Java3D (which requires at least OpenGL 1.3).

N.B: JogAmp's Ardor3D Continuation 1.1 will work flawlessly in this case because:
- it uses on-screen rendering most of the time unlike Java3D
- it will support OpenGL 1.1 too in 2015 (it needs another code path when the vertex arrays can't be used)

Edit.: Please provide much more information, display GL_VERSION, GL_RENDERER, ... How can we efficiently help you without knowing which driver is in use?