Repository navigation
Releases
Triforce v0.3.6
A big round of fixes from your bug reports, plus DLSS, a new HDR mode and Triforce's own home. Still an early pre-release: please keep reporting what you find, with your triforce_log.txt.
Fixed: graphics
- Pixelated shadows on wet floors and water (Jabu-Jabu, the Water Temple, any lit wet floor). Some shadow samples read a constant where they should have read their shadow map.
- Lights over water each cast their own shadow now, instead of sharing one.
- Pixelated, flickering lights and a banded sky on some PCs.
- Sharpness slider turning the screen black on HDR displays.
- Loading screen and options far too dark with HDR on.
- Triforce crest missing on the shader loading screen.
- AMD: crash on RX 6800 / 6900 / 6950 cards.
- AMD: red flashing at the top of Hyrule Castle and similar spots, and broken water in the Royal Family's Tomb.
- AMD: grass drawn as holes while it loads.
- AMD and Intel: dashed shadow edges and other glitches from three shader bugs.
- Intel: crash logs now say far more, so Arc crashes can be tracked down.
Fixed: performance and stability
- 15 fps on PCs with 16 GB of RAM (reported in Hyrule Field). With memory short the game handed memory back to Windows and asked for it again, in a loop.
- Start screen freezing while shaders are prepared. When the graphics driver fails there, the game now starts itself again instead of hanging.
- Far fewer first-time stutters. Every one of the game's 80 maps was walked to collect shader pipelines: 18,403 are known up front now (12,067 before), and the rest are built in the background while you play until all are done.
- Linux: the game no longer switches off its faster memory handling after a normal exit.
Fixed: game
- Button prompts did nothing since v0.3.4. They work now.
- Debug Inventory now really gives the items.
New
- NVIDIA DLSS and DLAA for RTX cards. Tick NVIDIA DLSS on Setup's build page; it asks you to accept NVIDIA's license and downloads NVIDIA's files (about 60 MB) to your PC.
- Upscale before bloom (Options, Graphics; off by default): DLSS, DLAA and FSR work on the scene before the game's glow and tone mapping.
- RenoDX HDR (Options, Display, with HDR set to Native; off by default): RenoDX's tone mapping and eye adaptation, with its own controls for mid grey, UI brightness, colour space, exposure, highlights, shadows, contrast, saturation and bloom. RenoDX is by Carlos Lopez (clshortfuse), under the MIT license. The build downloads its shaders and their compiler (about 60 MB) to your PC.
- All settings are in the game's own Options screen. The old F1 / Insert menu is gone.
- Setup: a Back button on the build page, and it asks before building a game you already built.
Triforce's new home
https://triforceproject.com has the downloads, the notes of every version and the install steps. From this version on, Setup and the game look for updates there.
Good to know
- The first start after this update prepares shaders again. That happens once.
- Not every fix could be tested on the hardware it is for. We have no AMD or Intel card and no 16 GB PC: the AMD fixes are matched to your reports by their symptoms, and the 16 GB fix was shown to stop the loop, not measured as frames per second. If you reported one of these, please tell us whether it is gone.
- DLSS on a game you already have: update first, then open Build a game folder, tick NVIDIA DLSS, and build again.
- RenoDX HDR needs an HDR display with HDR turned on in Windows.
- Intel Arc: the crash after the intro and the wrong colours are not fixed. The new log lines are there to find them.
- Everything from v0.3.5 is included.
Linux test build
Triforce-v0.3.6-linux-test-x86_64.AppImage is a test build for Linux. It has not been run on a Linux PC by us. It was built and checked automatically (the package builds and a build starts from it), but nobody has yet reported building the game with it or playing it on Linux. Expect problems, and please tell us what happens.
- For x86-64 Linux with glibc 2.35 or newer (Ubuntu 22.04 and later, and most current distributions) and a Vulkan 1.3 graphics card.
- Download it, make it executable (
chmod +x Triforce-v0.3.6-linux-test-x86_64.AppImage) and run it. It opens the builder window: point it at your own copy of the game, pick a folder, and press Build the game (around 45 minutes). Play is in the same window afterwards. - Replaced on 14 November. The first v0.3.6 Linux file had no way to open Triforce's settings: the tabs in the game's Options screen were missing on Linux. This one has them. If you built your game with the first file, download this one, choose your copy of the game in the builder again and build once more.
- If you have an older test build, replace it with this file. Updating from inside the Linux builder is not set up yet.
- New: a game built with this version looks for new versions at triforceproject.com and tells you when there is one. Older Linux builds never did.
- When you report, say your distribution, graphics card and driver, how far it got (builder window, build, first start, in game), and attach the build's output or the game's
triforce_log.txt.
Windows players do not need this file: Triforce Setup ignores it.
Updating
Open Triforce Setup and press Update & merge. Your saves and settings are kept.
Install
- Download
TriforceSetup.exeand run it. No administrator prompt and nothing else to install. - Setup installs itself and downloads the Triforce tools (about 270 MB).
- Point Setup at your own copy of the game (
.nup, orromfs+exefs; program0400486024DEC000, update v131072, builde0f3ccfa), pick a language and a folder, and press Build. The first build takes around 40 minutes. - Press Play. Settings and controls are in the game's Options.
Windows 10 or 11 (64-bit) · a Vulkan 1.3 graphics card (tested on NVIDIA) · 16 GB of RAM · about 60 GB free while building.
Triforce v0.3.5
Two fixes from your bug reports. Still an early pre-release: please keep reporting what you find, with your triforce_log.txt.
Fixed
- Intel Arc: crash a short while into the game (reported on an Arc A750, every session, at the Deku Tree). The game saved its shader cache in the background while new shaders were still being built, and Intel's driver crashed there. On Intel cards the cache is now saved when the game closes instead.
- Long freezes on PCs with 16 GB of RAM (reported as a 40-second freeze after a warp). The game kept every prepared shader pipeline in memory, about 2 to 3 GB, and Windows ran out. On PCs with less than 20 GB of RAM those are now loaded when first needed. In exchange you may see a handful of very short hitches (10-65 ms) when entering an area.
Good to know
- This update is quick: about 3 to 5 minutes, and your prepared shaders are kept.
- Neither fix could be tested on the hardware it is for (we have no Intel card and no 16 GB PC). If you reported one of these, please tell us whether it is gone.
- Intel Arc: the picture can still show wrong colours. That is a separate problem and is not fixed here.
- AMD cards: a long pause the first time something new appears (for example calling Epona) is known. The card builds new shaders for it, and the game waits. It happens once per new thing; more of it will be prepared at startup in a coming update.
- If you play with 16 GB of RAM, closing browsers and other heavy programs before playing still helps.
- Everything from v0.3.4 is included (the fight slowdown fix and the controller fix).
Linux test build
Triforce-v0.3.5-linux-test-x86_64.AppImage is a test build for Linux. It has not been run on a Linux PC by us. It was built and checked automatically (the package builds and a build starts from it), but nobody has yet reported building the game with it or playing it on Linux. Expect problems, and please tell us what happens.
- For x86-64 Linux with glibc 2.35 or newer (Ubuntu 22.04 and later, and most current distributions) and a Vulkan 1.3 graphics card.
- Download it, make it executable (
chmod +x Triforce-v0.3.5-linux-test-x86_64.AppImage) and run it. It opens the builder window: point it at your own copy of the game, pick a folder, and press Build the game (around 45 minutes). Play is in the same window afterwards. - If you have the v0.3.4 test build, replace it with this file. Updating from inside the Linux builder is not set up yet, and the older file will ask for an update it cannot get.
- When you report, say your distribution, graphics card and driver, how far it got (builder window, build, first start, in game), and attach the build's output or the game's
triforce_log.txt.
Windows players do not need this file: Triforce Setup ignores it.
Updating
Open Triforce Setup and press Update & merge. Your saves and settings are kept.
Install
- Download
TriforceSetup.exeand run it. No administrator prompt and nothing else to install. - Setup installs itself and downloads the Triforce tools (about 250 MB).
- Point Setup at your own copy of the game (
.nup, orromfs+exefs; program0400486024DEC000, update v131072, builde0f3ccfa), pick a language and a folder, and press Build. The first build takes around 40 minutes. - Press Play. Settings and controls are in the game's Options.
Windows 10 or 11 (64-bit) · a Vulkan 1.3 graphics card (tested on NVIDIA) · 16 GB of RAM · about 60 GB free while building.
Bring your own game. This release contains no game data and no keys. Never share the files a build makes.
Triforce v0.3.4
Two fixes for problems you could hit in normal play. Still an early pre-release: please keep reporting what you find, with your triforce_log.txt.
Fixed
- Slowdown in fights, and fps getting lower the longer you played. After a quiet moment the renderer could decide to read one of the game's buffers from system memory instead of video memory. From then on the frame rate fell to 18-45 fps with constant hitches, worst in fights, until the game was restarted. That buffer now goes back into video memory by itself, and large buffers are no longer tested that way at all. This had been there since v0.3.0.
- Controller: only the triggers worked until the game was restarted. Buttons and sticks stopped arriving shortly after the game started when the controller was already switched on. Seen with an Xbox Series controller on the Xbox Wireless Adapter; other controllers read the same way were at risk too. Buttons and sticks now arrive.
Also in this release
- If a controller's buttons ever stop arriving again,
triforce_log.txtnow says so in one line ("button and stick input is not arriving"), which makes a report much easier to act on. - A first Linux test build is attached (see below).
Linux test build
Triforce-v0.3.4-linux-test-x86_64.AppImage is a first Linux build for people who want to help test. It has not been run on a Linux PC by us. It was built and checked automatically (the package builds and a build starts from it), but nobody has yet built the game with it or played it on Linux. Expect problems, and please tell us what happens.
- For x86-64 Linux with glibc 2.35 or newer (Ubuntu 22.04 and later, and most current distributions) and a Vulkan 1.3 graphics card.
- Download it, make it executable (
chmod +x Triforce-v0.3.4-linux-test-x86_64.AppImage) and run it. It opens the builder window: point it at your own copy of the game, pick a folder, and press Build the game (around 45 minutes). Play is in the same window afterwards. - Updating from inside the Linux builder is not set up yet: for a newer test build, download the new file.
- When you report, say your distribution, graphics card and driver, how far it got (builder window, build, first start, in game), and attach the build's output or the game's
triforce_log.txt.
Windows players do not need this file: Triforce Setup ignores it.
Good to know
- This update is quick: about 3 to 5 minutes, and your prepared shaders are kept.
- Both fixes were played on one PC (RTX 4070 SUPER, 2560 x 1440, Xbox Series controller): the fight slowdown fix was seen doing its job in a session, and the controller worked through a 26-minute session started with the controller on.
- If the game still slows down after a long session, check how much memory your other programs use: when Windows runs short of memory the game gives some back and stutters. Closing browsers and other heavy programs before playing helps on 16 GB and 32 GB PCs alike.
- Cards with 8 GB or less still drop frames in busy areas when the game's textures do not fit in video memory. That is unchanged in this release.
Updating
Open Triforce Setup and press Update & merge. Your saves and settings are kept.
Install
- Download
TriforceSetup.exeand run it. No administrator prompt and nothing else to install. - Setup installs itself and downloads the Triforce tools (about 250 MB).
- Point Setup at your own copy of the game (
.nup, orromfs+exefs; program0400486024DEC000, update v131072, builde0f3ccfa), pick a language and a folder, and press Build. The first build takes around 40 minutes. - Press Play. Settings and controls are in the game's Options.
Windows 10 or 11 (64-bit) · a Vulkan 1.3 graphics card (tested on NVIDIA) · 16 GB of RAM · about 60 GB free while building.
Bring your own game. This release contains no game data and no keys. Never share the files a build makes.
Triforce v0.3.3
Smoother travel between areas, and a batch of fixes from the Hookshot project. Still an early pre-release: please keep reporting what you find, with your triforce_log.txt.
Smoother when the world loads
- Arriving in a new area stalls less. The textures of the area you left are let go before the new area's come in, so video memory no longer runs over for a few seconds at each arrival (on our test card the peak went from about 100% of what the driver allows to 85-88%). This part is active on cards with more than 8 GB.
- Fewer short pauses while the world streams in on NVIDIA cards: memory the game hands to the graphics card for the first time is now prepared on a background thread instead of in the middle of a frame.
- Memory the renderer is about to need is made ahead of time on another thread, which removes a class of 20-60 ms stalls (also on cards with more than 8 GB).
Fixed
- Bosses and new enemies drawn all blue in their first cutscene.
- Cyan patches for a few seconds after pausing with the game in the background, or after reloading a save.
- Textures in view thrown out and loaded again when turning the camera on cards whose video memory is nearly full.
- The game's clock running slightly fast when frame times were uneven.
- Sound staying silent after a headset or audio device went away: it comes back on Windows' default device.
- A rare crash source when the game lists the save folder, and draws that write data are no longer skipped while their shader compiles.
Experimental: a little more fps
A "recorder thread" moves part of the renderer's work off the frame's critical thread. In our tests it gave about 3% more fps in most places and up to 14% in busy ones like the Market, with no flicker. It is off by default because it has only been played briefly. To try it, add the line RX_VK_RECORDER=thread to triforce_env.txt in your game folder (create the file if it is not there) and tell us how it goes; remove the line to turn it off.
Good to know
- This update is quick: about 3 to 5 minutes, and your prepared shaders are kept.
- Cards with 8 GB or less are not helped much by this release. When the game's textures do not fit in video memory the frame rate still drops in busy areas; that is the next thing we are working on.
- Several of the fixes above (blue bosses, cyan after a pause, the audio device) were checked by test and in the lab, not yet seen fixed in play by us.
- Measured and played on one PC (RTX 4070 SUPER, 2560 x 1440, cap 120).
Updating
Open Triforce Setup and press Update & merge. Your saves and settings are kept.
Install
- Download
TriforceSetup.exeand run it. No administrator prompt and nothing else to install. - Setup installs itself and downloads the Triforce tools (about 250 MB).
- Point Setup at your own copy of the game (
.nup, orromfs+exefs; program0400486024DEC000, update v131072, builde0f3ccfa), pick a language and a folder, and press Build. The first build takes around 40 minutes. - Press Play. Settings and controls are in the game's Options.
Windows 10 or 11 (64-bit) · a Vulkan 1.3 graphics card (tested on NVIDIA) · 16 GB of RAM · about 60 GB free while building.
Bring your own game. This release contains no game data and no keys. Never share the files a build makes.
Triforce v0.3.2
Fixes for playing above 60 fps, and a first fix for the RX 5500 / 5600 / 5700 XT family. Still an early pre-release: please keep reporting what you find, with your triforce_log.txt.
Fixed: playing with the Frame rate cap above 60
Above a cap of 60 the game got a fraction of a frame as its time step, and several of its counters cut that to zero. With the cap at 90, 120 or more:
- Rupees and other pick-ups: the counter above Link crawled or stood still, stayed on screen, and its sound stuttered. It counts and fades normally again.
- Water ripples ran in slow motion.
- Sounds, then the music, could stop after a few loading zones.
- Moving platforms could slide out from under Link.
- The time of day ran slow or stood still.
- Cutscene cues drifted from their movie.
RX 5500 XT / 5600 XT / 5700 XT: a first fix for flashing foliage
A report from an RX 5700 XT showed hedges and grass flashing in a flat colour. These cards run shaders in groups of 64 where the game's code expects 32; this release carries the Hookshot project's fix for that (Bruno Baccari). We have no card of this family to test on: if you have one, please tell us whether the flashing is gone.
Good to know
- This update rebuilds the game itself, not only the renderer, so it takes longer than the last one.
- Shaders are prepared once more on the first start after it.
- Measured and played on one PC (RTX 4070 SUPER, 2560 x 1440, cap 120).
Updating
Open Triforce Setup and press Update & merge. Your saves and settings are kept.
Install
- Download
TriforceSetup.exeand run it. No administrator prompt and nothing else to install. - Setup installs itself and downloads the Triforce tools (about 250 MB).
- Point Setup at your own copy of the game (
.nup, orromfs+exefs; program0400486024DEC000, update v131072, builde0f3ccfa), pick a language and a folder, and press Build. The first build takes around 40 minutes. - Press Play. Settings and controls are in the game's Options.
Windows 10 or 11 (64-bit) · a Vulkan 1.3 graphics card (tested on NVIDIA) · 16 GB of RAM · about 60 GB free while building.
Bring your own game. This release contains no game data and no keys. Never share the files a build makes.
Triforce v0.3.1
A stutter fix on top of v0.3.0. Still an early pre-release: please keep reporting what you find, with your triforce_log.txt.
Fixed
- Bursts of stutter while moving between areas. While Link moves, the game keeps making its temporary render targets at new sizes. The ones it was done with stayed in video memory for up to 13 frames before being reclaimed; when video memory was nearly full they piled up and each new one waited on the graphics driver, 110-170 ms at a time (ten such frames in a row in one session). They are now reclaimed on the next frame.
In our test, running across Hyrule Field with video memory full: frames over 40 ms went from 13-31 to 1-7, and the longest wait for a new render target from 139-165 ms to 3-37 ms. - A new low-memory rule from v0.3.0 was too eager on PCs with more than 16 GB of RAM, and caused short pauses of its own. It now only acts when less than 1.5 GB of RAM is free.
Still there
- Short single hitches (about 30 ms) when new parts of the world stream in, and a longer one on arriving in a new area.
Good to know
- Your prepared shaders are kept; this update only changes the renderer.
- Measured on one PC (RTX 4070 SUPER, 2560 x 1440). AMD and Intel cards are untested: tell us how it runs.
Updating
Open Triforce Setup and press Update & merge. Your saves and settings are kept.
Install
- Download
TriforceSetup.exeand run it. No administrator prompt and nothing else to install. - Setup installs itself and downloads the Triforce tools (about 250 MB).
- Point Setup at your own copy of the game (
.nup, orromfs+exefs; program0400486024DEC000, update v131072, builde0f3ccfa), pick a language and a folder, and press Build. The first build takes around 40 minutes. - Press Play. Settings and controls are in the game's Options.
Windows 10 or 11 (64-bit) · a Vulkan 1.3 graphics card with mesh shaders (tested on NVIDIA) · 16 GB of RAM · about 60 GB free while building.
Bring your own game. This release contains no game data and no keys. Never share the files a build makes.
Triforce v0.3.0
A performance update: less stutter in new areas, a steadier frame rate on cards short of video memory, and less memory held on 16 GB PCs. Still an early pre-release: please keep reporting what you find, with your triforce_log.txt.
Faster and smoother
- Less stutter the first time you enter an area. The tools now carry a list of about 12,000 pipelines from every map and dungeon, as child and adult, and the game builds them before the title screen instead of when they are first drawn. On our test tour of five areas the game built none during play (1,717 before).
- Steadier frame rate when video memory is tight. The game's copies of its own memory on the graphics card now take a third of the space (about 1 GB instead of 3 GB). At the Market after a tour of ten areas, on a 12 GB card: 53 -> 57 fps; held to an 8 GB card's allowance: 41 -> 57 fps.
- 16 GB PCs: memory the graphics driver pins for the game is given back when Windows runs short of RAM (about 4 GB less after a long tour in our test).
- Video memory is tidied up while you play on NVIDIA cards, so the frame rate no longer sinks over a long session.
Fixed
- A texture that came up blank on some water and fog effects (seen at Zora's River).
- A new pipeline list was only used by a brand new install; an updated game now uses it too.
Good to know
- The first start after this update takes longer, once: the game builds the listed pipelines before the title screen. Your prepared shaders are kept.
- AMD and Intel cards: the new memory handling starts on trial there and switches itself off if the game crashes or the graphics device is lost during the trial. We could only test on NVIDIA; tell us how it runs.
- Measured on one PC (RTX 4070 SUPER, 2560 x 1440). Your numbers will differ.
Updating
Open Triforce Setup and press Update & merge. Your saves and settings are kept.
Install
- Download
TriforceSetup.exeand run it. No administrator prompt and nothing else to install. - Setup installs itself and downloads the Triforce tools (about 250 MB).
- Point Setup at your own copy of the game (
.nup, orromfs+exefs; program0400486024DEC000, update v131072, builde0f3ccfa), pick a language and a folder, and press Build. The first build takes around 40 minutes. - Press Play. Settings and controls are in the game's Options.
Windows 10 or 11 (64-bit) · a Vulkan 1.3 graphics card with mesh shaders (tested on NVIDIA) · 16 GB of RAM · about 60 GB free while building.
Bring your own game. This release contains no game data and no keys. Never share the files a build makes.
Triforce v0.2.0
Updating
Triforce v0.2.0 comes from a new home, github.com/ruckus7382sfgsgdf/CBeta0.2. Older Setups look for updates at the old address and will not find this one: download TriforceSetup.exe below and run it, then press Update & merge. Your saves are kept.
Install
- Download
TriforceSetup.exeand run it. No administrator prompt and nothing else to install. - Setup installs itself and downloads the Triforce tools (about 250 MB).
- Point Setup at your own copy of the game (
.nup, orromfs+exefs; program0400486024DEC000, update v131072, builde0f3ccfa), pick a language and a folder, and press Build. The first build takes around 40 minutes. - Press Play. Settings and controls are in the game's Options.
Windows 10 or 11 (64-bit) · a Vulkan 1.3 graphics card with mesh shaders (tested on NVIDIA) · 16 GB of RAM · about 60 GB free while building.
Bring your own game. This release contains no game data and no keys. Never share the files a build makes.