From 78ee0ddb1e29206ec730bbcfb8f5105cb4087499 Mon Sep 17 00:00:00 2001 From: chrg6 Date: Mon, 9 Nov 2026 11:44:39 -0500 Subject: [PATCH] Say in the 0.6.1 notes that an update from 0.5.0 keeps its compiled game too, and that the device-lost fix covers low memory. Checked with the 0.6.0 launcher's own update path against a local copy of the 0.6.1 release: 552 of the game's 562 objects were taken over, 10 compiled, the prepared shaders kept with the translator that made them named, done 0.2 minutes after the download. Co-Authored-By: Claude Opus 5.5 --- docs/releases/v0.6.1.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/releases/v0.6.1.md b/docs/releases/v0.6.1.md index 85334ed9..9827431a 100644 --- a/docs/releases/v0.6.1.md +++ b/docs/releases/v0.6.1.md @@ -7,6 +7,8 @@ memory fixes, a higher frame rate, Navi's light on AMD GPUs, and updates that ke - **Already have 0.6.0:** start the launcher; it offers 0.6.1, updates itself and keeps the game it compiled: only what changed is compiled again, and the prepared shaders are kept. The shader translator changed, so the game plays with the shaders already prepared and translates them again in the background. +- **Already have 0.5.0:** the same, and the game's code 0.5.0 compiled is kept too, as it was compiled (for any x86-64 + processor); *Rebuild the Game* in the launcher's home compiles it again for yours. - **New install:** download **`NX2navi-Setup-0.6.1.exe`** below, put it next to your `.nup` dump of the game and start it. Windows SmartScreen warns on the first start because the setup is not signed: choose *More info* and *Run anyway*. The launcher builds the game (10 to 25 minutes, once), prepares every shader and starts it. @@ -32,8 +34,8 @@ cards). - Navi's glowing orb should draw again on AMD GPUs, and the black and white blocks on Navi and Link on Radeon RX 5000 and 6000 cards should be gone: on every GPU but NVIDIA's, the game's shaders now keep the NaN and infinity results they rely on. Tell us if Navi is still missing her light on your AMD GPU. -- The device-lost crash at area loads on GeForce RTX 4090, 5090 and 5070 Ti cards: a released texture could be read - after it was freed. +- The device-lost crash at area loads on GeForce RTX cards (seen on the 4090, 5090, 5080 and 5070 Ti), most often when + the system's memory ran low: a released texture could be read after it was freed. - A crash at start with code 71 when RivaTuner Statistics Server runs. - Long sessions running out of memory: idle textures are now freed when the system's memory runs low too, not only the video memory.