Lossless Scaling: Best settings.json for LSFG 2.0 Frame Generation

The settings.json file allows for granular control over the Queue Target and Capture API, which are the two biggest factors in determining whether your game feels “fluid” or “floaty.”

File Path

Lossless Scaling stores its global configuration and per-executable profiles in the local AppData folder.

%LOCALAPPDATA%\Lossless Scaling\settings.json

Technical Note: To prevent the app from overwriting your custom “Queue Target” tweaks, ensure the game is closed before editing. In 2026, using the WGC (Windows Graphics Capture) API is recommended for Windows 11 24H2+ users for lower latency.

Optimized “LSFG High-Speed” Configuration Block

Add or modify these parameters within your JSON structure. This setup targets a $3:1$ or $2:1$ frame ratio with minimal artifacting ($A_{vis}$).

Parameter	Recommended Value	Technical Purpose
"captureAPI"	0 (DXGI) or 1 (WGC)	WGC is faster on modern Win11; DXGI is more stable on Win10.
"lsfg_multiplier"	2	2x is the Gold Standard. 3x/4x adds significant input lag.
"flow_scale"	0.75	Balance between motion vector accuracy and GPU overhead.
"queue_target"	1	The Latency Fix. 0 is lowest lag but prone to stutter; 1 is ideal.
"performance_mode"	true	Uses a lighter ML model—mandatory for high-res (1440p/4K).

{
  "active_profile": "Standard_2026",
  "profiles": [
    {
      "name": "High_Performance_FG",
      "lsfg_multiplier": 2,
      "flow_scale": 0.75,
      "performance_mode": true,
      "queue_target": 1,
      "capture_api": 1,
      "sync_mode": 0,
      "max_frame_latency": 1,
      "allow_tearing": true
    }
  ]
}

HowTo: Engineering the Ultimate Frame Generation Setup

Follow these GameEngineer.net technical steps to ensure your “fake” frames feel real:

1. The “Half-Refresh” Rule: Always cap your in-game FPS to exactly half (for 2x) or one-third (for 3x) of your monitor’s refresh rate ($Hz$). For a 144Hz screen, cap the game at 72 FPS. This prevents the “pacing judder” that occurs when the engine and LS compete for the same GPU cycle.
2. GPU Headroom Check: LSFG requires roughly 10–15% of your GPU’s power to generate frames. If your GPU is at 99% usage, LS will fail, causing massive stutter. Lower your in-game settings until you hit ~85% usage before turning on LS.
3. Reflex/Anti-Lag Integration: Enable NVIDIA Reflex or AMD Anti-Lag in the game menu. This reduces the base latency ($L_{base}$), making the added latency from LSFG much less noticeable.
4. Cursor Speed Adjustment: In the LS app, enable “Adjust Cursor Speed.” Frame generation naturally slows down your mouse movement because the UI is also being interpolated; this setting compensates for the “heavy” mouse feel.
5. Disable Overlays: Steam, Discord, and even RTSS overlays can interfere with the frame capture ($C_{path}$). If you experience black screens or flickering, disable all overlays before scaling.

Technical Explanation: Flow Scale and Motion Estimation

LSFG (Lossless Scaling Frame Generation) operates on a Motion Estimation algorithm. The flow_scale parameter dictates the resolution of the optical flow grid.

Mathematically, at a scale of 1.0, the algorithm analyzes every pixel block for movement. At 0.75, it uses a slightly coarser grid, which reduces the GPU Compute Time ($T_{comp}$) by roughly 25%. In high-speed games, a lower flow scale is often better because it reduces the “ghosting” artifacts around fast-moving objects, as the algorithm is less likely to get “confused” by sub-pixel micro-movements.