Triforce

TRIFORCE

Your game, native on your PC.
No emulator: Triforce builds a real Windows program on your PC, from your own copy of the game, and draws its graphics on Vulkan.

Download Triforce Setup Windows 10 | 11 Vulkan 1.3 No emulator GPL-3.0+

About  ◆  Install  ◆  Playing  ◆  Settings  ◆  Controls  ◆  Saves  ◆  Mods  ◆  How it works  ◆  Credits

## The three pieces **Triforce** is a native PC version of your game. Every piece has one job: to make it look and play on your PC exactly the way it does on the console. | | Piece | What it does | |:-:|---|---| | | **Power** · the recompiler | Turns the game's own ARM64 code into a Windows program ahead of time. No emulation at runtime, no CPU guessing. | | | **Wisdom** · the system | Plays the part of the console's operating system: files, saves, audio, controllers, threads and timing. | | | **Courage** · the renderer | Rebuilds the console's graphics on Vulkan, with the game's own lighting, fog, water and foliage. | What makes the game look right in Triforce: - **Living forest:** trees with full canopies, ferns, grass, drifting leaves and fireflies, all drawn by the game's own GPU culling. - **True light:** ambient light probes keep the hero, signs and plants lit in the shade; the pond's water and the game's own fog are as the console shows them, with no tuned workarounds on top. - **Steady play:** no freeze after loading a save, no exposure flicker, and GPU data that survives memory pools being rebuilt. - **Triforce Setup:** one small download that installs, builds, updates and launches the game, with your settings, controls and saves handled before the game even starts. > [!IMPORTANT] > **Bring your own game.** Triforce contains no game data, no keys and no ready-made executable, and it won't tell you > how to get them. Everything is built **on your PC, from your own copy**, and everything it makes (the program, the > generated code, shader caches and saves) stays yours. Don't share those files.

## Installing Triforce *Every hero starts in the forest.* You download one small program, **Triforce Setup**, and it does the rest: the game itself is assembled on your PC, from your copy, in one guided build. ### Before you start | You need | Details | |---|---| | Windows | 10 or 11, 64-bit. Nothing else to install: Setup runs on what Windows already has | | Graphics card | Vulkan 1.3 with mesh shaders, on an up-to-date driver (tested on NVIDIA) | | Memory | 16 GB of RAM or more (the game uses about 10 GB) | | Disk space | About 2 GB for Setup and its tools, and about 60 GB free while building | | Your game | Program `0400486024DEC000`, update v131072, build `e0f3ccfa`, as a `.nup` or as `romfs` + `exefs` folders. Other versions are refused. | ### Four steps to play **1 · Download.** Get **`TriforceSetup.exe`** from the [newest release](https://triforceproject.com) and run it. **2 · Install.** Choose where Triforce goes (your own user folder by default, so no administrator prompt) and whether you want it on the desktop and in the Start menu. Setup then fetches the Triforce tools (about 250 MB, once). **3 · Forge your game.** Point Setup at your game, either the `.nup` or the `romfs` and `exefs` folders; it checks the version first. Pick a language and a folder for the game, then press **Build**. The first build takes around **40 minutes**, and your PC stays usable the whole time. **4 · Play.** Press **Play**. Settings and controls are in the game's own **Options** screen. From then on, the **Triforce** shortcut on your desktop and in the Start menu opens Setup first: that's where updates and saves live. ### Uninstalling Remove **Triforce** from Windows' *Settings → Apps*. That takes Setup, its tools, its `save-backups` folder and the build's work folder (`%LOCALAPPDATA%\Triforce\build`) away; your game folder and its saves stay until you delete them yourself.

