[getzabelz]

What this is for: the readme's Project status table points readers at bugs that are already closed and describes the ultrawide HUD as it was before the Aspect ratio row. This brings it in line with main 51da046. What changed: readme.md only, the intro and five rows. Not changed: the other rows (including Performance and the mesh-shader fallback, which still match the code: vk_draw.cpp still leaves out mesh draws whose count comes from a buffer).

What changed

• Links to closed issues → the open tracking issues. All eight issues the table cited as open problems are closed:

  Row	Was	Closed as	Now
  Hyrule Field, Castle Town…	Shadows going crazy in Hyrule Field (later in Castle Town - Video) #468	duplicate of [Tracking] Lighting: overexposure, over-bright bloom, crushed or black shadows, black faces #1004	[Tracking] Lighting: overexposure, over-bright bloom, crushed or black shadows, black faces #1004 (lighting and shadows)
  	Crashing in Hyrule Castle Town #317	not planned (no log)	[Tracking] Crashes, freezes and device lost on NVIDIA and other cards (AMD: #996, Intel: #999, Linux: #1000) #2507 (crashes and freezes)
  	[AMD RX 9070 XT] Reproducible crash in Hyrule Field: write to guest address 0 after "flags of no memory pool" (thread OptimizeChangeBanc) #648	fixed in v2.0.0	(dropped)
  AMD cards	[AMD RX 6600] Reproducible Vulkan device loss and crash inside Deku Tree on v2.0.2 #708, Crash into deku #614	duplicates of [Tracking] AMD on Windows: driver crash, device lost or freeze (RX 5000-9000, Deku Tree / after cutscenes) #996	[Tracking] AMD on Windows: driver crash, device lost or freeze (RX 5000-9000, Deku Tree / after cutscenes) #996
  Intel cards	Intel GPU Issues #17	duplicate of [Tracking] Intel Arc and Core Ultra iGPUs: device lost, black screen after the intro, Linux ANV crashes #999	[Tracking] Intel Arc and Core Ultra iGPUs: device lost, black screen after the intro, Linux ANV crashes #999
  Linux	RX 6800 XT (RADV, Linux): GPU hang and full GPU reset a few seconds after loading a save in Kokiri, also with RX_VK_KEEP_RETIRED=1 #604, [AMD RX 9070 / RADV Linux] Low FPS (22-25) in Kokiri Forest + color distortion & background flicker #528	duplicates of [Tracking] Linux and Steam Deck: GPU hangs, crashes, low FPS and build failures #1000	[Tracking] Linux and Steam Deck: GPU hangs, crashes, low FPS and build failures #1000

• Ultrawide and 4:3: it said the HUD is stretched. Since feat(menu): the Aspect ratio row (was Ultrawide), at the monitor's shape by default #2119 the Aspect ratio row's default (Monitor's shape) keeps the HUD and movies in the middle 16:9, as the readme's own menu notes already say. ⚠️ → ✅.

• AMD cards:

  • adds the RX 6800 XT (RX 6800 XT (RADV, Linux): GPU hang and full GPU reset a few seconds after loading a save in Kokiri, also with RX_VK_KEEP_RETIRED=1 #604) and RX 9070 XT ([AMD RX 9070 XT] Reproducible crash in Hyrule Field: write to guest address 0 after "flags of no memory pool" (thread OptimizeChangeBanc) #648) reports;
  • adds that on Windows the RX 6000 cards (Navi 21 and 22) take the task + mesh compute fallback by default (Work around AMD Vulkan task shader timeouts and restore cloth rendering #1747, fix(vk): task + mesh draws through the compute fallback on Navi 21 too (#996) #1992, fix(vk): the Navi 21 task + mesh fallback also covers the RX 6900 XT XTXH and RX 6950 XT (#996) #2215);
  • the RX 6600 Deku Tree note becomes a pointer to [Tracking] AMD on Windows: driver crash, device lost or freeze (RX 5000-9000, Deku Tree / after cutscenes) #996.

• Intro: no longer says testing stayed near the start of the game, since the table itself reports players in the dungeons. It now also says that open problems are collected in tracking issues.

Checks

• Issue states and close reasons read with gh issue view; the cited PRs (Work around AMD Vulkan task shader timeouts and restore cloth rendering #1747, fix(vk): task + mesh draws through the compute fallback on Navi 21 too (#996) #1992, feat(menu): the Aspect ratio row (was Ultrawide), at the monitor's shape by default #2119, fix(vk): the Navi 21 task + mesh fallback also covers the RX 6900 XT XTXH and RX 6950 XT (#996) #2215) are all merged.
• No test reads this table (searched tests/).

[Joey-Magnus]

I checked the claims against GitHub and main.

• The eight issues the table cited (#468, #317, #648, #708, #614, #17, #604, #528) are all closed. The replacements (#1004, #2507, #996, #999, #1000) are the open tracking issues.
• #1747, #1992 and #2215 are merged, and gpu/vk/vk_main.cpp:550 does pick the compute fallback for Navi 21 device IDs, so the AMD row is accurate.
• The Ultrawide row matches the Aspect ratio default from #2119.

No test reads this table, and CI is green. It also merges cleanly alongside #2747 and #2755, which edit other parts of readme.md. The before/after picture is a screenshot of the readme, not game content.