riperiperi 052deebf26 Another workaround for NVIDIA driver 496.13 shader bug (#2750) ... * Another workaround for NVIDIA driver 496.13 shader bug This might work better than the other one. Give this a test to see if it fixes/doesn't fix issues with the other one. The problem seems to be when any variable assignment happens with a negation. `temp_1 = -temp_0;` seems to trigger weird behaviour, but `temp_1 = 0.0 - temp_0;` does not. This also might to extend towards integer types? * Update cache version * Add disclaimer comment * Wording		2021-10-18 20:04:06 -03:00
..
Cache	Initial tessellation shader support (#2534)	2021-10-18 18:38:04 -03:00
CachedGpuAccessor.cs	Initial tessellation shader support (#2534)	2021-10-18 18:38:04 -03:00
GpuAccessor.cs	Initial tessellation shader support (#2534)	2021-10-18 18:38:04 -03:00
GpuAccessorState.cs	Initial tessellation shader support (#2534)	2021-10-18 18:38:04 -03:00
ShaderAddresses.cs
ShaderBundle.cs
ShaderCache.cs	Another workaround for NVIDIA driver 496.13 shader bug (#2750)	2021-10-18 20:04:06 -03:00
ShaderCacheState.cs
ShaderCodeHolder.cs	Salieri: shader cache (#1701)	2020-11-13 00:15:34 +01:00
ShaderCompileTask.cs	Use a new approach for shader BRX targets (#2532)	2021-08-11 20:59:42 +02:00
ShaderDumper.cs	Make sure attributes used on subsequent shader stages are initialized (#2538)	2021-08-11 22:27:00 +02:00
ShaderDumpPaths.cs	Make sure attributes used on subsequent shader stages are initialized (#2538)	2021-08-11 22:27:00 +02:00
TextureDescriptorCapableGpuAccessor.cs	Rewrite shader decoding stage (#2698)	2021-10-12 22:35:31 +02:00