diff --git a/site/content/entry/yuzu-progress-report-sep-2021/8.png b/site/content/entry/yuzu-progress-report-sep-2021/8.png
new file mode 100644
index 00000000..cce737c5
Binary files /dev/null and b/site/content/entry/yuzu-progress-report-sep-2021/8.png differ
diff --git a/site/content/entry/yuzu-progress-report-sep-2021/array.png b/site/content/entry/yuzu-progress-report-sep-2021/array.png
new file mode 100644
index 00000000..dae5f658
Binary files /dev/null and b/site/content/entry/yuzu-progress-report-sep-2021/array.png differ
diff --git a/site/content/entry/yuzu-progress-report-sep-2021/art.png b/site/content/entry/yuzu-progress-report-sep-2021/art.png
new file mode 100644
index 00000000..fe9f6dc8
Binary files /dev/null and b/site/content/entry/yuzu-progress-report-sep-2021/art.png differ
diff --git a/site/content/entry/yuzu-progress-report-sep-2021/banner.png b/site/content/entry/yuzu-progress-report-sep-2021/banner.png
new file mode 100644
index 00000000..48252dde
Binary files /dev/null and b/site/content/entry/yuzu-progress-report-sep-2021/banner.png differ
diff --git a/site/content/entry/yuzu-progress-report-sep-2021/blast.png b/site/content/entry/yuzu-progress-report-sep-2021/blast.png
new file mode 100644
index 00000000..4acdc272
Binary files /dev/null and b/site/content/entry/yuzu-progress-report-sep-2021/blast.png differ
diff --git a/site/content/entry/yuzu-progress-report-sep-2021/botwbug.png b/site/content/entry/yuzu-progress-report-sep-2021/botwbug.png
new file mode 100644
index 00000000..f12767a9
Binary files /dev/null and b/site/content/entry/yuzu-progress-report-sep-2021/botwbug.png differ
diff --git a/site/content/entry/yuzu-progress-report-sep-2021/botwfix.png b/site/content/entry/yuzu-progress-report-sep-2021/botwfix.png
new file mode 100644
index 00000000..1e55fb13
Binary files /dev/null and b/site/content/entry/yuzu-progress-report-sep-2021/botwfix.png differ
diff --git a/site/content/entry/yuzu-progress-report-sep-2021/brain.png b/site/content/entry/yuzu-progress-report-sep-2021/brain.png
new file mode 100644
index 00000000..bac5c000
Binary files /dev/null and b/site/content/entry/yuzu-progress-report-sep-2021/brain.png differ
diff --git a/site/content/entry/yuzu-progress-report-sep-2021/cube.png b/site/content/entry/yuzu-progress-report-sep-2021/cube.png
new file mode 100644
index 00000000..8cbc7a4d
Binary files /dev/null and b/site/content/entry/yuzu-progress-report-sep-2021/cube.png differ
diff --git a/site/content/entry/yuzu-progress-report-sep-2021/death.png b/site/content/entry/yuzu-progress-report-sep-2021/death.png
new file mode 100644
index 00000000..d582366f
Binary files /dev/null and b/site/content/entry/yuzu-progress-report-sep-2021/death.png differ
diff --git a/site/content/entry/yuzu-progress-report-sep-2021/debugbug.png b/site/content/entry/yuzu-progress-report-sep-2021/debugbug.png
new file mode 100644
index 00000000..8767eba3
Binary files /dev/null and b/site/content/entry/yuzu-progress-report-sep-2021/debugbug.png differ
diff --git a/site/content/entry/yuzu-progress-report-sep-2021/debugfix.png b/site/content/entry/yuzu-progress-report-sep-2021/debugfix.png
new file mode 100644
index 00000000..872311f8
Binary files /dev/null and b/site/content/entry/yuzu-progress-report-sep-2021/debugfix.png differ
diff --git a/site/content/entry/yuzu-progress-report-sep-2021/diablo.png b/site/content/entry/yuzu-progress-report-sep-2021/diablo.png
new file mode 100644
index 00000000..6deb579d
Binary files /dev/null and b/site/content/entry/yuzu-progress-report-sep-2021/diablo.png differ
diff --git a/site/content/entry/yuzu-progress-report-sep-2021/dqbug.png b/site/content/entry/yuzu-progress-report-sep-2021/dqbug.png
new file mode 100644
index 00000000..e41f3710
Binary files /dev/null and b/site/content/entry/yuzu-progress-report-sep-2021/dqbug.png differ
diff --git a/site/content/entry/yuzu-progress-report-sep-2021/dqfix.png b/site/content/entry/yuzu-progress-report-sep-2021/dqfix.png
new file mode 100644
index 00000000..b6a71f04
Binary files /dev/null and b/site/content/entry/yuzu-progress-report-sep-2021/dqfix.png differ
diff --git a/site/content/entry/yuzu-progress-report-sep-2021/exit.png b/site/content/entry/yuzu-progress-report-sep-2021/exit.png
new file mode 100644
index 00000000..6628fd51
Binary files /dev/null and b/site/content/entry/yuzu-progress-report-sep-2021/exit.png differ
diff --git a/site/content/entry/yuzu-progress-report-sep-2021/framerate.png b/site/content/entry/yuzu-progress-report-sep-2021/framerate.png
new file mode 100644
index 00000000..bc0b587c
Binary files /dev/null and b/site/content/entry/yuzu-progress-report-sep-2021/framerate.png differ
diff --git a/site/content/entry/yuzu-progress-report-sep-2021/index.md b/site/content/entry/yuzu-progress-report-sep-2021/index.md
new file mode 100644
index 00000000..0900d1d2
--- /dev/null
+++ b/site/content/entry/yuzu-progress-report-sep-2021/index.md
@@ -0,0 +1,325 @@
++++
+date = "2021-10-11T12:00:00-03:00"
+title = "Progress Report September 2021"
+author = "GoldenX86"
+coauthor = "Honghoa"
+forum = 472953
++++
+
+Hi yuz-ers! Welcome to the latest entry of our monthly progress reports. We have even more GPU rendering fixes, TAS support, 8 player mayhem, input and UI 
+changes, some preliminary work for future big changes, and more!
+
+<!--more--> 
+
+## Yet more AMD specific changes and other graphical fixes
+
+Certain AMD and Intel GPUs were unable to utilize yuzu's unlock FPS feature with the Vulkan API, due to the lack of driver support for the `VK_PRESENT_MODE_MAILBOX_KHR` presentation mode.
+They, however, support `VK_PRESENT_MODE_IMMEDIATE_KHR`, another mode that allows Vulkan to present at a higher framerate than the screen refresh rate, so 
+[epicboy](https://github.com/ameerj) made the [necessary changes](https://github.com/yuzu-emu/yuzu/pull/7003) in order to unlock the FPS on these GPUs.
+Due to the nature of this presentation mode, this may cause visible tearing on the screen, so bear that in mind if you try this out.
+
+{{< imgs
+	"./framerate.png| And this is with just an RX 550 (Metroid Dread)"
+  >}}
+
+Booting a title in Linux with the Vulkan API using the Intel Mesa driver resulted in a crash due to a device loss error.
+The problem was in the synchronization between the rendering and subsequent presentation of frames.
+
+Previously, yuzu would issue the Vulkan `Present` command, then wait for the frame to be rendered before continuing with the process.
+While this was fine for other drivers and vendors, ANV (Intel’s Vulkan driver) expected to have the frame already rendered before this command, causing this error.
+
+epicboy fixed the synchronization behaviour so that 
+[yuzu now waits until the frame is fully rendered and ready before presenting it](https://github.com/yuzu-emu/yuzu/pull/6953).
+
+With the release of AMD’s Windows driver version 21.9.1, and its equivalent AMDVLK and AMDGPU-PRO Vulkan Linux counterparts, users started noticing crashes in most games right 
+at boot.
+We rushed once again to blame AMD for breaking another extension, as it wouldn’t be the first time.
+We even singled out `Int8Float16` as the culprit, providing an 
+[alternative path that reduced performance on all AMD GPUs running non-RADV drivers.](https://github.com/yuzu-emu/yuzu/pull/7006)
+
+We were wrong.
+
+Turns out, it was our fault. 
+epicboy found out that during the process of initializing Vulkan, the emulator 
+[assigned Int8Float16’s values after its memory was freed.](https://github.com/yuzu-emu/yuzu/pull/7027) 
+Surprisingly, this only started affecting official AMD drivers recently, after their periodical Vulkan version update.
+So we had to lay down the pitchforks, *this time.*
+Performance returned to normal after the introduction of this PR.
+
+AMD Windows users are also familiar with certain stages in `Super Smash Bros. Ultimate` turning completely white or ghosting, akin to when applications [would freeze](https://i.stack.imgur.com/4Jh7t.jpg) back in the Windows XP era.
+Those were the good days. 
+
+Ahem, anyway, AMD Radeon GPUs lack support for fixed point 24-bit depth textures, or D24 for short, a relatively common texture format.
+To bypass this hardware limitation, yuzu uses D32 textures instead, which can cause precision issues during the conversion process. 
+[By adjusting the Depth Bias and Polygon Offset of yuzu’s D24 emulation,](https://github.com/yuzu-emu/yuzu/pull/7070) [Blinkhawk](https://github.com/FernandoS27) solves the issue for good.
+
+{{< single-title-imgs
+    "Fair play, please (Super Smash Bros. Ultimate)"
+    "./smashbug.png"
+    "./smashfix.png"
+    >}}
+
+Yet another AMD Radeon specific issue is visible when playing `The Legend of Zelda: Breath of the Wild`.
+Terrain textures were colourful and corrupted, like when a PC gamer dials up the RGB to 11.
+
+This issue affected our regular suspects, GCN4 devices (Polaris, RX 400/500 series) and older, running on the Windows and Linux proprietary Vulkan drivers. 
+GCN5 (Vega), RDNA1, and RDNA2 devices were unaffected.
+The problem resided in how we guessed the textures were being handled by the game.
+
+Some information first: there are several ways to handle textures, and in this particular example we need to focus on two, `Cube Maps` and `Texture Arrays`.
+
+Cube maps are a cube with its six faces filled with different textures.
+The coordinate used to fetch the data, unlike the regular X and Y values, is a single [versor](https://en.wikipedia.org/wiki/Versor) originating from the center and pointing 
+to the surface of the cube.
+
+{{< imgs
+	"./array.png| "
+  >}}
+
+Texture arrays on the other hand are just as the name implies, an ordered array of textures one after the other, with X and Y used for positioning information inside the 
+texture, and a Z axis used to determine which texture of the array is in use.
+
+{{< imgs
+	"./cube.png| "
+  >}}
+
+TL;DR, one is a sphere and the other is a list.
+
+Vulkan allows for textures to be marked for conversion into cube maps if later needed, but the sampling (reading) is determined by the texture type specified by the game’s shader 
+instructions. This type is then passed to the graphics API.
+We do just this and the game decides to keep its textures as arrays, which is its own decision.
+However, the AMD driver decides that the textures should be sampled as cube maps, ignoring what the texture view determined just before.
+
+While this should not be a problem on its own, as coordinates can still be pulled out from the wrong texture type, the driver can end up reading the wrong texel.
+This can result in happy rainbow ground in `The Legend of Zelda: Breath of the Wild`, or as dark and evil terrain in `Hyrule Warriors: Age of Calamity`.
+
+[By disabling Cube Compatibility on GCN4 and older devices running the official AMD proprietary drivers,](https://github.com/yuzu-emu/yuzu/pull/7076) epicboy returned proper 
+sense to the devastated land of Hyrule.
+
+{{< imgs
+	"./botwbug.png| I prefer no RGB, thanks (The Legend of Zelda: Breath of the Wild)"
+  >}}
+
+{{< imgs
+	"./botwfix.png| But not THAT dark! (Hyrule Warriors: Age of Calamity)"
+  >}}
+
+Speaking of RGB, [as discussed back in February](https://yuzu-emu.org/entry/yuzu-progress-report-feb-2021/#paint-me-like-one-of-your-french-bits), yuzu has to use compute 
+shaders to convert most BGR texture formats in OpenGL to avoid mismatched colours.
+While this can work fine on most current GPUs, there’s a performance cost that can affect older and slower products.
+
+Users of Kepler series Nvidia GPUs (usually GTX 600/700 series, with several renamed 800 and 900 series too) could experience those performance penalties while also producing 
+rendering corruptions.
+Instead of using compute shaders to swizzle textures, epicboy figured we could just use `Pixel Buffer Objects` 
+[(or PBO for short)](https://www.khronos.org/opengl/wiki/Pixel_Buffer_Object) for [all affected texture formats instead.](https://github.com/yuzu-emu/yuzu/pull/7036) 
+This has many benefits: it solves Kepler BGR issues, improves performance on weak devices from any GPU vendor, and is also a required change for `A.R.T.` (the resolution 
+scaler in development).
+
+{{< single-title-imgs
+    "A Hat in Time"
+    "./keplerbug.png"
+    "./keplerfix.png"
+    >}}
+
+On the subject of changes needed for the resolution scaler, Blinkhawk implemented [fixes to queries and indexed samplers.](https://github.com/yuzu-emu/yuzu/pull/7077)
+The result is fewer crashes while playing `Luigi’s Mansion 3` on Intel and AMD GPUs, be it on Windows or Linux. 
+This PR helps improve stability for `A.R.T.` as well.
+
+Another issue affecting `Luigi’s Mansion 3` is related to its use of [Tessellation Shaders](https://en.wikipedia.org/wiki/Tessellation_(computer_graphics)) on Vulkan.
+The Vulkan specification requires the input-assembler topology to be `PATCH_LIST` in the tessellation stages. Not all games follow this, so 
+[manually forcing it](https://github.com/yuzu-emu/yuzu/pull/7101) solves crashes experienced in some drivers, more specifically, as you may have guessed it, AMD’s proprietary 
+ones. All thanks to our fishy epicboy.
+
+epicboy has also [fixed some minor bugs with the `StencilOp`](https://github.com/yuzu-emu/yuzu/pull/7001), a type of data buffer intended to help limit the size of the 
+rendering area. 
+Thanks to this, `WarioWare: Get It Together!` properly renders its models.
+
+{{< single-title-imgs
+    "Waa! (WarioWare: Get It Together!)"
+    "./waabug.png"
+    "./waafix.png"
+    >}}
+
+[vonchenplus](https://github.com/vonchenplus) added support for the legacy GLSL `gl_Color` and `gl_TexCoord` attributes into our Vulkan backend, so that any game that uses 
+them can render properly when using this API.
+
+Both these attributes are part of a set of attributes with specific definitions and uses.
+But they were deprecated in newer versions of OpenGL in favour of "generic" attributes that the programmer can freely define as they want, based on their needs.
+
+While OpenGL is still able to run shaders that use this legacy feature for the sake of  backwards compatibility, they were already considered obsolete by the time Vulkan was 
+created, which means that this API lacks a fallback.
+
+What vonchenplus did is use generic attributes in Vulkan to emulate these features, so that they behave exactly as the legacy GLSL attributes.
+
+After that, vonchenplus corrected the definition of [the values in an enum](https://github.com/yuzu-emu/yuzu/pull/6980) used for blending textures.
+
+Both these changes affect `DRAGON QUEST III: The Seeds of Salvation`, fixing the graphical bugs present in this game.
+
+{{< single-title-imgs
+    "DRAGON QUEST III: The Seeds of Salvation"
+    "./dqbug.png"
+    "./dqfix.png"
+    >}}
+
+## Tool-assisted speedrun
+
+[MonsterDruide1](https://github.com/MonsterDruide1) has added [TAS support](https://github.com/yuzu-emu/yuzu/pull/6485) to yuzu!
+This means precise input commands can be recorded and replayed in-game.
+The format used to store them is the one [TAS-nx](https://github.com/hamhub7/TAS-nx/tree/master/scripts) implemented, and we have a guide on 
+[how to enable and use this feature here.](https://yuzu-emu.org/help/feature/tas/)
+
+You can access TAS configuration by going to `Tools > Configure TAS…`
+
+{{< imgs
+	"./tas.png| TAS Configuration window"
+  >}}
+
+## Other input changes
+
+Let’s start with a nice addition by [german77](https://github.com/german77) that will make `Super Smash Bros. Ultimate` players happy, and Parsec users especially so. 
+There’s now an option to enable [8 player support](https://github.com/yuzu-emu/yuzu/pull/6950) for XInput devices, at the cost of disabling the Web Applet. A small price to pay 
+for epic fights with your friends.
+
+You can find the option in `Emulation > Configure… > Controls > Advanced > Enable XInput 8 player support (disables web applet)`.
+
+{{< imgs
+	"./8.png| yuzu Controls configuration window"
+  >}}
+
+[v1993](https://github.com/v1993) later [hid the option for non-Windows OSes](https://github.com/yuzu-emu/yuzu/pull/7042), as this limitation doesn’t apply outside the Windows 
+SDL builds.
+
+Linux kernel drivers for Joy-Cons use a different naming convention than the ones we use on Windows. 
+[Properly following this convention makes the Dual Joy-Con input show up in the device list.](https://github.com/yuzu-emu/yuzu/pull/6979) german77 thinks of the penguins.
+
+## UI changes
+
+With the release of [Project Hades](https://yuzu-emu.org/entry/yuzu-hades/), yuzu started using a full `Pipeline cache` instead of single stages of the graphics pipeline, both 
+in Vulkan and OpenGL.
+This means parts of our UI were outdated, so [your degenerate writer](https://github.com/goldenx86) decided to simply 
+[update the context menu entries](https://github.com/yuzu-emu/yuzu/pull/6976) from Shader cache to Pipeline cache.
+
+Following suit, [Moonlacer](https://github.com/Moonlacer) helped [replace `Use disk shader cache` with `Use disk pipeline cache`](https://github.com/yuzu-emu/yuzu/pull/6977). 
+¡Gracias!
+
+Later on, Moonlacer [removed the toggle](https://github.com/yuzu-emu/yuzu/pull/7020) for `Enable audio stretching` from the audio settings, as it no longer had any purpose. 
+As a general rule, the fewer options available, the better.
+
+Morph decided to [eliminate a 2 year old feature,](https://github.com/yuzu-emu/yuzu/pull/7102) [boxcat](https://yuzu-emu.org/entry/yuzu-boxcat/). 
+
+BCAT is a network service used by the Nintendo Switch to add content to its games without needing constant updates.
+Our old BCAT implementation only added some “gifts” our developers placed into games that were playable at the time. It was unable to support real use cases, like the game
+updates `Animal Crossing: New Horizons` regularly pushes.
+
+While the plan is to add support for this in the future, major changes to the file system emulation need to come first.
+
+[behunin](https://github.com/behunin) implemented much needed [clean ups to our debug configuration window.](https://github.com/yuzu-emu/yuzu/pull/7068)
+View the results below:
+
+{{< single-title-imgs
+    "Before and After, Debug configuration settings"
+    "./debugbug.png"
+    "./debugfix.png"
+    >}}
+
+## General bugfixes
+
+epicboy noticed a memory leak that would grow progressively after stopping and restarting the emulation, which was caused by yuzu’s `main_process` not being cleaned up.
+[By destroying this process when stopping emulation](https://github.com/yuzu-emu/yuzu/pull/7009), the resources are properly freed now, fixing the leak.
+
+Additionally, epicboy also mitigated the crashes that happened when emulation was stopped by 
+[using std::jthread for worker threads](https://github.com/yuzu-emu/yuzu/pull/7019).
+
+`std::jthread` is a [new implementation of the thread class that was recently introduced in C++20](https://en.cppreference.com/w/cpp/thread/jthread), which alleviates their 
+management and usage, since they simplify some of the synchronization challenges inherent to multithreading.
+
+With this change, the number of crashes caused by race conditions between working threads upon shutdown was supposed to decrease, but it also introduced a new bug that would 
+cause yuzu to hang when the emulation was stopped.
+
+This problem was caused by the order in which objects were being destroyed, which epicboy 
+[fixed in a follow-up PR](https://github.com/yuzu-emu/yuzu/pull/7078).
+
+[bunnei](https://github.com/bunnei) also [introduced std::jthreads into the cpu_manager](https://github.com/yuzu-emu/yuzu/pull/6965), in favour of using this more efficient 
+implementation of the class for yuzu's host threads.
+
+He also made changes so that the KEvents used in the nvflinger [service](https://github.com/yuzu-emu/yuzu/pull/6968) and [queue](https://github.com/yuzu-emu/yuzu/pull/6971) 
+are owned by these services, instead of being owned by the process for the emulated game, which makes the implementation more accurate.
+
+We’ve been trying to focus on improving our homebrew support, as this isn’t just a powerful tool that only developers use. For example, modders have very powerful homebrew apps 
+that the Switch community enjoys.
+One important example is [UltimateModManager](https://github.com/ultimate-research/UltimateModManager), or UMM for short, which refuses to work on yuzu for now.
+
+To counter this, [ogniK](https://github.com/ogniK5377) allowed homebrew running in yuzu to [also create subdirectories instead of just the parent directory](https://github.com/yuzu-emu/yuzu/pull/6974), 
+resulting in UMM managing to at least start. 
+This is a temporary solution until our much needed filesystem rewrite is finished.
+Additionally, [Morph](https://github.com/Morph1984) pushed a [partial implementation of the `GetFileTimeStampRaw` function,](https://github.com/yuzu-emu/yuzu/pull/7010) removing 
+several warnings.
+
+This isn’t enough to allow full UMM compatibility, but we’re getting there.
+
+Moving on to a quality-of-life change, some games pop-up a confirmation window when trying to stop emulation.
+
+{{< imgs
+	"./exit.png| Like this, End emulation confirmation window"
+  >}}
+
+This kind of redundant question is generated by the game itself and while we always had a toggle to skip it, it wasn’t working properly. epicboy comes to the rescue, 
+[fixing the toggle](https://github.com/yuzu-emu/yuzu/pull/6997) for good and saving us precious seconds in quitting our games.
+
+If you wish to change this behaviour, the option is in `Emulation > Configure… > General > Confirm exit while emulation is running`.
+
+v1993 [moved all QtWebEngine data to a more organized centralized folder,](https://github.com/yuzu-emu/yuzu/pull/7075) improving consistency and reducing clutter from the 
+user’s storage.
+Instead of a separate folder in `%localappdata%`, information is now saved in yuzu’s directory, `%appdata%\yuzu\qtwebengine` by default.
+
+[toastUnlimited](https://github.com/lat9nq) 
+[performed his first stubbing surgery with the audio input services `Start`, `RegisterBufferEvent`, and `AppendAudioInBufferAuto`](https://github.com/yuzu-emu/yuzu/pull/7018).
+This way, `Splatoon 2` can now be played via [LAN](https://yuzu-emu.org/entry/yuzu-progress-report-aug-2021/#lan-party-time) without requiring the use of auto-stub. Happy 
+splatting!
+
+german77 [stubbed `SetTouchScreenConfiguration` and implemented `GetNotificationStorageChannelEvent`](https://github.com/yuzu-emu/yuzu/pull/6992) to make `Dr Kawashima's Brain 
+Training for Nintendo Switch` playable.
+
+{{< imgs
+	"./brain.png| Dr Kawashima's Brain Training for Nintendo Switch"
+  >}}
+
+He has also [stubbed `Match`](https://github.com/yuzu-emu/yuzu/pull/7015) to make `Cruis'n Blast` playable. 
+This game experiences some crashes, so there’s more work to do.
+
+{{< imgs
+	"./blast.png| Cruis'n Blast"
+  >}}
+
+ogniK [implemented the `EnsureTokenIdCacheAsync` function,](https://github.com/yuzu-emu/yuzu/pull/6975) making `Death Coming` go in-game, albeit with some graphical bugs that 
+we have to sort out in the future.
+
+{{< imgs
+	"./death.png| Death Coming"
+  >}}
+
+Morph has been working on implementing what is needed to get `Diablo II: Resurrected` working.
+Initially, the [`Read` socket service was implemented](https://github.com/yuzu-emu/yuzu/pull/7082), but this mandates also implementing more complex services like `Select` and 
+`EventFD`. 
+`EventFD` is particularly tricky as there is no native support for it on Windows, so a considerable amount of work is needed to properly emulate it in the most popular OS.
+
+As a temporary alternative, [Read was just stubbed](https://github.com/yuzu-emu/yuzu/pull/7085), allowing the game to boot.
+
+{{< imgs
+	"./diablo.png| Diablo II: Resurrected"
+  >}}
+
+## Future projects
+
+For anyone wondering about `Project A.R.T.`, the following image speaks for itself.
+
+{{< imgs
+	"./art.png| Xenoblade Chronicles Definitive Edition"
+  >}}
+
+Regarding works in progress, there are more rendering fixes underway, and we’re already starting plans on what to focus on after `A.R.T.` is finished.
+
+That’s all folks! Thank you for your attention and see you next month!
+
+&nbsp;
+{{< article-end >}}
diff --git a/site/content/entry/yuzu-progress-report-sep-2021/keplerbug.png b/site/content/entry/yuzu-progress-report-sep-2021/keplerbug.png
new file mode 100644
index 00000000..468eced9
Binary files /dev/null and b/site/content/entry/yuzu-progress-report-sep-2021/keplerbug.png differ
diff --git a/site/content/entry/yuzu-progress-report-sep-2021/keplerfix.png b/site/content/entry/yuzu-progress-report-sep-2021/keplerfix.png
new file mode 100644
index 00000000..eef65ff2
Binary files /dev/null and b/site/content/entry/yuzu-progress-report-sep-2021/keplerfix.png differ
diff --git a/site/content/entry/yuzu-progress-report-sep-2021/smashbug.png b/site/content/entry/yuzu-progress-report-sep-2021/smashbug.png
new file mode 100644
index 00000000..47271eda
Binary files /dev/null and b/site/content/entry/yuzu-progress-report-sep-2021/smashbug.png differ
diff --git a/site/content/entry/yuzu-progress-report-sep-2021/smashfix.png b/site/content/entry/yuzu-progress-report-sep-2021/smashfix.png
new file mode 100644
index 00000000..9b7c1180
Binary files /dev/null and b/site/content/entry/yuzu-progress-report-sep-2021/smashfix.png differ
diff --git a/site/content/entry/yuzu-progress-report-sep-2021/summary.png b/site/content/entry/yuzu-progress-report-sep-2021/summary.png
new file mode 100644
index 00000000..389905cc
Binary files /dev/null and b/site/content/entry/yuzu-progress-report-sep-2021/summary.png differ
diff --git a/site/content/entry/yuzu-progress-report-sep-2021/tas.png b/site/content/entry/yuzu-progress-report-sep-2021/tas.png
new file mode 100644
index 00000000..558c7eb7
Binary files /dev/null and b/site/content/entry/yuzu-progress-report-sep-2021/tas.png differ
diff --git a/site/content/entry/yuzu-progress-report-sep-2021/waabug.png b/site/content/entry/yuzu-progress-report-sep-2021/waabug.png
new file mode 100644
index 00000000..404b79fc
Binary files /dev/null and b/site/content/entry/yuzu-progress-report-sep-2021/waabug.png differ
diff --git a/site/content/entry/yuzu-progress-report-sep-2021/waafix.png b/site/content/entry/yuzu-progress-report-sep-2021/waafix.png
new file mode 100644
index 00000000..355d1ef4
Binary files /dev/null and b/site/content/entry/yuzu-progress-report-sep-2021/waafix.png differ