Changes between Version 7 and Version 8 of Debugging/OpenGL

Timestamp:

08/12/15 06:31:58 (6 years ago)

Author:

Antoine Martin

Comment:

--

Debugging/OpenGL

@@ -7 +7 @@
 [[BR]]
 
+The first step is to run the client with {{{-d opengl}}}, this should log a lot more information about opengl calls and is often enough to spot the source of the problem
 
-Whenever you encounter problems with client-side `OpenGL` rendering, for example with `OpenGL` error messages, crashes, or visual artifacts, there are some specific steps to take to investigate. The *`Apitrace`* tool will get a dump of the `OpenGL` command stream, allowing it to be sent to the developers for replaying and investigation.
+Then there is also the environment variable {{{XPRA_OPENGL_DEBUG=1}}} which will enable the {{{GREMEDY}}} extension if present.
+
+If these options are not sufficient to identify the source of the problem, you can use other tools to dig into the opengl rendering:
+* Apitrace (see below)
+* [https://github.com/ValveSoftware/vogl vogl]
+* [https://developer.nvidia.com/linux-graphics-debugger NVidia's Linux Graphics Debugger]
 }}}
 
 {{{#!div class="box"
-== Installation ==
+== Apitrace Installation ==
+
+The *`Apitrace`* tool will get a dump of the `OpenGL` command stream, allowing it to be sent to the developers for replaying and investigation.
 
 * On Linux:
@@ -25 +33 @@
 
 {{{#!div class="box"
-== Trace generation ==
+== Apitrace Usage ==
 
 This trace will enable you to replay the actions of the client without having to re-run it; giving you additional error tracing, ability to send the trace to another person, and ability to replay the exact same steps every time.