eugeniosegala/decky-lsfg-vk-experimental v0.13.0-experimental.19

Decky LSFG-VK Experimental 0.13.0-experimental.19

on GitHub

Optional coexistence: If you want to keep the original/public Decky LSFG-VK plugin installed, you can. Both plugins can remain installed and enabled. For native Steam/Proton games, choose exactly one launch wrapper: public ~/lsfg %command% or experimental ~/.local/bin/lsfg-vk-experimental %command%; never combine them. Flatpak apps, including Heroic, are selected through Flatpak setup instead.

This release: Adaptive Frame Generation, SteamOS recovery, and 2x hitch handling

• Full-quality image path: With Performance Mode disabled, the v2 engine can show noticeably less ghosting than the older layer in testing. Results are game-dependent; Performance Mode remains useful when lower GPU overhead matters more than image quality.
• Adaptive Frame Generation: Optional 30–240 FPS targeting with a configurable 2x–4x ceiling; fixed 2x, 3x, and 4x remain the default. Adaptive mode now defaults to a 90 FPS target with Smooth Cadence enabled. Smooth Cadence is game- and hardware-dependent: it can improve both smoothness and perceived responsiveness, but can be turned off when a game feels better without it. Live Adaptive changes briefly reset timing and stability calculations, so allow a few seconds for output to settle before judging it.
• Adaptive stability: Adaptive starts and recovers on real frames, keeps the lowest proven multiplier that can already meet the target, and backs off extra generation load when it causes a delayed base-rate collapse. It can also rebase promptly to a sustained gameplay FPS change instead of waiting for an old cadence to return.
• 2x short-hitch recovery: Once Adaptive has validated its 2x ceiling, an isolated 100–250 ms gameplay hitch keeps that proven level, refreshes three real history frames, and resumes instead of taking the longer menu/focus recovery path. Fixed mode and Adaptive 3x/4x are unchanged.
• Profile compatibility settings: Launcher-only options such as Base FPS Cap, WoW64, Gamescope WSI, Zink, MangoHud, and Disable Frame Generation now persist with the selected Decky profile. Existing wrapper settings are imported automatically during the upgrade.
• Per-game profiles: Create a named profile in Decky, set Active In to the game executable, and lsfg-vk selects its engine settings automatically. Returning the UI selector to Default does not disable matching profiles.
• SteamOS / Gamescope recovery: A bounded image wait prevents stalls from blocking indefinitely. After a Steam-menu cadence interruption, Adaptive presents real frames, preserves the last proven level, waits for healthy game cadence, and resumes without learning from temporary menu-rate samples. A guarded swapchain rebuild remains available only for repeated stalls; Fixed mode is unchanged.
• Heroic runtime updates: Flatpak Setup now offers Update for an installed matching runtime extension, so Heroic can receive the engine bundled with a new plugin ZIP without changing its per-game Wrapper commands.

See the Configuration guide and Troubleshooting guide for the full behaviour and per-game controls.

⚠️ Required engine-update step: Installing the ZIP updates the plugin files, but does not by itself replace the private LSFG-VK layer. Open this plugin and select Install Experimental LSFG-VK (developer build) to install the version bundled in the new ZIP.

First-time Heroic setup: Read the Heroic and other Flatpak applications guide in the README.

Installation

New to Decky or installing this plugin for the first time? See the full Install and use guide for Decky Loader setup and prerequisites.

1. Download Decky.LSFG-VK.Experimental-0.13.0-experimental.19.zip below.
2. On the Steam OS, open Decky Loader's settings and enable Developer Mode.
3. Choose Developer > Install Plugin from Zip, then select the downloaded ZIP.
4. In the plugin, select Install Experimental LSFG-VK (developer build). For native Steam/Proton games, add ~/.local/bin/lsfg-vk-experimental %command% to the game’s Steam launch options.

Updating an existing experimental installation

1. Quit any game currently using ~/.local/bin/lsfg-vk-experimental.
2. Download the newer ZIP from this fork’s releases.
3. In Game Mode, open Decky Loader’s settings, then choose Developer > Install Plugin from Zip and select it.
4. Reload the plugin from Decky. If it does not reload automatically, restart your Steam Deck or Steam Machine.
5. ⚠️ Required: Open this plugin and select Install Experimental LSFG-VK (developer build) to install the version bundled in the new ZIP. Installing the ZIP updates the plugin files, but does not by itself replace the private LSFG-VK layer. Do not skip this step.
6. If you use Heroic, select Flatpak Setup, then select Update for Heroic’s matching runtime extension (usually 25.08). This replaces its Flatpak layer with the engine bundled in the new ZIP; Heroic preparation and per-game Wrapper commands remain unchanged.
7. If Decky does not show or reload the update, use the reinstall-and-restart fallback above, then repeat step 5.

Existing experimental profiles, Steam launch options, and Heroic per-game Wrapper command settings are retained. The engine files are deliberately replaced, not stacked. Prepare Heroic again only after changing the configured Lossless.dll location or disabling its Flatpak preparation. The public/original plugin may remain installed, but use exactly one plugin wrapper per game.

Known limitations of lsfg-vk 2.0.0-dev28-experimental.19

• HDR: HDR remains problematic with this payload. Disable HDR in the game before playing; it can remain enabled in SteamOS. The plugin has no general HDR control, and the v1 HDR toggle was also non-functional.

• No fixed 0x multiplier: Unlike v1, the fixed multiplier selector has no 0x choice. To run a game without frame generation, use the dedicated Disable Frame Generation setting and restart the game. Adaptive mode may internally schedule zero generated frames for an individual interval; that is not a persistent disable setting.

• Isolation trade-offs: The public and experimental plugins can coexist, but a game launched with the experimental wrapper cannot use vkBasalt or other globally installed Vulkan layers, such as overlay or post-processing layers. This affects only that game. If it needs those layers, switch its launch option back to the public plugin’s ~/lsfg %command% wrapper.

Before you play

• This is experimental: test each game before relying on it.
• Confirm the detected Lossless.dll path before launching. Leaving it blank permits upstream discovery.

Engine payload

• Bundles checksum-verified lsfg-vk-2.0.0-dev28-experimental.19-linux.tar.xz.