antialiasing not working with bumblebee and nvidia propietary
luca.boccassi at gmail.com
Sun Jan 24 13:20:31 UTC 2016
On Sat, 2016-01-23 at 13:44 +0100, Jakub Pišek wrote:
> i tried nvidia-settings, but settings are not applied.
> also enviroment variables __GL_FSAA_MODE and VGL_SAMPLES with no effect
> here is fsaa query from nvidia-settings:
> optirun nvidia-settings -c :8 --query=fsaa --verbose
> Attribute 'FSAA' (debext:8.0): 0.
> Valid values for 'FSAA' are: 0, 1, 5, 9, 10 and 11.
> 'FSAA' can use the following target types: X Screen.
> Note to assign 'FSAA' on the commandline, you may also need to assign
> 'FSAAAppControlled' and 'FSAAAppEnhanced' to 0.
> Valid 'FSAA' Values
> value - description
> 0 - Off
> 1 - 2x (2xMS)
> 5 - 4x (4xMS)
> 9 - 8x (4xSS, 2xMS)
> 10 - 8x (8xMS)
> 11 - 16x (4xSS, 4xMS)
> next week i have big show, i dont know what to do, what to try.
> do you have some ideas?
Changing values through nvidia-settings won't work through bumblebee,
you can find an explanation by upstream devs at .
Upstream developers suggest that VGL_SAMPLES should work when using
virtualgl as the bridge, so double check that it's not using primus.
If that still doesn't work, I'd suggest forwarding this issue upstream
 as the developers might have more suggestions.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: This is a digitally signed message part
More information about the pkg-nvidia-devel