## Every time you play Opening Triforce shows the **Welcome back** screen first: your game, your saves and the newest Triforce side by side. - **A new version is out:** choose **Update & merge** to bring it into your game, or **Not now** to keep playing what you have; you'll be asked again next time. Updating downloads the new release and builds your game folder again from the game files it keeps. Only what changed is compiled again, so it usually takes a few minutes. **Your saves and settings stay.** Setup keeps itself up to date the same way. - **You're up to date:** press **Continue**. - **No internet, or the Triforce site is down:** Setup says so, and you play what you have. Beside **Your game** on that screen are **Mods** (see [Mods](#mods)) and **Add to Steam**. Add to Steam puts the game into your Steam library as a non-Steam game, with Triforce's own crest as its pictures; from there Steam starts the game itself, without Setup. **Close Steam first:** Steam writes its own list of shortcuts when it closes, so Setup changes nothing while Steam runs. Your other shortcuts stay as they are, the file as it was is kept beside the new one (`shortcuts.vdf.triforce-backup`), and the same link takes the game out of Steam again. **Sounds.** Once your game is built, Setup plays two of the game's own menu sounds: the decide sound when you choose a button, a link or a row, and the cancel sound when you go back. They are read from your own game folder each time Setup starts (a mod that replaces one of them is heard here as in the game) and kept in memory only: **no sound comes with Setup**, so before a game is built it is silent. Moving the mouse makes no sound, and Setup stays quiet while the game is running. **Sounds**, at the top of the window beside the minimize button, goes through **Off**, **Low** (the start), **Medium** and **High** at each click. Then come your settings, and **Start game**.

