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:
@@ -675,8 +675,11 @@ bool capable() {
|
||||
}
|
||||
|
||||
uint32_t frames_wanted() {
|
||||
// (the row first: a device is not asked anything, and nothing is logged, while frame generation is not at 2x)
|
||||
return asked() && !dlssg::active() && capable() ? 1u : 0u; // (Triforce: not beside NVIDIA DLSS frame generation)
|
||||
// (the row first: a device is not asked anything, and nothing is logged, while frame generation is not at 2x.
|
||||
// (Triforce, FG-6) It was not read: with RX_VK_FSR_FG=1 and the row Off, FSR 3.1's inputs were made every frame and its
|
||||
// upscale moved after the bloom for frames nothing was made for. Still RX_VK_FSR_FG=1 alone: it has no picture without
|
||||
// the HUD, and the row's AMD FSR frame generation is AMD's own library, which has)
|
||||
return opts.framegen == 2 && asked() && !dlssg::active() && capable() ? 1u : 0u; // (Triforce: not beside NVIDIA DLSS frame generation)
|
||||
}
|
||||
|
||||
bool prepare(uint32_t width, uint32_t height, uint32_t render_width, uint32_t render_height,
|
||||
|
||||
Reference in New Issue
Block a user