Skip to content

v0.7.9.2

Latest

Choose a tag to compare

@github-actions github-actions released this 19 Nov 03:29

What's new

The fastest ReLink so far: up to +31 % frames a second, around +20 % in most places. Lost Woods 68–72 → 85–86, Kokiri Forest 79–82 → 99–101, Hyrule Field 77–81 → 95–99, Forest Temple 80 → 105, on our PC (Ryzen 5 5500, RTX 3060 Ti). There is no setting to change: it is on after the update.

With it: a new look for the menu, the launcher and the loading screen, shorter installs, and the fixes for what you reported on 0.7.9.1.

Next is hotfix 3 (0.7.9.3), and it will be the one with the most bug fixes: this version went to speed and to the reports with a clear cause; the next one goes to the bugs that are still open. See "What's coming" at the end.

Before you update: this version builds the whole game code again and prepares the shaders again, one time. Count the time of a first install. Two reasons: the code is now compiled in smaller parts (that is what makes installs shorter from now on), and the shader translation changed for cards without mesh shaders.

Every figure below is from our PC (Ryzen 5 5500, RTX 3060 Ti, 16 GB) unless said otherwise.

Faster: +7 to +31 % frames a second, most places around +20 %

Two changes that only show together.

1. The game no longer waits for the graphics card to finish a whole frame before starting the next one. At the start of each frame the game was held until the card had finished the frame before. It was held because it reads the picture's exposure back from the card every frame: read too early, the exposure jumped, which were the white flashes of older versions, and every earlier attempt to shorten that wait brought them back. Now the exposure sums are cleared on the card itself, the game is handed the last finished measure when no new one has arrived, and it waits only for the part of the frame that sends its own data back.

2. The game's hot code computes its floating point on the processor's own instructions. The translated code kept ARM's results bit for bit by going through checks on every operation. It now computes natively and takes the exact path only where the two could differ. Checked out of the game on 175 million cases: no difference.

Standing still, 75 % render resolution, frame rate unlocked, two alternated runs a side (0.7.9.1 → 0.7.9.2):

Place Before After
Lost Woods 68–72 85–86
Market 64–65 76–79
Kokiri Forest 79–82 99–101
Hyrule Field 77–81 95–99
Kakariko 70 83
Hyrule Castle 58 65–68
Zora's Fountain 59–60 64–67
Death Mountain Trail 91–93 113
Goron City 88 101–106
Zora's River 67 80–84
Zora's Domain 74–75 88–89
Inside the Deku Tree 77 95–96
Dodongo's Cavern 90 109–114
Inside Jabu-Jabu 77–78 93–96
Forest Temple 80 105–106

What else we measured:

  • The first change alone, same build with it on and off: Lost Woods 73–74 → 84–85, Market 67–68 → 76–79, Kokiri 80–81 → 98–99.
  • At night (Hyrule Field, 22:00): +15 %, with the same picture and the same exposure behaviour as before.
  • As adult Link: +10 % in Hyrule Field, +12 % at Gerudo Fortress, nothing in the Water Temple.
  • On fewer cores (the game held to 4 of our 6): Lost Woods 58 → 78, Market 54 → 63, Kokiri 80 → 97.
  • A 22-minute run through 24 places in a row on the final build: no incident.
  • The picture detectors we use against flashes (exposure steps, flicker, black frames, white frames) find the same as before on our camera test, at night, and on the title's sequence.

What we could not check: the new frame pacing was measured and watched on an NVIDIA card only. It is on for every card. If the picture's brightness flickers or pulses on your AMD or Intel card, put this line in a file relink_env.txt beside relink-game.exe, and tell us in an issue:

RX_VK_FAST_SYNC=0

Cutscenes in play and sessions of more than half an hour were not checked either.

A new look, by RootChad

Everything around the game is redrawn in one style, a cartridge: a grey shell, a cream label, a colour strip per section, round corners, and the Rubik typeface.

The Insert menu

  • The rows sit under small headings (Display, Upscaling, Smoothness, Advanced; Sound, Items, Keyboard, More; Pad, Mouse, Camera, Motion), with switches, chips, sliders and arrows. What a row does is in a box of fixed height under the rows, so nothing moves when you select one.
  • Cheats, Teleport, Inventory, Travel and Controls are redrawn the same way. In Travel a click selects a place; a second click, or Go there, travels.
  • The mouse: the row under the cursor is selected, the wheel scrolls the rows and stops at the ends (it no longer changes values), and the scroll bar can be dragged.
  • A V-Sync row (Smoothness), applied at once: see the fixes below.
  • The Cheats row is now shown by default. HOS_OOT_CHEATS=0 in relink_env.txt hides it.

The loading screen

  • The ReLink staff fills with gold as the shaders are prepared, with a note playing on it, and it stays alive when the percentage does not move.
  • The ending is played in full before the game starts: the gold finishes the staff, the staff closes into the logo, the logo pulses.

The launcher

  • Home: Play in the sky, and four cards (how it looks, how it moves, Mods, release notes), each opening its page.
  • A Mods page: one row per mod with a switch. Turning a mod off renames its folder with a leading -. It also lists the code patches the last build left without effect, with the build's reasons, and offers Build again when the code patches changed.
  • One side for every screen: Home, Options and Mods, a state card with the version, the update and the way through an install (your copy → build → shaders → play), and icons for the game folder, help, Discord and reporting a problem.
  • The options are laid out as the in-game menu's, with a V-Sync switch.
  • The "game is ready" screen is gone: after a build you land on Home.

