Environment Variables
+Environment Variables
Normally, no environment variables need to be set. Most of the environment @@ -15,7 +23,7 @@ sometimes be useful for debugging end-user issues.
-LibGL environment variables
+LibGL environment variables
- LIBGL_DEBUG - If defined debug information will be printed to stderr. @@ -24,11 +32,13 @@ sometimes be useful for debugging end-user issues.
- LIBGL_ALWAYS_INDIRECT - forces an indirect rendering context/connection.
- LIBGL_ALWAYS_SOFTWARE - if set, always use software rendering
- LIBGL_NO_DRAWARRAYS - if set do not use DrawArrays GLX protocol (for debugging) +
- LIBGL_SHOW_FPS - print framerate to stdout based on the number of glXSwapBuffers + calls per second.
Core Mesa environment variables
+Core Mesa environment variables
- MESA_NO_ASM - if set, disables all assembly language optimizations @@ -37,10 +47,12 @@ sometimes be useful for debugging end-user issues.
- MESA_NO_SSE - if set, disables Intel SSE optimizations
- MESA_DEBUG - if set, error messages are printed to stderr. For example,
if the application generates a GL_INVALID_ENUM error, a corresponding error
- message indicating where the error occured, and possibly why, will be
+ message indicating where the error occurred, and possibly why, will be
printed to stderr.
If the value of MESA_DEBUG is 'FP' floating point arithmetic errors will generate exceptions. + - MESA_LOG_FILE - specifies a file name for logging all errors, warnings, +etc., rather than stderr
- MESA_TEX_PROG - if set, implement conventional texture env modes with fragment programs (intended for developers only)
- MESA_TNL_PROG - if set, implement conventional vertex transformation @@ -59,9 +71,25 @@ If the extension string is too long, the buffer overrun can cause the game to crash. This is a work-around for that.
- MESA_GL_VERSION_OVERRIDE - changes the value returned by
-glGetString(GL_VERSION). Valid values are point-separated version numbers,
-such as "3.0". Mesa will not really implement all the features of the given
-version if it's higher than what's normally reported.
+glGetString(GL_VERSION) and possibly the GL API type.
+
-
+
- The format should be MAJOR.MINOR[FC] +
- FC is an optional suffix that indicates a forward compatible context. +This is only valid for versions >= 3.0. +
- GL versions < 3.0 are set to a compatibility (non-Core) profile +
- GL versions = 3.0, see below +
- GL versions > 3.0 are set to a Core profile +
- Examples: 2.1, 3.0, 3.0FC, 3.1, 3.1FC
+
-
+
- 2.1 - select a compatibility (non-Core) profile with GL version 2.1 +
- 3.0 - select a compatibility (non-Core) profile with GL version 3.0 +
- 3.0FC - select a Core+Forward Compatible profile with GL version 3.0 +
- 3.1 - select a Core profile with GL version 3.1 +
- 3.1FC - select a Core+Forward Compatible profile with GL version 3.1 +
- Mesa may not really implement all the features of the given version. +(for developers only) +
- MESA_GLSL_VERSION_OVERRIDE - changes the value returned by glGetString(GL_SHADING_LANGUAGE_VERSION). Valid values are integers, such as "130". Mesa will not really implement all the features of the given language version @@ -70,11 +98,11 @@ if it's higher than what's normally reported. (for developers only)
Mesa Xlib driver environment variables
+Mesa Xlib driver environment variables
The following are only applicable to the Mesa Xlib software driver. -See the Xlib software driver page for details. +See the Xlib software driver page for details.
- MESA_RGB_VISUAL - specifies the X visual and depth for RGB mode
@@ -93,17 +121,45 @@ See the Xlib software driver page for details.
i945/i965 driver environment variables (non-Gallium)
-
-
- INTEL_STRICT_CONFORMANCE - if set to 1, enable sw fallbacks to improve - OpenGL conformance. If set to 2, always use software rendering. -
- INTEL_NO_BLIT - if set, disable hardware-accelerated glBitmap, - glCopyPixels, glDrawPixels. +
- INTEL_NO_HW - if set to 1, prevents batches from being submitted to the hardware. + This is useful for debugging hangs, etc. +
- INTEL_DEBUG - a comma-separated list of named flags, which do various things:
+
-
+
- tex - emit messages about textures. +
- state - emit messages about state flag tracking +
- blit - emit messages about blit operations +
- miptree - emit messages about miptrees +
- perf - emit messages about performance issues +
- perfmon - emit messages about AMD_performance_monitor +
- bat - emit batch information +
- pix - emit messages about pixel operations +
- buf - emit messages about buffer objects +
- reg - emit messages about regions +
- fbo - emit messages about framebuffers +
- fs - dump shader assembly for fragment shaders +
- gs - dump shader assembly for geometry shaders +
- sync - emit messages about synchronization +
- prim - emit messages about drawing primitives +
- vert - emit messages about vertex assembly +
- dri - emit messages about the DRI interface +
- sf - emit messages about the strips & fans unit (for old gens, includes the SF program) +
- stats - enable statistics counters. you probably actually want perfmon or intel_gpu_top instead. +
- urb - emit messages about URB setup +
- vs - dump shader assembly for vertex shaders +
- clip - emit messages about the clip unit (for old gens, includes the CLIP program) +
- aub - dump batches into an AUB trace for use with simulation tools +
- shader_time - record how much GPU time is spent in each shader +
- no16 - suppress generation of 16-wide fragment shaders. useful for debugging broken shaders +
- blorp - emit messages about the blorp operations (blits & clears) +
- nodualobj - suppress generation of dual-object geometry shader code +
Radeon R300 driver environment variables (non-Gallium)
+Radeon driver environment variables (radeon, r200, and r300g)
-
-
- R300_NO_TCL - if set, disable hardware-accelerated Transform/Clip/Lighting. +
- RADEON_NO_TCL - if set, disable hardware-accelerated Transform/Clip/Lighting.
Gallium environment variables
-
+
- GALLIUM_HUD - draws various information on the screen, like framerate, + cpu load, driver statistics, performance counters, etc. + Set GALLIUM_HUD=help and run e.g. glxgears for more info. +
- GALLIUM_LOG_FILE - specifies a file for logging all errors, warnings, etc. + rather than stderr.
- GALLIUM_PRINT_OPTIONS - if non-zero, print all the Gallium environment variables which are used, and their current values. -
- GALLIUM_NOSSE - if non-zero, do not use SSE runtime code generation for - shader execution -
- GALLIUM_NOPPC - if non-zero, do not use PPC runtime code generation for - shader execution
- GALLIUM_DUMP_CPU - if non-zero, print information about the CPU on start-up
- TGSI_PRINT_SANITY - if set, do extra sanity checking on TGSI shaders and print any errors to stderr. @@ -131,6 +188,9 @@ Mesa EGL supports different sets of environment variables. See the
- DRAW_NO_FSE - ???
- DRAW_USE_LLVM - if set to zero, the draw module will not use LLVM to execute shaders, vertex fetch, etc. +
- ST_DEBUG - controls debug output from the Mesa/Gallium state tracker. +Setting to "tgsi", for example, will print all the TGSI shaders. +See src/mesa/state_tracker/st_debug.c for other options.
Softpipe driver environment variables
@@ -141,14 +201,14 @@ Mesa EGL supports different sets of environment variables. See the to stderr - SOFTPIPE_NO_RAST - if set, rasterization is no-op'd. For profiling purposes.
- SOFTPIPE_USE_LLVM - if set, the softpipe driver will try to use LLVM JIT for - vertex shading procesing. + vertex shading processing.
LLVMpipe driver environment variables
- LP_NO_RAST - if set LLVMpipe will no-op rasterization -
- LP_DEBUG - a comma-separated list of debug options is acceptec. See the +
- LP_DEBUG - a comma-separated list of debug options is accepted. See the source code for details.
- LP_PERF - a comma-separated list of options to selectively no-op various parts of the driver. See the source code for details. @@ -157,16 +217,22 @@ Mesa EGL supports different sets of environment variables. See the cores present.
VMware SVGA driver environment variables
+-
+
- SVGA_FORCE_SWTNL - force use of software vertex transformation +
- SVGA_NO_SWTNL - don't allow software vertex transformation fallbacks +(will often result in incorrect rendering). +
- SVGA_DEBUG - for dumping shaders, constant buffers, etc. See the code +for details. +
- See the driver code for other, lesser-used variables. +
Other Gallium drivers have their own environment variables. These may change frequently so the source code should be consulted for details.
- --
- - - - +