Repository navigation
v0.7.8
What's new
Item wheel, with Cycle items (Gameplay tab of the Insert menu, both off by default). Contributed by @samaBR85 (#57), thank you. With Item wheel on, holding R or L shows your items as a wheel instead of the game's row: point at one with either stick and let go to put it on ZR; D-pad Left/Right (or ZL/ZR) turn the pages; Y picks an item up and puts it down in another slot. The icons, names and sounds are the game's own, made from your copy when the game is built. Cycle items changes the item on ZR with a tap of R or L. Checked here with a player's save: the wheel opens, an item is chosen and equipped, one is moved to another slot. Not tried by us: the mouse on the wheel, and Linux.
Black screen right after the intro of a new game (#21, RTX 4070): the game renders into two compressed "noise" images there, which that driver did not survive. A plain image now stands in for them and is copied back around the pass. Here the stand-in is active and the picture is unchanged; we have no card that showed the black screen, so please confirm in #21. If you added RX_VK_SKIP_PROG=53509044401d78d2 to relink_env.txt, remove it.
A first start that prepares more before the title. A new install now also builds the game's compute pipelines before the title (about 5,000 here) instead of during your first minutes of play, and the start-up percentage is one count that no longer goes back to 0. The old pipeline cache file (mkw_vk_pipelines.bin, 800 MB and more), which nothing has read since 0.7.6, is deleted at the first start.
Quit game (#32): a row in the Insert menu's Gameplay tab. It asks first, saves your options and closes the game as closing the window does. Closing the window now also waits for a save that is being written.
The screen no longer turns off while you play with a controller (#65): Windows does not count a controller as activity; the display is now kept on while the game's window is the active one.
Unlocked frame rate on a second monitor (#16): the limit is now the refresh rate of the display the game's window is on, not of the primary display, and relink_log.txt says the limit. HOS_FPS_MAX=<n> in relink_env.txt still overrides it.
Striped or blank ground after a while (#47, #59): a texture the game had drawn itself could be thrown away when video memory was short, and came back empty. Such textures are now kept. In a test here with video memory forced very low, 15 such textures were lost before and none after; one very large texture can still be lost in that test. We never saw the stripes themselves here, so please tell us in #47 whether Dodongo's Cavern still does it.
Mouse camera, Native mode (#13, #2): the camera no longer stops following in the middle of a motion, and short flicks while aiming reach the game. Checked here with a simulated mouse only.
Cards without mesh shaders (GTX 10 series: #60, #70, #71): in one report the renderer stopped because a build the driver refused was tried again on every draw. It is tried once now, and the log says why it failed. These cards are still below what ReLink supports and we have none to test on: this removes one cause of the black screen, it does not promise a picture. A new log from 0.7.8 in #60 would help.
Clearer messages:
- A
romfsfolder that is not the supported game's, or is another version's, is refused with a plain message in the launcher and the builder, and the game says so in a box (#26). - A graphics driver that crashes while reading a shader gives a message and a log line instead of the game closing silently (#43).
- The start of
relink_log.txtsays which "device lost" diagnostics your driver has (#62, #66).
Launcher: a Discord link beside Help. The project's server: https://discord.gg/RFNUtCQk8j
This update translates the game's code again: expect the rebuild to take a few more minutes than usual, and about 21 MB more in the game folder (the wheel's icons). Your saves, settings and prepared shaders are kept.
Known issues (v0.7.8)
- AMD RX 6600 (#66, #45) and Intel Arc B580 (#62): the graphics card stops ("device lost"). Not fixed; no cause found yet. On AMD, please try
RX_VK_CAPTURE_WAIT_ADAPT=0inrelink_env.txtand tell us. - Dark blocks on broken pot shards, blocky shadows on wet ground (#48): being looked at; two test switches are described in #48.
- Camera turning into a view not seen yet: a second or two of long frames (#29, #54).
- Game speed above 60 fps (#16, #67): some players report the game running too fast when unlocked. Not reproduced here (Link walks the same distance in the same time at 60 and at 80 fps); details asked in #67.
- Intel Arc 140V (#49): missing and flashing textures.
- 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: the card is full in Hyrule Castle at 3840x2160 and 100 %; use 67 % or 75 % render resolution.
- Gyro on some Pro-style controllers: left/right can come out reversed and weak (#8).
- Button remapping and Xbox / PlayStation button pictures (#34, #63, #68): not in this version; next on the list.
Updating
The launcher offers the update. The game is built again (a few more minutes this time, see above); saves, settings and prepared shaders 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.