Skip to content

v0.7.9

Latest

Choose a tag to compare

@github-actions github-actions released this 17 Nov 04:11

What's new

The game no longer runs too fast above 60 fps (#16, #67). With Frames per second on Unlocked, everything in the game went faster the higher the frame rate was: 1.24 times its speed at 75 fps, 1.77 times at 102 fps. The game's own frame-rate controller was overwriting, every frame, the frame rate ReLink gives it, and never let it go above 60. The time step now takes the real frame rate above 60 too. Measured on the game's own clock: 5.04 s of game time in 5.01 s at 123 fps, and Link walks the same distance in 2.5 s at 60 fps and unlocked. Our answer in 0.7.8's notes ("not reproduced") came from a flawed test; thank you to the three players who insisted.

AMD Radeon RX 6000: the start no longer hangs while preparing shaders (#80). Contributed by @RootChad (#85), who has the hang on an RX 6600 XT. On these cards (RX 6600, 6700 XT, 6750 XT in the reports) one pipeline never came back from the driver and the start waited at 79 to 87 % for good. A pipeline that stays in the driver for over a minute is now left behind and named in the log, the start goes on, later starts skip it, and it is built in play when first needed. Checked here by making pipelines hang on purpose (we have no AMD card).

Xbox and PlayStation button prompts (#34, #63, #68). A Button prompts row in the Insert menu's Controls tab: Nintendo, Xbox or PlayStation (applies at the next start). The game's prompts and the four faded letters of the HUD cross then show your pad's own labels, each at the place of the button you press. The ocarina's note buttons are not covered yet. A mod that replaces the game's button font still wins.

Code mods (exefs). Patches of the game's code in mods\<name>\exefs\ are now applied: <build id>.ips (IPS and IPS32) and .pchtxt. ReLink translates the game's code when it builds the game, so after adding, changing or removing one, the launcher's first page offers Build again, and the game says so once at its start. What the last build applied or left out, and why, is in relink_exefs_mods.txt. Not supported: whole replacement modules, and patches of rtld. The README has the details. Checked here with two test patches; no player's mod has been tried yet, so reports are welcome.

GTX 10 series and other cards without mesh shaders: no longer a black screen (#60, #70, #71). Experimental. The game draws grass, foliage and many effects with mesh shaders; on cards without them ReLink runs those programs another way. The shaders that path made were invalid (since 0.6.1): the driver gave up on the first one after a save was loaded and the picture stayed black. That is fixed. What to expect, measured by forcing that path on an RTX 3060 Ti, since we still have no GTX 10 card: a first start that prepares shaders for about 19 minutes, then roughly half the normal frame rate (24 to 36 fps in Kokiri Forest, where the normal path gives 60), and some large rock pieces missing. A relink_log.txt from a real GTX 10 would tell us how it goes there.

30 fps, smooth; Field of view; stick dead zones. Also from @RootChad (#85, #93). In the launcher, Frames per second has a third choice, 30, smooth: each frame is shown for the same number of refreshes and the game keeps its speed (33.3 fps on a 100 Hz display). In the Insert menu: Field of view (Graphics, 70 to 150 %) and Left / Right stick dead zone (Controls, 0 to 50 %, 24 as before).

Travel page. Contributed by @samaBR85 (#58). With the cheats on, the Cheats page has a Travel row: 190 places to go to, each with a picture taken in your own game the first time you stand there.

Black cliffs, blurry or missing rocks: damaged game copies. Some dumps of the game hold texture files whose first kilobytes are zeros; which files differs from one dump to another. The game cannot read them: an area's baked lighting comes out black (a cliff side on Death Mountain Trail), or a model never finishes loading and its rocks are missing. The install now checks every texture and stands in for each damaged one with its nearest intact relative; mods\00-dump-repair\README.txt lists what it found. The real files only come back with a fresh dump. Reproduced here by damaging those files on purpose; if you had these symptoms, please tell us whether they are gone.

F12 saves a screenshot. The game's picture at its output resolution, without the menu or the FPS counter, as a PNG in the game folder's screenshots folder.

Item wheel: the first opening of a session shows the wheel at once instead of the game's row for a moment. Contributed by @samaBR85 (#74).

Low video memory: a texture the game drew itself that has to leave the card is now kept in system memory and put back, instead of coming back empty (from #85). In a test with video memory forced very low: 4 textures read empty before, none after. This is not the striped ground of #47 and #72 (see the known issues).

Messages:

  • The "game files are from another version" box no longer shows for a dump of the updated game that still holds the first version's size table beside the new one (#88). The installer now also refuses, before building anything, a .nup whose game files really are another version's.
  • With DLSS or FSR, textures are sampled sharper (a mip bias that follows the render scale), and ReShade's layer is handled (both from #85).

Thanks also to @biosed for #73 (profile generation on Linux) and #89 (a small saving in the renderer's draw calls).

Known issues (v0.7.9)

  • AMD Radeon RX 6000 in play (#66, #79): the graphics card can still stop ("device lost") after the start, on Windows and on Linux. Not fixed; tests are running with a player in #79.
  • Square blocks around characters on water and ice, and on broken pot shards (#84, #78, #48): reproduced here; the part of the frame that makes them is identified (the game's light list, built on the GPU), the fix is not in this version.
  • Ground and paths turning striped or black in patches after a while (#47, #72): seen by several players, also on cards with plenty of video memory (so not what 0.7.8 fixed), in Dodongo's Cavern, Hyrule Field and Kakariko. Not reproduced here yet and not fixed. One player reports that saving and loading that save in the game clears it.
  • Reported, not reproduced here yet: a crash around Lon Lon Ranch as adult Link, the Market's dogs without textures at night, a menu running above the frame-rate cap, and a black picture during the intro on a ROG Ally. A relink_log.txt from a session where it happens is what helps most.
  • A mod that crashes the game at its start: in the one log we have, the game runs out of memory for Link's model right after reading the mod's model file, and the mod also has code patches that 0.7.8 left out. Try it again on 0.7.9 (with Build again), and send relink_log.txt if it still crashes.
  • Pre-rendered videos can stutter above 60 fps (#67).
  • Camera turning into a view not seen yet: a second or two of long frames (#29, #54).
  • Intel Arc 140V (#49): missing and flashing textures. Intel Arc B580 (#62): the card can stop.
  • FSR tested on NVIDIA only. Short trails with FSR and DLSS on what moves by itself without a skeleton (particles, water, plants in the wind).
  • 4K native on 8 GB cards: use 67 % or 75 % render resolution in Hyrule Castle.
  • Gyro on some Pro-style controllers: left/right can come out reversed and weak (#8).

What's coming

No dates. This is what is being worked on or reviewed now:

  • The square blocks on water, and a faster path for GTX 10 cards. Both need a change in the shader translator, and such a change makes every PC prepare its shaders again at the next start (about as long as a first start). They will ship together, so that it happens once. The GTX 10 part already runs here, forced on an RTX card: 44 to 45 fps in Kokiri Forest in place of 36; its missing rocks are still to find.
  • AMD. Radeon RX 6000 cards that stop in play (#66, #79), and integrated Radeon chips such as the ROG Ally's, for which a contributor's work is under review (#95).
  • Linux and Steam Deck. Still the first priority after the bugs that stop people from playing. Contributors' pull requests for Linux are under review (#38, #77, #82, #83, #86, #91).
  • Shorter installs and updates. A contributor's work on the build's speed is under review (#87).
  • Asked for on the Discord and in the issues, noted, not started: the ocarina's note buttons following Button prompts, a volumetric fog setting, FSR 4, a sprint button, choosing the display the game opens on, an enemy damage setting, and the companion map app.

Updating

The launcher offers the update. The game is built again; saves, settings and mods are kept, and the shaders are not prepared again.

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).