Dead Cells: Best settings.json for High Refresh Rate Sync

The objective is to disable the internal Unity/Heaps V-Sync and utilize the DirectX 12/Vulkan flip-model for zero-latency frame delivery.

File Path & Access

1. Locate the Config: Navigate to C:\Program Files (x86)\Steam\userdata\<YourID>\588650\remote.
2. The File: Look for settings.json. (Note: If you use the OpenGL legacy branch, this might be in the root game folder).
3. Pro Tip: If the file is missing, launch the game, change one video setting, and close it to force the JSON generation.

Optimized “High-Hz” Configuration Table

Parameter	Recommended Value	Technical Purpose
vsync	false	The Core Fix. Removes the engine-level sync lock.
maxFps	-1 or MonitorHz + 3	Unlocks the engine or sets a stable ceiling above refresh.
fullscreen	true	Required for “Exclusive Fullscreen” low-latency hooks.
displayMode	1	Forces the hardware-accelerated rendering path.
limit_fps_in_background	false	Prevents stuttering when alt-tabbing during stream sessions.

HowTo: Engineering the Dead Cells Sync Pipeline

Follow these GameEngineer.net technical steps to stabilize your 2026 high-Hz build:

1. The “Uncapped” Injection: Open settings.json and locate the "maxFps" line. Set it to -1. This allows the game to render as fast as your GPU can push, which minimizes the input-to-pixel latency ($L_{pixel}$).
2. The “Windowed-to-Full” Reset: There is a known bug in the Dead Cells engine where V-Sync remains active even if set to false. To fix this, toggle Windowed Mode on and then back to Fullscreen once in-game. This forces the Windows compositor to release the frame-buffer lock.
3. Reflex/Anti-Lag Integration: If using an NVIDIA GPU, set Low Latency Mode to Ultra in the Control Panel. For AMD, enable Radeon Anti-Lag. This ensures the CPU doesn’t queue frames ahead of the GPU, maintaining a 1:1 input feel.
4. Triple Buffering Kill-Switch: Ensure "tripleBuffer": false is set in your JSON. Triple buffering adds exactly one frame of lag ($+4ms$ to $+16ms$ depending on Hz), which is detrimental in a game where parry windows are frame-sensitive.
5. Controller Polling Rate: If the game feels “heavy” at 240Hz+, it’s often your controller’s polling rate ($R_{poll}$). Use LordOfMice’s HIDUSBF tool to overclock your controller’s polling rate to 1000Hz.

Technical Explanation: Frame Pacing and the Heaps Engine ($E_{heaps}$)

Dead Cells runs on the Heaps engine. Unlike Unreal or Unity, Heaps relies heavily on a fixed update loop for its logic.

$$Update\_Interval = \frac{1}{60} \text{ (Standard Logic Tick)}$$

Even if your screen renders at $240Hz$, the game logic still “thinks” in $60Hz$ steps. By unlocking the FPS via settings.json, you are not speeding up the game, but rather providing more “opportunities” for the renderer to catch the latest logic update. This results in smoother motion blur and reduced “teleporting” of projectiles, as the visual delta ($\Delta_{vis}$) is updated 4x more frequently than the standard base.