mirror of
https://git.triforceproject.com/triforce/source
synced 2026-11-21 00:59:59 -04:00
Triforce v0.6.0 "Sage Of Power"
Faster frames (the replay's memory work, held submits, helper threads, collection and capture cuts), the game letting old areas go (QueryMemoryInfo), the 0.5.2 stutter fixed, AMD RX 5000/6000 and integrated-GPU fixes, the GPU device chosen by name, the in-game menus and launcher reworked, controller, Linux and benchmark fixes.
This commit is contained in:
41
readme.md
41
readme.md
@@ -132,48 +132,47 @@ Then come your settings, and **Start game**.
|
||||
## <img src="assets/readme/sapphire.svg" alt="" width="26"> 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.
|
||||
Graphics, Audio, Controls and System sit beside the game's own list, and **L** / **R** switch between them. Each tab's
|
||||
settings come in groups under the game's own separator: Display has Screen, Ultrawide, HDR, RenoDX and Overlay; Graphics
|
||||
has Upscaling, Anti-aliasing, Frame generation, Frame rate & latency and Textures. A setting that does nothing with the
|
||||
others as they are is not shown (Paper white with HDR off, the DLSS model without DLSS). 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 |
|
||||
| HDR | Off, Expanded, Native (the game's own HDR), Native + RenoDX, on an HDR display; with HDR on, Paper white 80 to 400 nits and Peak brightness 400 to 10,000 nits. Native + RenoDX applies at the next start (Off, Expanded and Native change at once) |
|
||||
| RenoDX | With HDR Native + RenoDX: RenoDX's tone mapping in place of the game's own, and its rows. UI brightness (the HUD's and the menus' white); Tonemapper Vanilla, PsychoV35 or RenoDRT; Gamma correction Off, 2.2 or BT.1886 (2.4); Color space, Exposure, Middle gray, 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 Color grading |
|
||||
| Frame generation | Off, Auto, 2x up to 8x; AMD FSR (one frame made by AMD's frame generation library between each two of the game's, the HUD kept where the game drew it) where your card, driver and build have AMD's frame generation, shown with its version: AMD FSR (3.1.6) on a Radeon RX 6000 or 7000, FSR 4's on an RX 9000. Paused with HDR Native or RenoDX (the renderer's own makes the one frame there, as at 2x); HDR Expanded works; NVIDIA DLSS 2x, 3x, 4x on an NVIDIA RTX card with a build that has NVIDIA's Streamline (an RTX 40 or 50 runs it; applies at the next start) |
|
||||
| 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% |
|
||||
| Frame pacing | Off, Even, Steady (any rate), Steady (refresh steps). Even (the default): each frame is shown at an even interval, for less stutter at up to one frame of delay. Steady applies at the next start: 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 |
|
||||
| Low latency | Off, On, On + Boost: NVIDIA Reflex on an NVIDIA card (Boost keeps the card's clocks up), AMD Anti-Lag 2 on an AMD one (Off, On); not shown where neither runs. With DLSS frame generation Reflex is always on, and it holds the frame rate cap where each frame starts in place of the game's own wait, so a frame waits once (where RivaTuner limits the game, RivaTuner does) |
|
||||
| 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 |
|
||||
| Upscaler | Game, NVIDIA DLSS, AMD FSR 3.1, AMD FSR 4 (named by the version AMD's library runs, such as AMD FSR 4.1): those your card and build can run |
|
||||
| Render resolution | Auto (the game's dynamic resolution), 100%, 75%, 67%, 50% with the game's own upscaler; with DLSS and FSR Auto, Native (100%: DLAA, or FSR's native anti-aliasing), Quality, Balanced, Performance, Ultra Performance. Applies at the next start |
|
||||
| Anti-aliasing | Game SMAA, Off, FXAA, SMAA Ultra: how the 3D's edges are smoothed with the game's own upscaler. DLSS and FSR smooth them themselves, from frames the game's SMAA has not been over, and the row is then not shown |
|
||||
| Sharpness | 0–100% (0, off, by default; around 50% suits DLSS and FSR): with DLSS or AMD FSR as the Upscaler the 3D before the HUD, with the game's own upscaler the picture at the window |
|
||||
| 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 |
|
||||
| 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 2 or 3 by your processor, none with four cores or fewer; 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 |
|
||||
| Output resolution | 1536x864 (handheld: the game's handheld profile, as if the console were undocked), 1920x1080, 2048x1152 (the game's own), 2560x1440, 3840x2160, 5120x1440, 5120x2160, 5120x2880; applies at the next start. The finished picture is scaled to the window by AMD FSR 1 when it is enlarged (sharpened only by the Sharpness row) and by the plain copy otherwise, and always by the plain copy with HDR Native, which keeps its 10 bits (`RX_VK_UPSCALE=<0..3>` in `triforce_env.txt` fixes the filter) |
|
||||
| Aspect ratio | 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. Wider than 16:9, HUD position and Menu sides show too |
|
||||
| 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 |
|
||||
| Left stick dead zone, Right stick dead zone | Default (24%), or 0% to 50%: how far that stick moves before the game sees it |
|
||||
| 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 |
|
||||
| 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 with none the device you used last in the game before (the keyboard and mouse the first time); 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 |
|
||||
|
||||
Reference in New Issue
Block a user