Shorter first installs

  • The package's read stage: about 5 minutes → 9 seconds. Only what the translation needs is read first; the game's files are unpacked while the code is translated and compiled.
  • The compile no longer under-uses PCs with 16 GB: the memory check counted each compiler twice at 4 MB. The cold code is compiled in parts of about 8 MB, a third of the peak memory, so more compilers run at once.
  • The first start prepares shaders on every processor thread but one.
  • A fresh install on our PC: 35:46 → 28:26.

Cards without mesh shaders (GTX 10 series and the like)

The fallback that runs the game's task and mesh shaders as compute shaders now shares one set of buffers instead of one per program, and draws its meshes whole. With the fallback forced on our card, in Kokiri Forest: 43–48 → 60 frames a second, video memory 8080 MB → 5214 MB (#114, #60, #107). We have no such card: please tell us how it goes. Still missing on that path: some big rocks.

Fixes

  • 5 frames a second at the Market on cards with a lot of video memory (#136). When the game tidies its video memory it gives emptied blocks back to the driver, and it did that on the render thread: 5 to 7 ms a block here, about 250 ms on the reporter's RTX 4080 SUPER, 83 times in a row. It is now done on a background thread, and the tidying stops for a long while if one of its steps is still slow. Checked here (the render thread's share of a 12-block tidy: 50 ms → 17 ms); not checked on a card where the call is that slow.
  • Screen tearing (#133). On cards whose driver has no "mailbox" mode (AMD and Intel on Windows) the game shows frames as soon as they are ready, which tears. The new V-Sync row, in the Insert menu and in the launcher, shows each frame in step with the display.
  • The frame rate chosen in the launcher going back to 60 after the game was closed. The game's options save dropped the launcher's line. By RootChad.
  • AMD: the Market's and Kakariko's dogs drawn as flat silhouettes. A pipeline the driver's compiler fails on is now built again without its optimizer. By RootChad, checked on an RX 6600 XT.
  • A crash in AMD's driver on the first frame after the intro (#109). An indirect mesh draw could ask the driver to read more records than had been written. By RootChad. Not confirmed as #109's cause yet: please tell us.
  • An update stopping in the translation step with errors of every kind on PCs short of memory. The workers of the last step are now bounded by free memory, and one that dies no longer stops the update. By RootChad.
  • Long sessions. Two things that grew with the length of a session and slowed the render thread: memory pools the game had given back were walked again and again (with 6000 of them: 3.4 s → 0.008 s over about three minutes), and the table of the game's locks and events read every object each time it grew (62.9 ms → 6.85 ms).
  • Slow PCIe links (an x8 card in a PCIe 3.0 board, a laptop's x4). The link's speed is measured at start; under 9 GB/s the copies back to the game's memory are put off to the end of the frame. +12.9 % at Hyrule Castle, measured with the bus saturated on purpose, not yet on a real slow link.
  • The display stays on while the game's window is the active one, also when the window was already active at start (#65).
  • relink_env.txt: a line starting with RX_VK_GPU_ or RX_VK_GPL no longer prepares every shader again.

Not in this version

  • Water squares and ripples (#84, #78, #48, #120): the cause is still open. A candidate fix removes the stair-step blocks around Link in water but makes white blotches on his legs under water more frequent, so it is not shipped.
  • AMD RX 6000 cards stopping in play (#45, #66, #79, #123, #130): we have no such card. We need runs with the three diagnostic lines asked for in those issues.
  • AMD: a long start at every launch (#131, #111): the driver compiles the start's pipelines again each time. A setting that keeps our own copy on disk exists (RX_VK_LEAN_PIPELINES=0 in relink_env.txt); we are asking players with those cards to try it before it becomes the default there.
  • The rupee counter staying too long above 60 fps (#135), the flickering ring when Link becomes an adult (#122): noted, cause not found yet.
  • HUD labels and dialogue frames after an area change (#69), striped ground after minutes (#47, #72): fixes written, not verified yet.

Known issues (v0.7.9.2)

  • The new frame pacing has not been tried on AMD and Intel cards: see the line above to turn it off.
  • The Water Temple (adult) does not gain from it.
  • Cards without mesh shaders: some big rocks are missing.

What's coming: hotfix 3 (0.7.9.3), the one with the most bug fixes

No date. The next release is for bugs first, and it is planned as the one that fixes the most of them. What it is gathering:

  • Water: the black squares on Link's shadow in and near water, and the ripples (#84, #78, #48, #120).
  • AMD: the RX 6000 cards stopping in play (#45, #66, #79, #123, #130) and the long start at every launch (#131, #111). Both need players with those cards: the runs asked for in those issues decide what ships.
  • Picture: HUD labels and dialogue frames after an area change (#69), striped ground after minutes (#47, #72), the flickering ring when Link becomes an adult (#122), the missing rocks on cards without mesh shaders.
  • Above 60 fps: the rupee counter staying on screen too long (#135).
  • Crashes waiting for a log: loading a save (#118), after the intro (#109, #105) if 0.7.9.2 does not settle them.

Noted for later, not started: a toggle for running (#119), .nx packages (#128), lighter grass shaders for more frames in open areas.

If a bug of yours is not in this list, open an issue with relink_log.txt from the game folder: a log is what gets a bug into a hotfix.

Thanks to RootChad for the new look and four of the fixes, and to everyone who attached a log: each fix above started from one.