From 58f3bb1c0738c500f1d1d55a025df7d6ff8c51e9 Mon Sep 17 00:00:00 2001
From: kd-11 <15904127+kd-11@users.noreply.github.com>
Date: Fri, 17 May 2019 16:43:24 +0300
Subject: [PATCH] Updated Graphics Driver Issues (markdown)

---
 Graphics-Driver-Issues.md | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/Graphics-Driver-Issues.md b/Graphics-Driver-Issues.md
index 91753c0..0e704b1 100644
--- a/Graphics-Driver-Issues.md
+++ b/Graphics-Driver-Issues.md
@@ -6,7 +6,7 @@ This page quickly summarizes graphics driver quirks and issues present in GPU dr
 - GLSL compiler is broken. There are likely other issues as well. This driver is unsupported by RPCS3.
 
 **Vulkan.**
-- Raster pattern requires 'Strict Mode' to be enabled to deal with framebuffer feedback loops, otherwise a diagonal line may be observed on screen between triangle edges.
+- No known problems at this time.
 
 ### AMD (proprietary)
 **OpenGL.**
@@ -14,7 +14,6 @@ This page quickly summarizes graphics driver quirks and issues present in GPU dr
 - ~~glGetTexImage/glGetTextureImage/glGetTextureImageEXT do not work with immutable textures if pack/unpack byteswap is requested. Workaround implemented.~~ Fixed in driver version 19.4.3
 
 **Vulkan.**
-- Raster pattern requires 'Strict Mode' to be enabled to deal with framebuffer feedback loops, otherwise a diagonal line may be observed on screen between triangle edges.
 - Primitive restart is 'broken'. This seems to be a GCN hardware bug as it also affects mesa drivers to some extent. Workaround implemented. (confirmed - see [this commit](https://github.com/mesa3d/mesa/commit/eae8f49fc65e6e625f5e05d38c3bf1b61b84bd3d))
 
 ### NVIDIA (proprietary)
@@ -31,5 +30,4 @@ This page quickly summarizes graphics driver quirks and issues present in GPU dr
 - The debug overlay is not visible
 
 **Vulkan.**
-- RADV: Raster pattern requires 'Strict Mode' to be enabled to deal with framebuffer feedback loops, otherwise a diagonal line may be observed on screen between triangle edges.
 - Primitive restart is 'broken'. This seems to be a GCN hardware bug as it also affects proprietary drivers. Workaround implemented. (confirmed - see [this commit](https://github.com/mesa3d/mesa/commit/eae8f49fc65e6e625f5e05d38c3bf1b61b84bd3d))
\ No newline at end of file