A fix release for *The Legend of Zelda: Ocarina of Time* for Nintendo Switch 2 (game version 1.1.1): crash and memory fixes, a higher frame rate, Navi's light on AMD GPUs, and updates that keep your compiled game and shaders. **No game files are included**: the setup builds the game on your PC from your own dump. ## Install or update - **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. - **AMD and Intel GPUs:** the game's shaders change for your GPU in this release (see Fixed), so the graphics driver builds its pipelines again on the first start and on the first visit to each area. **Requirements:** Windows 10 or 11; an x86-64 CPU with SSE4.2; 16 GB of RAM; about 30 GB free for the game and 1.5 GB for the launcher; a GPU with Vulkan 1.3, `VK_EXT_external_memory_host` and `VK_EXT_mesh_shader` (current NVIDIA and AMD cards). ## New - Updates download in the background, even while you play, and install when the game is not running: when the launcher starts or right after the game exits. Turn off *Install Updates Automatically* in the launcher's Settings to install them yourself from the Updates row. - Later updates keep the compiled game and the prepared shaders, so they take minutes instead of a full build. - *Rebuild the Game* compiles the game for your current processor. - DLSS Frame Generation at 2x, 3x or 4x: the *DLSS multiplier* row under Frame generation in the settings menu (`framegen_multiplier`). 3x and 4x need a GeForce RTX 50 GPU and are not yet tested in play. The frame limit now counts the frames on screen: with 2x a limit of 60 shows 60 frames a second, not 120. With no limit chosen, frame generation now uses the display's refresh rate, so on a 165 Hz monitor 4x draws about 41 frames a second and shows 165. RivaTuner Statistics Server stays out of the frame limit while DLSS Frame Generation runs. ## Fixed - A higher frame rate: far less copying into the game's video memory each frame, the GPU starts its work earlier, and render target images are reused. - 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 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. - A crash when Frame generation was switched from NVIDIA DLSS to AMD FSR 3.1 in the menu: that change now takes effect at the next start, as the menu says. - A crash in Intel's Windows driver while the pipeline cache was saved during play. - Long sessions running out of memory: idle textures are now freed when the system's memory runs low too, not only the video memory. - Shader preparation no longer crashes the RADV driver (AMD GPUs on Linux) on a texture size query. - Things that moved no longer leave a trail when neither DLSS nor FSR 3.1 is on. - FSR 3.1 no longer turns itself off for the rest of the session once the render scale has been changed a few times in the menu. - With frame generation on, the mouse turned the camera as fast as if the game drew every frame on screen: twice as fast with FSR 3.1 frame generation. - The game's own Restart no longer brings the launcher back over the game, where Play could start a second copy. - A cut connection while the launcher reads a small file, such as the package index of *Gather Build Tools*, is tried again instead of failing the install. - After a crash, the game's log ends with the exit code and what it means, also when the game was ended before it could write a line itself, and the crash report stays in place when a driver or overlay installs its own. ## Known issues - The first visit to an area after an install can pause while the graphics driver builds what it has not seen. - Machines with 16 GB of RAM can run out of system memory in Hyrule Field. - Integrated AMD GPUs can fail at the title screen (their host memory heap is too small for the game's memory). - Opening the game's settings menu can crash on some AMD Radeon GPUs. - A rare crash in the game's particle code. ## For builders - With lld, `tools/make_game.py` links the game's manifest and icon itself instead of through windres, so a build or user folder whose name holds characters outside Windows' code page no longer fails the Compile step. - Release and build kit scripts download the pinned Streamline runtime for DLSS Frame Generation themselves (`tools/streamline_pin.py`), and the build kit can carry DLSS Frame Generation too. - `NX2NAVI_PROFILE_SLOW` writes a profile of every slow frame, and `mem_census` also reports the memory of each of the game's address regions. ## Thanks Pull requests in this release came from epicmeme546, itaskaev2, mitch030504 and twisted89. Report problems as issues, with the game's log (`logs\nx2navi.log` in the game folder) and what you were doing. NX2navi is an independent, non-commercial fan project, not affiliated with or endorsed by Nintendo. *The Legend of Zelda*, *Ocarina of Time* and *Nintendo Switch* are trademarks of Nintendo.