What does LIBGL_ALWAYS_INDIRECT= 1 in fact do?

KDE SC 4.5.0 has some troubles with some video clip cards consisting of mine. Upon Release Arch recommended several workarounds. Among which was

export "LIBGL_ALWAYS_INDIRECT= 1" prior to beginning KDE

I determined that it was the most convenient, ideal method. Yet I do not recognize what it does or just how it influences my system. Is it slower than the default? should I bear in mind to watch on the trouble and also disable it later on as soon as it's dealt with?

2019-05-04 05:16:41
Source Share
Answers: 1

Indirect providing methods that the GLX method will certainly be made use of to send OpenGL commands and also the X.org will certainly do the actual illustration.

Direct rendering suggests that application can access hardware straight without interaction with X.org first using mesa.

The straight making is much faster as it does not call for adjustment of context right into X.org process.

Explanation : In both instances the making is done by GPU (or practically - might be done by GPU ). Nonetheless in indirect providing the process resembles :

  1. Program calls a command (s )
  2. Command (s ) is/are sent out to X.org by GLX method
  3. X.org calls hardware (i.e. GPU ) to attract

In straight making

  1. Program calls a command (s )
  2. Command (s ) is/are sent out to GPU

Please keep in mind that due to the fact that OpenGL was made in such manner in which might run over network the indirect making is much faster after that would certainly be ignorant execution of style i.e. permits to send a buch of commands in one go. Nonetheless there is some expenses in regards to CPU time invested for context buttons and also taking care of method.

2019-05-08 00:49:28