diff options
author | riperiperi <rhy3756547@hotmail.com> | 2023-03-26 11:51:02 +0100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-03-26 12:51:02 +0200 |
commit | a34fb0e9392c59e5bd7a764b83f3460bf65b861b (patch) | |
tree | 486113d26809d85f6567866a18df5a8f3fc456f5 /Ryujinx.Horizon.Kernel.Generators/Kernel | |
parent | 21ce8a9b80c94b0636acb4a8762d8516bdb800e2 (diff) |
Vulkan: Insert barriers before clears (#4596)1.1.682
* Vulkan: Insert barriers before clears
Newer NVIDIA GPUs seem to be able to start clearing render targets before the last rasterization task is completed, which can cause it to clear a texture while it is being sampled.
This change adds a barrier from read to write when doing a clear, assuming it has been sampled in the past. It could be possible for this to be needed for sample into draw by some GPU, but it's not right now afaik.
This should fix visual artifacts on newer NVIDIA GPUs and driver combos. Contrary to popular belief, TetrisĀ® Effect: Connected is not affected. Testing welcome, hopefully should fix most cases of this and not cost too much performance.
* Visual Studio Moment
* Address feedback
* Address Feedback 2
Diffstat (limited to 'Ryujinx.Horizon.Kernel.Generators/Kernel')
0 files changed, 0 insertions, 0 deletions