[Mesa-dev] [Bug 107391] feature request: enforceable vsync and anisotropic filtering via environment variables

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Jul 26 22:21:03 UTC 2018


            Bug ID: 107391
           Summary: feature request: enforceable vsync and anisotropic
                    filtering via environment variables
           Product: Mesa
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: enhancement
          Priority: medium
         Component: Drivers/Vulkan/radeon
          Assignee: mesa-dev at lists.freedesktop.org
          Reporter: tempel.julian at gmail.com
        QA Contact: mesa-dev at lists.freedesktop.org

With RadeonSI, it's possible to force vsync on/off with vblank_mode and level
of anisotropic filtering with R600_TEX_ANISO.
It would be nice to have equivalent features for RADV.

Explanation why it would make sense to have these:
Some games/applications don't offer options for these features and the user may
not like the choice the application forces on him.
For example, a casual game runs with hundreds or thousands of frames per
second, which wastes lots of energy. Or a game doesn't offer to turn vsync off
and the user doesn't want the additional input lag that comes with this.
Enforceable vsync on/off would be very helpful in such cases.

Regarding anisotropic filtering:
Some games tend to ignore to apply AF to every texture when it's not enforced
via the driver. Sometimes even ground textures look blurry due to this, which
is a real shame. There are lots of examples for this when running DX11 games
with DXVK on RADV, e.g. Dying Light or Hitman (they run faster with DXVK than
the official OGL Linux ports).

You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20180726/f3beda05/attachment.html>

More information about the mesa-dev mailing list