The primary goal for Hollow Knight performance is Input Latency Minimization. The game’s in-game V-Sync toggle often fails to fully disengage the Unity engine’s internal vertical sync, leading to ghosting or delayed response times. This configuration focuses on disabling the sync via the Config.ini and using the game’s built-in (but hidden) FrameRateCap to match your monitor’s refresh rate perfectly.
File Path
Hollow Knight stores its configuration in the game’s local data folder. Note that the folder name is usually hollow_knight_Data.
...\Steam\steamapps\common\Hollow Knight\hollow_knight_Data\Config.ini
(Note: If the file is not there, check %AppData%\..\LocalLow\Team Cherry\Hollow Knight for the global settings file.)
Technical Configuration (The 2026 “Godhome” Template)
Open the Config.ini with Notepad. Locate and modify these specific values to ensure the game runs as fast as your hardware allows without the V-Sync penalty.
# Hollow Knight V-Sync & Lag Fix - GameEngineer.net
[Video]
VSync=0
FrameRateCap=144 # Set this to your monitor's refresh rate (e.g., 60, 144, 240)
FrameRateLimit=1
UseNativeResolution=1Parameter Breakdown:
- VSync=0: This is the hard override. Setting this to
0in the.iniis more reliable than the in-game menu, as it prevents the Unity engine from initializing the vertical buffer at the driver level. - FrameRateCap=144: Hollow Knight actually has a built-in limiter that is often set to
-1(unlimited) or400. For the most stable input response, set this to match your monitor’s Hz. This prevents the GPU from overworking and reduces “frame-time jitter.” - FrameRateLimit=1: Ensures the cap you set above is strictly enforced by the engine logic.
- UseNativeResolution=1: Prevents the game from scaling, which can sometimes introduce slight pixel-processing lag in full-screen mode.
Strategy for 2026 Competitive Precision
- Disable “Blur” and “Particle” Overkill: While not in the
.ini, ensure Blur Quality is set to Low or Off in-game. In 2026, the high-refresh-rate clarity of OLED/IPS panels is ruined by the game’s post-process blur, making fast bosses like Nightmare King Grimm harder to track. - The “Fullscreen” Trap: Always play in Fullscreen mode, not “Windowed” or “Borderless.” Windows’ Desktop Window Manager (DWM) forces its own sync on windowed applications, re-introducing the lag you just removed in the
.ini. - Launch Options (DirectX 11): Right-click Hollow Knight in Steam > Properties > Launch Options and enter
-force-d3d11. This forces the game into a more stable rendering path for 2026 drivers, often reducing micro-stutter. - Controller Latency: If using a wireless controller, ensure your Bluetooth polling rate is optimized, or use a wired connection. Hollow Knight’s input reading is extremely sensitive to the “polling intervals” allowed by the OS.
Key Performance Parameters
| Parameter | Recommended Value | Impact |
| VSync | 0 (Off) | Eliminates the 1-2 frame delay in jump/attack. |
| FrameRateCap | Monitor Hz | Provides consistent, predictable timing for parries. |
| Anti-Aliasing | Off | Sharpens the “hand-drawn” edges for better clarity. |
| Particle Effects | Medium / Low | Reduces CPU spikes in boss arenas (e.g., Trial of the Fool). |
Frequently Asked Questions (FAQ)
I see “Screen Tearing” now. How do I fix it without V-Sync?
Use NVIDIA G-Sync or AMD FreeSync from your GPU control panel instead of the in-game V-Sync. This provides the smoothness of V-Sync without the input lag penalty.
Why does the game feel “fast” after disabling V-Sync?
If your FPS goes too high (e.g., 400 FPS), the physics can occasionally feel “floaty.” This is why setting the FrameRateCap in the .ini to a sensible number (like 144 or 165) is vital.
Does this work for the Silksong demo/release?
While Silksong uses a newer version of the engine, the internal logic for VSync and FrameRateCap remains similar. However, the file path may change to ...\TeamCherry\Silksong\....
My controller stopped working after the update!
This is often a “Steam Input” conflict. Right-click the game > Properties > Controller > Disable Steam Input. Then, let the game’s native Config.ini handle the raw input.
Conclusion and Expected Results
By manually forcing VSync=0 and setting a dedicated FrameRateCap in your Config.ini, you are removing the single biggest obstacle to high-level play. You can expect instantaneous nail swings, more responsive mid-air dashes, and perfectly timed parries against even the fastest bosses in the Pantheon.