Skip to content

content-2026.10.31

Choose a tag to compare

@arnaudcouturier arnaudcouturier released this 31 Oct 22:19
· 8 commits to main since this release

OptiScaler-FFXIV is updated from v0.3.0 to v0.5.1, which includes v0.4.0 and v0.5.0. The fork’s new options ship off unless a line below says otherwise. Lucent adds the new keys to your OptiScaler.ini and keeps your values.
The Neural Rendering card has a new choice, Frame rate governor (Experimental). With Hold frame rate, Neural Rendering lowers its model resolution in steps, down to half, when the frame rate falls below your frame rate limit or your display’s refresh rate, whichever is lower, and raises it again once the frame rate recovers. It does nothing while Spatial compression or the fork’s automatic multiplier ([DLSSG] AutoMFG) is on. It is Off by default, and the fork has not tried it in game. An existing setup keeps it off; a Reset offers the choice.
Scene HDR now uses the fork’s continuous composition of world and interface light ([HDR] LegacyComposition = false), which replaces the rule that could draw a ring around the interface. Nobody has tried it on an HDR display yet. To go back to the old composition, set LegacyComposition = true in OptiScaler.ini. Off and HDR are not affected.
UI-free stays experimental. Its micro-stutter in motion was removed by the fork’s new default probe interval ([HudLess] ProbeInterval = 8, from v0.5.1) in the one play session it was tried, with DLSS-G preset C; ProbeInterval = 1 brings the old behaviour back. Recomposition with DLSS-G preset Auto, Lucent’s defaults, stays the recommended setup. If you picked UI-free, it stays; you can change the UI mode in OptiScaler’s menu (FFXIV tab, HUD-less) or with a Reset. Switching to or from Recomposition takes effect at once: frame generation restarts for a moment.
The fork removed the HUD replacement that the FFXIV Companion Dalamud plugin drove, and its [Companion] keys are now ignored. If you installed that plugin yourself, uninstall it: the fork no longer has the functions it calls. Lucent never installed it. The hidden AutomaticReShadeMotionScale key is retired too: the motion scaling it could turn off is now always on, and its line stays in your file, ignored.
The fork’s new diagnostics (a frame generation event recorder, a status file and several capture tools) are off. If you turn one on, Uninstall removes what it wrote in the game folder, recordings included, unless that folder was already there when Lucent installed or updated.
Fixes in the fork: a possible freeze at start-up while Streamline plugins load (never seen in a game), and a GPU reset when the UI mode was switched away from UI-free while the game ran.
Since 2026.10.28, OptiScaler-FFXIV has Automatic ReShade scene depth, which Lucent turns on by default. When the game renders below your screen resolution, it lines up the depth, normals and motion vectors that ReShade effects read with the upscaled picture, so ambient occlusion such as MXAO stops drawing shapes into walls. It needs ReShade, which Lucent installs, and stands down by itself if a preset scales or offsets depth by hand. It was tried on one RTX 4090 in SDR with one preset, so treat it as experimental: you can turn it off in the OptiScaler menu (FFXIV tab, ReShade depth compatibility). It is on for a new install or Reset setup, and for an update unless you had already set it yourself.
Since v0.3.0, OptiScaler-FFXIV finds the game’s code addresses by pattern search instead of relying on a table for one game build. After an XIV patch, the features that identify the game by program name or shader fingerprint (scene HDR, lighting, HUD-less, markers, mipmap bias) keep running. The features that read or hook the game’s own code stay off unless FfxivUnknownBuildHooks=true is set in OptiScaler.ini and the search found every address they need; the fork has not yet tried that on a real game patch. OptiScaler’s own update check, which asked the wrong project for releases, is now off. The new keys ship off, and Lucent adds them to your OptiScaler.ini.
Removes the Alive NEXT Stable 4K preset and the two shaders only it used (ffxiv_crashpad_4K and ffxiv_common_4K). Alive NEXT Stable stays. If the 4K preset was your selected preset, ReShade is switched to Alive NEXT Stable. If you edited the 4K preset, the update saves your copy as Alive NEXT Stable 4K (my edits).ini before it removes the original.
ReShade now loads every effect, including the ones your preset turns off, so the game can take a little longer to load, and it compiles shaders with debug information. Your keybinds and the rest of your ReShade settings stay as they are. It needs Lucent 1.0.2.
The Graphics step has three new choices inside the Neural Rendering card, in a collapsed Advanced section: the model hint each pass receives (Pass 1, Pass 2 and Pass 3 preset hint). Their effect on the picture is unverified. The defaults are what Lucent shipped before, so nothing changes unless you pick one, and they apply to a new install or Reset setup, not to an update.
The Graphics step has a new choice in the Neural Rendering card, Character preview Neural Rendering, which runs the Neural Rendering model on the character, equipment and glamour previews. It is Off by default because the model takes a lot of video memory for each open preview window; the previous setup had it on. It applies to a new install or Reset setup, so an existing setup keeps what it has.

Components and source tags: