| Age | Commit message (Collapse) | Author |
|---|
|
Yellow squiggly lines begone!
Done automatically on .cpp files through `run-clang-tidy`, with manual corrections to the mistakes.
If an import is directly used, but is technically unnecessary since it's recursively imported by something else, it is *not* removed.
The tool doesn't touch .h files, so I did some of them by hand while fixing errors due to old recursive imports.
Not everything is removed, but the cleanup should be substantial enough.
Because this done on Linux, code that isn't used on it is mostly untouched.
(Hopefully no open PR is depending on these imports...)
|
|
consistent
|
|
They appear to have been unused since #13432.
|
|
initialized
|
|
shaders and provide a direct override of the tev stage logic
|
|
VideoCommon: move lighting shader logic to callable functions
|
|
Fix depth texture being incorrectly affected by swap table
|
|
|
|
|
|
|
|
This saves three instructions on AMD GPUs. Dunno about Nvidia.
|
|
VideoCommon: allow custom shaders to set the alpha value
|
|
VideoCommon: More specific subgroup op bugs
|
|
blending is enabled
|
|
A nonzero index makes no sense, and Mesa doesn't like it when you supply an index
|
|
We now use subgroup ops for more than just a minor performance optimization
|
|
isn't set for custom shaders
|
|
output is defined
|
|
|
|
uniform to be able to support animation effects in custom shaders
|
|
in graphics mods
|
|
|
|
|
|
While the NV extension is totally fine, the KHR extension should be able to support more hardware.
For NVIDIA, the hardware either supports both or neither, it just needs a driver from the last two years.
For AMD, the drivers from late 2022-12 seems to bring support for the KHR extension.
For Intel, the KHR is also supported for some years.
|
|
Kill Renderer (with phire)
|
|
They were essentially just pass-though methods
|
|
|
|
|
|
stereoscopic 3D
Otherwise, texelFetch() will use an out-of-bounds layer for game textures (that have 1 layer; EFB copies have 2 layers in stereoscopic 3D mode), which is undefined behavior (often resulting in a black image). The fast texture sampling path uses texture(), which always clamps (see https://www.khronos.org/opengl/wiki/Array_Texture#Access_in_shaders), so it was unaffected by this difference.
|
|
VideoCommon: fix uint shader compiler error when using d3d
|
|
It stores both the konst selection value for alpha and color channels (for two tev stages per ksel), and half of a swap table row (there are 4 total swap tables, which can be used for swizzling the rasterized color and the texture color, and indices selecting which tables to use are stored per tev stage in the alpha combiner). Since these are indexed very differently, the old code was hard to follow.
|
|
error is in renderers that use uint for their color output (for logic ops). Remove D3D check for uint output since other backends could use uint output as well.
|
|
|
|
Add a post-cache shader UID fixup pass
|
|
Adds a pass to process driver deficiencies between UID caching and use, allowing a full view of the whole pipeline, since some bugs/workarounds involve interactions between blend modes and the pixel shader
|
|
|
|
|
|
generation
|
|
|
|
|
|
DriverDetails: Add broken discard with early-Z bug on Apple Silicon GPUs
|
|
|
|
|
|
|
|
|
|
Previously we were using this workaround when using framebuffer fetch
to emulate dual source blending, but it seems like we also need to use
it when using framebuffer fetch to emulate logic ops, otherwise some
Adreno devices get a crash when compiling OpenGL ES ubershaders.
Using the workaround in specialized shaders doesn't seem to be
necessary, but I've made the same change there for consistency.
This gets us closer to fixing https://bugs.dolphin-emu.org/issues/12791
but doesn't actually fix it.
|
|
On devices which have hardware support for dual source blending
but not logic ops, this lets us skip performing the framebuffer
fetch in situations where the game isn't actually using logic ops.
|
|
This removes the white box in fortune street again, without causing Mario Kart Wii to regress.
|
|
It doesn't make sense for alpha to add the bias ONLY when dividing by 2, while color doesn't apply the bias for divide by 2 only; hardware testing indicates that alpha should have the bias.
This fixes the menus in Mario Kart Wii (https://bugs.dolphin-emu.org/issues/11909) but reintroduces the white rectangle in Fortune Street.
This reverts commit 5aaa5141ed76acc3fffc70561a6b6e7fe3b9b470 (and several other matching changes elsewhere).
|
|
|
