Login  Register

Re: Incorrect context on GLCanvas drawable

Posted by MarcoNL on Sep 12, 2022; 10:18am
URL: https://forum.jogamp.org/Incorrect-context-on-GLCanvas-drawable-tp4041391p4041849.html

Hi Julien,

thank you for your message.

I've just run my test case "vtk.sample.rendering.JoglContextTestCase" (which was included in this Thread) on my development machine (NVIDIA GeForce GTX 1060 6 GB, dual screen), and setting "-Djogl.disable.opengles=true" doesn't make any difference: an OpenGL 1.1 profile is used by GLCanvas. Here is the output of my test case with this property set:

Screen device # 0: \Display0
Screen device # 0, configuration # 0:
Screen device # 0, configuration # 1:
Screen device # 0, configuration # 2:
Screen device # 0, configuration # 3:
Screen device # 0, configuration # 4:
Screen device # 0, configuration # 5:
Screen device # 1: \Display1
Screen device # 1, configuration # 0:
Screen device # 1, configuration # 1:
Screen device # 1, configuration # 2:
Screen device # 1, configuration # 3:
Screen device # 1, configuration # 4:
Screen device # 1, configuration # 5:
NewFrame created in thread [16], isEDT: true
* Context GL version: 1.1 (Compat profile, arb, compat[], FBO, hardware) - 1.1.0

Again, the only way to make it work on my PC, and on many other NVIDIA-powered PCs that I've tested, is to set the "-Dsun.awt.nopixfmt=true" system property. At that point, the output of my "vtk.sample.rendering.JoglContextTestCase" test case is:

Screen device # 0: \Display0
Screen device # 0, configuration # 0:
Screen device # 1: \Display1
Screen device # 1, configuration # 0:
NewFrame created in thread [16], isEDT: true
* Context GL version: 4.6 (Compat profile, arb, compat[ES2, ES3, ES31, ES32], FBO, hardware) - 4.6.0 NVIDIA 512.15

However, this setting seems to cause other NVIDIA adapters (namely, Quadro K600) to crash.

Best regards,

Marco Sambin