[v0.2.0] Enable/disable/force hardware acceleration

Created by Michael Müller on on 2013-08-26
Keywords:
Last updated by:
Sebastian Lackner on on 2014-01-20

The following text applies only to Pipelight version 0.1-2 or higher.

By default GPU acceleration is only enabled on pages that require it AND if your graphic driver is already contained in a list of known-to-work systems. This doesn't necessarily mean that it doesn't work when your graphic driver is not included there, but you will have to try it out! If you have GPU acceleration enabled and experience any problems with that (distorted image, crashes) and therefore want to disable it or you want to force the usage of the GPU for the video output, you can change that too.

In order to enable/disable/force GPU acceleration you always have to create a custom config. Simply create a copy of the original config in ~/.config/ by executing:

cp /usr/share/pipelight/configs/pipelight-silverlight5.1 ~/.config/
[NOTE: For versions < 0.2.4 the file was located at /usr/share/pipelight/pipelight-silverlight5.1 instead]

Open ~/.config/pipelight-silverlight5.1 in any text editor, for example with:
gedit ~/.config/pipelight-silverlight5.1

In order to force GPU acceleration uncomment this line:
overwriteArg = enableGPUAcceleration=true

In order to disable GPU acceleration (even if your graphic driver is probably supported) uncomment this line:
overwriteArg = enableGPUAcceleration=false

If you just want to skip the graphic drivers check, and enable GPU acceleration on every page that wants to use it, change the following settings (and leave all options above commented out):
graphicDriverCheck = /bin/true

-------------
Please note: When you are using some specific graphic card drivers it might be possible that GPU acceleration doesn't work correctly, but unfortunately there is nothing we can do about this, except hoping, that the graphic drivers and wined3d9 will improve even further. Nevertheless we are always glad about some additional test results (output of "glxinfo") which are known-to-work/not-to-work properly. Just send them to us, for example via bug-report.