| Age | Commit message (Collapse) | Author |
|---|
|
|
|
This reverts commit 1f1b127b69e47728593e8174d4ed8883622792a5.
|
|
This regression did only happen on OpenGL ES.
|
|
No need to do this within the shader per pixel if it can be done once.
|
|
Drivers that don't support GL_ARB_shading_language_420pack require that
the storage qualifier be specified even when inside an interface block.
AMD's driver throws a compile error when "centroid in/out" is used within
an interface block.
Our previous behavior was to include the storage qualifier regardless, but
this wasn't working on AMD, therefore we should check for the presence of
the extension and include based on this, instead.
|
|
Workaround OS X video driver bug #24983074
|
|
OS X's shader compiler has a bug with interface blocks where interface block members don't properly inherit the layout qualifier from the interface
block.
Work around this limitation by explicitly stating the layout qualifier on both the interface block and every single member inside of that block.
|
|
This reverts commit e2a1a085b6a9f36b23128872de85da727d231882, reversing
changes made to 2aea549eef85ba165672c8355d0e90781d805efd.
|
|
Fast depth is now more accurate than slow depth and should always be used.
The option will be kept in a different form as it is still used as a hack to fix some games.
Also, the slow depth code path will still be relied upon by cards that don't support GL_ARB_clip_control.
|
|
|
|
VideoCommon: Header cleanup
|
|
Also remedies places where the video backends and core rely on things
being indirectly included.
|
|
(x % y) is not defined in GLSL when sign(x) != sign(y).
This also has the added benefit of behaving the same as sampler wrapping modes, in regards to negative inputs.
|
|
buffer to ShaderCode
This fixes the crashes occuring at startup with a non-empty shader cache.
Because LinearDiskCache reads/writes to the storage of ShaderUid, ShaderUid must be trivially copyable.
Additionally, adds a static assert to LinearDiskCache to ensure this doesn't happen in the future.
The initialization of ShaderUid data has been moved to the code generation functions, so the above condition holds true.
|
|
Static by itself is sufficient
|
|
|
|
|
|
This should fix this panic message I saw when playing Super Mario Strikers:
Failed to compile pixel shader [...]: error C7011: implicit cast from "int" to "float"
|
|
rather than passing in non-const references
|
|
|
|
|
|
|
|
Allows Mesa based drivers to support ZCompLoc
|
|
|
|
|
|
|
|
|
|
|
|
|
|
These aren't used outside of it. This also reduces the amount of things in
the global namespace.
|
|
These actually convey a concrete type, as well as also providing a
symbolic constant during debugging.
|
|
|
|
The Star Wars games really push the hardware to its limits, which can cause the shaders that are produced to be 18kb or more.
Double our maximum shader size to compensate.
Fixes issue #8860
|
|
This bug has been reported to IMGTec at https://pvrsupport.imgtec.com/ticket/472
The basic idea of the bug is that if you're doing a bitwise and of a constant value vector with a constant scalar value, this causes PowerVR's shader
compiler to fail out with a very non-descriptive message.
Working around the issue by making the value a vector that it is being masked by.
|
|
|
|
Credits go to Galop1n for designing this technique and to BhaaLseN for cleaning up the commit.
|
|
Disable bbox
|
|
|
|
|
|
|
|
The zfreeze option freezes the depth plane of the rasterization.
So this is done before the TEV stages, where the z-textures are applied.
|
|
|
|
instead or rounding.
|
|
|
|
[fixed lint issues and grammar ~comex]
|
|
Partially fix WWE12 titantron videos.
|
|
|
|
The obvious question here is, why does it matter if we round or truncate?
The key is that GC/Wii does fixed-point interpolation, where PC GPUs do
floating-point interpolation. Discarding fractional bits makes the conversion
from floating-point to fixed point give more consistent results.
I'm not confident this is really the right fix, or that my explanation is
completely correct; ideally, we don't want to depend on floating-point
interpolation at all.
|
|
|
|
- Calculate ZSlope every flush but only set PixelShader Constant on Reset Buffer when zfreeze
- Fixed another Pixel Shader bug in D3D that was giving me grief
|
