From b9036755f50b6eec919a3d5a96dc58f8104b7b86 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mat=C3=ADas=20Locatti?=
 <42481638+goldenx86@users.noreply.github.com>
Date: Fri, 16 Sep 2022 04:50:11 -0300
Subject: [PATCH] Final Flam nit, and forum ID

---
 site/content/entry/yuzu-progress-report-aug-2022/index.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/site/content/entry/yuzu-progress-report-aug-2022/index.md b/site/content/entry/yuzu-progress-report-aug-2022/index.md
index d9618648..8d72875c 100644
--- a/site/content/entry/yuzu-progress-report-aug-2022/index.md
+++ b/site/content/entry/yuzu-progress-report-aug-2022/index.md
@@ -1,8 +1,8 @@
 +++
-date = "2022-09-15T12:00:00-03:00"
+date = "2022-09-16T10:00:00-03:00"
 title = "Progress Report August 2022"
 author = "GoldenX86"
-forum = 0
+forum = 628866
 +++
 
 Welcome back, yuz-ers! August was a month packed with progress. A plethora of graphical changes, kernel and file system improvements, and more work pumped into network emulation. Next slide, please!
@@ -51,7 +51,7 @@ Users can expect much lower VRAM and RAM usage now while running OpenGL and [suf
   >}}
 
 One advantage yuzu's OpenGL backend has had for `Xenoblade Chronicles 3` for some time was stability. 
-It didn't really crash. 
+It didn't really crash. However, Vulkan was another story.
 Even after the initial Vulkan shader fixes previously mentioned, the game would still randomly crash during cutscenes. 
 byte[] was able to reliably reproduce the issue and found that yuzu was receiving some invalid references in the GPU processing. 
 Whether or not this was something the game was legitimately doing, or just an emulation bug, he identified that yuzu could avoid the crash by {{< gh-hovercard "8700" "passing `VK_NULL_HANDLE` for an image view," >}} instead of trying to create an image view for a null image, which was guaranteed to crash.