What happens?
You run into OpenGL-related problems that are difficult to diagnose:
-
Your Lightspeed view exhibits graphical glitches, such as flickering or a partial corruption of the display
-
A running LuciadLightspeed sample or application suddenly crashes, or throws an inexplicable error related to an OpenGL call. When the application crashes, it generates a log file that contains a stack trace with OpenGL-related calls, for example:
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j org.lwjgl.opengl.GL11C.nglDrawElements(IIIJ)V+0
j org.lwjgl.opengl.GL11C.glDrawElements(IIIJ)V+4
j org.lwjgl.opengl.GL11.glDrawElements(IIIJ)V+4
j com.luciad.internal.view.opengl.binding.lwjgl.f.glDrawElements(IIIJ)V+5
Why does this happen?
Most of the time, those kinds of exceptions or glitches are due to the graphics driver: the driver is outdated, it contains a bug for some OpenGL features, or it does not handle a specific sequence of OpenGL calls correctly. Another potential cause is the installation of a driver other than the one provided by the manufacturer of the GPU.
How can I fix it?
First of all, make sure that you have installed the latest version of your GPU driver. You can find the most recent driver versions at the following download locations:
It is particularly advisable to download the latest GPU drivers from these sites if you are using a laptop. The drivers provided by laptop manufacturers (Dell, HP, and so on) typically lag far behind the latest versions made available by the GPU manufacturer. |
Reporting problems to the support desk
If updating the driver does not solve the issue, you can contact the Luciad Support Desk. If you do so, it is important that you provide us with the following information:
-
The LuciadLightspeed version, for example version 2015.1.02
-
The output of the
lightspeed.debug.report
sample, a LuciadLightspeed tool that generates a report on the hardware-related capabilities of your system. If it is not possible to send such a report, try sending us the information provided by one of the following reporting tools:-
glxinfo (Linux)
-
http://realtech-vr.com/home/glview (Windows)
-
http://www.ozone3d.net/gpu_caps_viewer/ (Windows)
-
-
The log file that was generated or any error messages in the console
-
A screenshot or screen recording in case of a graphical glitch
That information will help us diagnose the problem faster.