## Settings *Choose your path.* Settings live in the game's own **Options** screen (title screen or pause menu): the tabs Display, Graphics, Audio, Controls and System sit beside the game's own list, and **L** / **R** switch between them. A few apply at the next start; the game asks. They're saved in `triforce_options.ini` beside the game. | Setting | Options | |---|---| | Quality preset | Custom, Minimum (4 GB), Low (6 GB), Balanced (8 GB), High (12 GB), Ultra (16 GB+): one choice that sets resolution, upscaling, frame generation and VRAM limits for your card | | Fullscreen | Off, On | | HDR | Off, Expanded, Native (the game's own HDR), on an HDR display; paper white 80 to 400 nits, peak brightness 400 to 10,000 nits | | RenoDX HDR | Off, On, with HDR Native: RenoDX's tone mapping in place of the game's own (applies at the next start), and its rows. Tonemapper Vanilla, PsychoV35 or RenoDRT; gamma correction Off, 2.2 or BT.1886 (2.4); midgray, UI brightness, color space, exposure, highlights, shadows, contrast, saturation and bloom. With PsychoV35 also match tone slope, tone slope and hue clip; with RenoDRT highlight saturation, blowout, flare, hue correction and colour grading | | Frame generation | Off, Auto, 2x up to 8x; AMD FSR 4 (one frame made by AMD's library between each two of the game's) where your card, driver and build have AMD's FSR 4 frame generation, such as a Radeon RX 9000 | | VSync | On, Off: Off shows each frame at once, with a little less delay and possible tearing; the frame rate stays the cap's | | Frame pacing | Off, On (on by default: each frame is shown at an even interval, for less stutter at up to one frame of delay) | | Game frame rate cap | 30, 40, 45, 60, 90, 120, 144, 165, 240, Monitor's rate (your screen's refresh rate, up to 240). Past 60 is experimental; applies at the next start. Where RivaTuner Statistics Server is installed and running (Windows), the game puts this cap into RivaTuner's profile for `Triforce.exe` and RivaTuner limits the game instead of the game's own wait, once it is seen holding the game to it; with frame generation 2x to 8x or AMD FSR 4 the limit is the cap times the frames shown for each. Closing the game puts the profile back as it was, and after a crash the next start does (`triforce_rtss_profile.txt` beside the game keeps what it held). The game never starts RivaTuner. Changing that profile needs the game run as administrator (RivaTuner keeps its profiles under Program Files); without it a limit you set in RivaTuner yourself, at or under the cap, holds the game alone. With frame generation on Auto or DLSS frame generation, while the window is minimised and during movies (when the limit is the game's) the game limits itself. The overlay's Full view says who limits and why. `HOS_RTSS=0` in `triforce_env.txt` leaves RivaTuner out entirely | | Steady frame rate | Off, Any rate, Refresh steps (applies at the next start). Off: each frame goes out as soon as it is ready under the Game frame rate cap, as always. On, the game is paced to a frame rate your PC holds where you are, never above the cap, and each frame is shown a period after the last: the frames come evenly, for some frame rate given up (on the lab's recorded Market frame times about 74 to 81 fps where it ran at 93 to 95, with the frame-to-frame jitter halved). The rate is measured by letting about 30 frames run unpaced every 12 s or so (and right away where frames run late), and it goes down within a second of a heavier scene and back up within one such probe of a lighter one; loads and single hitches do not move it. Any rate suits a screen with variable refresh (G-SYNC, FreeSync) or VSync off; Refresh steps keeps to whole divisions of the refresh rate (at 240 Hz: 240, 120, 80, 60, 48, 40, 30) for VSync without variable refresh. The overlay's Full view shows the rate it holds. Where RivaTuner or Reflex limits the game, the cap holds as before. `HOS_FPS_STEADY=0`, `1` or `2` in `triforce_env.txt` over the row | | Reflex frame limit | Off, On: with DLSS frame generation, NVIDIA Reflex holds the frame rate cap where each frame starts, in place of the game's own wait, so a frame waits once. Off is the game's own wait, as always. Where RivaTuner limits the game, it does so whatever this row says | | Upscaler | Game, NVIDIA DLSS, NVIDIA DLAA, AMD FSR 3.1, AMD FSR 3.1 Native AA, AMD FSR 4, AMD FSR 4 Native AA: those your card and build can run | | Resolution | Auto (the game's dynamic resolution), 100%, 75%, 67%, 50% | | Anti-aliasing | Game SMAA, Off, FXAA, SMAA Ultra: how the 3D's edges are smoothed with the game's own upscaler. DLSS, DLAA and FSR smooth them themselves, and the row then does not apply | | Upscaling | Off, Catmull-Rom, Lanczos, AMD FSR 1 | | Sharpness | 0–100% | | Texture filtering | Game, 2x, 4x, 8x, 16x anisotropic | | Texture detail | Automatic, Full, Reduced, Low: how large the game's textures are kept in video memory. Automatic goes by your card; applies at the next start | | Fast pipeline link | Off, On (the Debug tab; on by default): new pipelines are first linked from prepared shader libraries, so fewer draws wait for the graphics driver. The first start with it compiles those libraries once; applies at the next start | | Replay helper threads | Automatic, Off, 2 to 8 threads (the Debug tab): more of your processor's cores prepare each frame for the graphics card, where short trials as you play find that faster, or at once where the frame plainly waits for that work (and no trial where it cannot help). Automatic uses none (with helper threads the game could slow down for seconds while moving); with DLSS or FSR on too, for upscaling or frame generation. Choose Off if frames flicker; applies at the next start | | Lazy write-back | Off, On (the Debug tab; on by default, Windows only): what the GPU writes into memory the game shares with it is copied back only when something reads it there, not after every submission. Stays off with an AMD card's driver unless `RX_VK_LAZY_WB=1` is set; applies at the next start | | Start next frame early | Off, On (the Debug tab; on by default; experimental): the game starts its next frame while the graphics card still draws the end of this one (the upscaling and the interface), where that end holds nothing the game reads back; other frames run as before. Applies at the next start (`RX_VK_TAIL_EARLY=1` or `=0` in `triforce_env.txt` over it) | | Opaque textures as BC1 | Off, On (the Debug tab): the game's large textures that have no transparency kept in half the video memory, with the same picture. On by default; applies at the next start | | Game language | The game's 16 languages, as `language.txt` beside the game lists them; applies at the next start | | Game speed | Real time (keeps normal pace), Per frame (slows down below 60 fps) | | Handheld profile | Off, On | | Ultrawide | 16:9 (the game's own), 16:10, 21:9, 32:9: the fixed shapes are for a screen or a window of that shape (a screen of another shape shows black bars); applies at the next start | | FPS counter | Off, On, Full: On is the frame rate in the top right corner; Full shows NX2navi's performance overlay there in its place (under the options while they are open), in the options' look and see-through: the build, the GPU's and the CPU's load and temperature, video memory and memory, the frame rate with its 1% and 0.1% lows, the frame times and their graph, the GPU's and the replay's time and waits per frame, the picture's settings and the GPU's and CPU's names (a "-" where the PC does not say: temperature and power need an NVIDIA or AMD card). It measures only while shown | | Menu sounds | Off, 5% to 100% (80% unless you change it): the game's own interface sounds as you move through these settings, the tabs and the rows, read from your game files (a mod's when a mod replaces them). Under Master volume on the Audio tab; changes at once | | Controller in background | Off, On: the pad keeps playing while another window has focus | | Stick dead zone | Default (24%), 5%, 10%, 15%, 20%, 30%: how far a stick moves before the game sees it | | Left stick dead zone, Right stick dead zone | As Stick dead zone, or 0% to 50% for that stick alone | | Rumble strength | Off, 25% to 300% of the game's rumble | | Vibration curve | 0.20 to 1.50: below 1.00 the game's many weak rumbles are lifted so you can feel them; 1.00 is the game's | | Trigger vibration | Off, On: an Xbox One or Series controller's triggers rumble too | | Walk key | Off, Caps Lock, Shift, Ctrl, Tab: hold it with the movement keys and Link walks instead of running | | Walk scale | 0.20 to 0.90: how far the movement keys push the stick while the Walk key is held | | Button prompts | Auto, Switch, Xbox, PlayStation 4, PlayStation 5, Steam Deck, Keyboard & mouse: the button icons the game shows (Controls page). Auto takes the controller connected when the game starts, or the keyboard and mouse with none; Keyboard & mouse shows the key or mouse button each control is bound to. Applies at the next start | | Text speed | Normal, 2x, 4x, Instant | | Export save | Your save as a zip in your Downloads folder (System tab; see *Export and import a save* below) | | Export save for a bug report | The same zip with the logs and settings a problem report needs | | Import a save | A save export of Triforce or NX2navi becomes your save at the next start | | Bug capture (F8) | One folder with what a problem report needs (System tab; see *Bug capture* below) | | Scan amiibo | A dump of one of your own figures from a folder `amiibo` beside the game (`.bin`, as the figure's tag has it: 532, 540 or 572 bytes), put on the reader when the game looks for a figure. Only the figure's serial number and which figure it is are read from the file: no key is needed. On the Debug tab (with Debug tools On) | | Game flags | The game's story and world flags by name, read from your game files: see which are set in your save, and set or clear one (Debug tab) | | Cutscenes | The game's events by name, read from your game files: start one (Debug tab) | | Mod cheats | Off, On for each cheat of a mod's cheat file, under its own name (System tab, only with such a mod; see *Mods* below) | In game, **F10** or **Alt+Enter** switches between a window and fullscreen. **F1** opens the same options from anywhere. **F8** takes a bug capture.

## Controls Play with a controller, or with keyboard and mouse. The **Controls** tab of the game's Options sets what presses each of the console's buttons: one controller input and up to two keys. Moving (W A S D) and the camera (arrow keys, or I J K L) are fixed.

## Convert saves Coming from NX2navi or an emulator? Your journey comes with you. **Convert saves** on the Welcome back screen brings your NX2navi saves into Triforce, and moves saves of this game between Triforce and an emulator in either direction: - **Into Triforce:** Setup looks for your saves by itself (an NX2navi game on this PC; Eden, yuzu, suyu, Sudachi, Citron, torzu and Ryujinx, and portable copies started from a desktop or Start menu shortcut), or you choose the folder. - **Out of Triforce:** your Triforce saves go back to an emulator the same way. Every slot comes across as it is. Whatever gets replaced is backed up first, in the `save-backups` folder beside Setup. Close the game and the emulator before converting.

## Export and import a save The **System** tab of the Options has three rows for your save. Each says under its help what it did and where the file went. | Row | What it does | |---|---| | **Export save** | Writes your save as `Triforce-save--