Announcement

Collapse
No announcement yet.

Forcing Multi-Sample Anti-Aliasing With Gallium3D

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • phoronix
    started a topic Forcing Multi-Sample Anti-Aliasing With Gallium3D

    Forcing Multi-Sample Anti-Aliasing With Gallium3D

    Phoronix: Forcing Multi-Sample Anti-Aliasing With Gallium3D

    With the recent improvements to MSAA Gallium3D support, if you have been wanting to benefit from anti-aliasing with the open-source Gallium3D drivers but your game/application doesn't have options to toggle the MSAA level, it's now a bit easier to configure...

    http://www.phoronix.com/vr.php?view=MTI1Mzc

  • ResponseWriter
    replied
    Note for anyone finding this now: these environment variables were removed in Mesa 10.3.1. https://www.mesa3d.org/relnotes/10.3.1.html

    Leave a comment:


  • curaga
    replied
    That's a bit wide question. Each option there has an explanation, and some are even in multiple languages.

    Leave a comment:


  • Hamish Wilson
    replied
    I have always been a bit confused by driconf. What exactly do the options it already has actually do?

    Leave a comment:


  • Veerappan
    replied
    Originally posted by droste View Post
    AFAIR the consensus of the mailing list was that there should be a driconf option. The problem is that someone has to do it
    Yup, that seemed to be the consensus. As you said, now someone just has to do it... which should be pretty easy.

    Leave a comment:


  • droste
    replied
    Originally posted by curaga View Post
    Why not driconf?
    AFAIR the consensus of the mailing list was that there should be a driconf option. The problem is that someone has to do it

    Leave a comment:


  • tomato
    replied
    Originally posted by curaga View Post
    Why not driconf?

    It's the standard way for these on linux, and would also support the env var. But in addition it would allow static configuration, and optionally via a GUI - you can say "I always want MSAA 8x for ET, but 0x for ETQW", without making wrapper scripts for those or exporting a global value in your environment, which would affect the compositor and possibly hurt.
    +1 for driconf

    Leave a comment:


  • curaga
    replied
    Why not driconf?

    It's the standard way for these on linux, and would also support the env var. But in addition it would allow static configuration, and optionally via a GUI - you can say "I always want MSAA 8x for ET, but 0x for ETQW", without making wrapper scripts for those or exporting a global value in your environment, which would affect the compositor and possibly hurt.

    Leave a comment:

Working...
X