Reply – Re: Understanding issue with automatic buffer swapping
Your Name
Subject
Message
or Cancel
In Reply To
Re: Understanding issue with automatic buffer swapping
— by Xerxes Rånby Xerxes Rånby
I am encountering some flicker and one buffer that is not cleared / updating properly
when running the sage2 test on Windows 8 in combination with the Azul JVM and AWT implementation.

Platform: Java Version: 1.8.0_121 (1.8.0u121), VM: OpenJDK 64-Bit Server VM, Run
time: OpenJDK Runtime Environment
Platform: Java Vendor: Azul Systems, Inc., http://www.azulsystems.com/, JavaSE:
true, Java6: true, AWT enabled: true

Swap Interval  1
GL Profile     GLProfile[GL4bc/GL4bc.hw]
GL Version     4.5 (Compat profile, arb, compat[ES2, ES3, ES31], FBO, hardware)
- 4.5.13399 Compatibility Profile Context 15.200.1062.1004 [GL 4.5.0, vendor 15.
200.1062 (Compatibility Profile Context 15.200.1062.1004)]
Quirks         [NoDoubleBufferedBitmap, NoSurfacelessCtx]
Impl. class    jogamp.opengl.gl4.GL4bcImpl
GL_VENDOR      ATI Technologies Inc.
GL_RENDERER    AMD Radeon(TM) R5 Graphics
GL_VERSION     4.5.13399 Compatibility Profile Context 15.200.1062.1004
GLSL           true, has-compiler-func: true, version: 4.40 / 4.40.0
GL FBO: basic true, full true
GL_EXTENSIONS  285
GLX_EXTENSIONS 24

As can be seen in this image: the top left quadrant have rendered two extra blue moons most likely originating from one nu-cleared buffer.



It is possible that the issues seen on this system is caused by different buffering in the Azul AWT implementation compared to the Linux implementation.

You can remove all AWT differences and AWT issues by switching from AWT to using the JogAmp JOGL GLWindow. GLWindow is highly recommended since it is supported on platforms that do not have AWT.
com.jogamp.newt.opengl.GLWindow