Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Optimize out some stencil emulation, try to avoid depth write #11620

Merged
merged 4 commits into from
Dec 2, 2018
Merged

Optimize out some stencil emulation, try to avoid depth write #11620

merged 4 commits into from
Dec 2, 2018

Commits on Dec 1, 2018

  1. GPU: Avoid a missing virtual destructor warning.

    @unknownbrackets
    unknownbrackets committed Dec 1, 2018
    Configuration menu
    Copy the full SHA
    b1e68c6 View commit details
    Browse the repository at this point in the history

  2. GPU: Dirty stencil on stencil mask change. 

    Otherwise it doesn't always apply.
    @unknownbrackets
    unknownbrackets committed Dec 1, 2018
    Configuration menu
    Copy the full SHA
    d8c80af View commit details
    Browse the repository at this point in the history

  3. GPU: Avoid stencil emulation if possible. 

    This reduces use of replaceAlpha, and reduces use of more complicated
blend states.  This simplifies fragment shaders a little.
    @unknownbrackets
    unknownbrackets committed Dec 1, 2018
    Configuration menu
    Copy the full SHA
    5932cba View commit details
    Browse the repository at this point in the history

  4. Vulkan: Avoid OpKill workaround with no stencil. 

    It seems like depth gets messed up either way on discard, but behaves
sorta better without the write to depth.
    @unknownbrackets
    unknownbrackets committed Dec 1, 2018
    Configuration menu
    Copy the full SHA
    9a7ee41 View commit details
    Browse the repository at this point in the history