Skip to content

v0.7.9.1

Latest

Choose a tag to compare

@github-actions github-actions released this 17 Nov 17:49

What's new

A hotfix of 0.7.9: crash and rendering fixes, faster updates, HDR. The first start after this update prepares the shaders again (one time, like a first start: 10 to 15 minutes), because of the AMD fix below.

AMD Radeon: the dogs drawn without textures. Thank you to Artspear for the logs. The game's shaders are written for groups of 32 threads; AMD's RX 6000 and newer cards can only be told 32 for compute work, and run the drawing shaders 64 wide. The shader that draws the Market's and Kakariko's dogs exchanges values between threads, which went wrong for half of each group. Such cards now get shaders translated for groups wider than 32. We have no AMD card: please tell us whether the dogs (and anything else that looked wrong only on AMD) are right now. NVIDIA cards get the same shaders as before, but prepare them again too.

Lon Lon Ranch: the crash at the end of the race is fixed. Thank you to kalm for testing without mods and sending a save. The renderer kept a small view on a memory buffer the game had just replaced, and the graphics driver read the old, freed one; the game rearranges that memory right where the race ends. Checked here on that save around the ranch with DLAA (nine such rearrangements, no crash); the race itself was not played to the finish line here, so please tell us if it holds.

Striped ground (#47, #72): a likely cause fixed. Thank you to Flix for a route that shows it every time after a fresh start (the Fire Temple's pillar room) and a video of it. When a shader was not ready yet, ReLink left that drawing out of the frame, which is harmless for the scene, drawn again in the next frame; but the game draws some things once into a picture it keeps (pieces of the ground's detail, decals, cached shadows), and those stayed wrong until the area was loaded again. They now wait for their shader. This could not be seen here (on our PC those shaders are always ready in time), so it is not confirmed yet; the log now names any drawing still left out, which will tell.

Stutters when Windows runs short of memory (#33). With NVIDIA's driver every byte of video memory also counts against what Windows can hand out (RAM plus the page file). On PCs whose page file Windows grows, ReLink kept 2 GB of that free and, below it, kept dropping and reloading the same textures: up to 444 every 10 seconds and 100-150 ms frames in one report, while Windows grew the page file anyway. It now keeps 512 MB where the page file can grow (as it already did on AMD integrated GPUs), and a page file sized by hand counts up to its maximum.

HDR. A HDR row in the Insert menu's Graphics tab (applies at the next start): on an HDR display the game draws its own HDR picture (the console's, with its brightness settings) and ReLink sends it to Windows as HDR10. Peak brightness is read from Windows. Works with RenoDX. Checked through the whole chain on an SDR display (the HDR picture and screenshots are right); we have no HDR display, so reports are welcome.

Keys: the Insert menu's key, the screenshot key (F12) and the fullscreen key (F11) can be changed in the Controls tab (F1 to F12, Insert, Pause, Scroll Lock).

Faster updates. The game's code is translated on every core on Windows too (2.5 minutes in place of 3.5 to 5 on our 12-thread CPU, the same result byte for byte), and the translated code is now kept, compressed (about 130 MB), for the next update: an update that does not change the translator skips it. Measured on a player's setup: such an update took 1 minute 10 here; one that does change it, 3.5 minutes. With @RootChad's work (#87): the first build compiles faster, and an update compiles only what changed.

From contributors:

  • AMD Radeon in play: no more ground missing after a few area changes (@RootChad, #99). The driver refused new memory once a session had kept too much of it, and Hyrule Field's ground disappeared until a restart.
  • AMD integrated GPUs (ROG Ally and the like) (@bubblesnout, #95): no more device lost a few frames after loading a save (the textures are decoded on the CPU there, with ARM's astcenc), no more flashing HUD icons, and no more freezes of a second when a big area's textures load.
  • The Insert menu in a 1280x720 window (#96) and the ocarina's note buttons following Button prompts (@RootChad, #98).
  • Linux and AMD (@biosed): AMD FSR on Linux, and the Low latency row (was NVIDIA Reflex) drives AMD Anti-Lag 2 there (#91); Mesa's submit thread on RADV (#86); the uniform data the GPU reads straight from the game's memory copied with each frame, so the next frame cannot change it under the GPU (#102); switches for testing (#77, #82, #83) and finer draw timing for profiling (#108, off by default); and the build with Clang 23 on Linux (#106). Measured by the author on Linux (BC-250).
  • Launcher: Game tab, Shaders, Prepare again (@RootChad, #100): deletes the prepared shaders so the next start prepares them again (10 to 15 minutes), for objects drawn white after a start that crashed while preparing.
  • Volume (@RootChad, #103): a row in the Insert menu's Gameplay tab sets the game's whole sound (music, effects, voices) from 0% (muted) to 100%, heard at once and kept with your settings.

For the logs: a scene load that searches for the same thing millions of times (a Market that never finishes loading) now names what it looks for.

Known issues (v0.7.9.1)

  • Striped ground (#47, #72): see above; please send relink_log.txt if you still see it.
  • AMD Radeon RX 6000 in play (#66, #79): the graphics card can still stop after the start.
  • Square blocks around characters on water and ice (#84, #78, #48): identified, fix in the next shader preparation.
  • Memory: on 16 GB PCs, the game's memory (about 12 GB) plus what video memory counts (5 to 7 GB) needs a page file Windows can grow; with a small fixed page file, long sessions slow down.
  • The rest of 0.7.9's list still applies.

What's coming

This hotfix takes the crashes and the fixes that were ready. Another update follows soon for the other bugs reported since 0.7.9 (the list above and the open issues): we are on them. No dates.

  • The square blocks on water, and a faster path for GTX 10 cards: both change the shader translator; they will ship together, with one more shader preparation.
  • AMD Radeon RX 6000 that stop in play (#66, #79).
  • Linux and Steam Deck: more from contributors (#38 under review).

Updating

The launcher offers the update. The game is built again (the code is translated once more for this update), and its first start prepares the shaders again; saves, settings and mods are kept.

If something does not work, please open an issue and attach relink_log.txt from the game folder, or come to the Discord (the link is in the README).