Crusader Kings III: Best pdx_settings.txt for Smooth Maps

The primary goal for Crusader Kings III optimization is Draw Call Reduction. Every time you pan the map, the game recalculates shadows for 3D city models and the “Advanced Shaders” for terrain borders. This configuration focuses on stabilizing the Map Panning Experience by offloading shadow resolution and disabling the notorious SSAO and Refractions which provide minimal visual benefit during active gameplay but heavy performance tax.

File Location

The pdx_settings.txt file is located in your Documents folder. Ensure the game and the Paradox Launcher are fully closed:

C:\Users\[YourUsername]\Documents\Paradox Interactive\Crusader Kings III\pdx_settings.txt

Technical Configuration (The 2026 “Smooth-Map” Template)

Open the file with a text editor and search for these specific variables. Update them to match the values below for the best performance-to-visual ratio:

"Graphics"={
	"shadow_map_size"={
		version=0
		value=1024 # Reduces CPU draw-call overhead significantly
	}
	"advanced_shader_effects"={
		version=0
		value=no # The biggest fix for 'zoomed-in' map lag
	}
	"ssao"={
		version=0
		value=no # Removes micro-stutters during panning
	}
	"refraction"={
		version=0
		value=no # Disables complex water calculations
	}
	"bloom"={
		version=0
		value=no
	}
	"mesh_lod_fade"={
		version=0
		value=no
	}
	"texture_streaming"={
		version=0
		value=yes # Essential for mid-range GPUs to prevent VRAM spikes
	}
}

Parameter Breakdown:

• advanced_shader_effects=no: This is the most critical change for 2026. This setting controls the complex lighting on borders and terrain. Disabling it has been reported to boost FPS from 20 to 90 when zoomed in on dense areas.
• shadow_map_size=1024: High-resolution shadows are calculated on the CPU in Paradox games. Reducing this to 1024 (or 512 for older CPUs) keeps the map fluid during fast movement without making the game look “flat.”
• ssao=no: Screen Space Ambient Occlusion in CK3 adds depth to the character models and buildings, but it is one of the leading causes of “frame-time jitter” when moving the camera.
• texture_streaming=yes: Forces the game to load textures into VRAM dynamically. If you have an 8GB+ VRAM card, this prevents the game from “hitching” when you quickly zoom from the Paper Map to the 3D Terrain.

Strategy for 2026 Late-Game Fluidity

To prevent the 1300+ AD “Simulation Drag”:

• The “Portrait” Sacrifice: In the in-game settings, set “Animated Characters” to Off. While seeing your heir breathe is nice, calculating 30+ 3D animations in the Royal Court or during big feasts is a massive drain on the engine.
• Exclusive Fullscreen: In the launcher settings, always choose “Fullscreen” over “Borderless.” This allows the GPU to take full priority over the display, reducing map-scrolling input lag.
• Clear the Cache: If the map feels “choppy” despite high FPS, delete the shader_cache folder located in the same directory as your pdx_settings.txt. The game will rebuild it on next launch, often fixing stuttering caused by outdated shader data.
• Population Control Mods: For very late-game runs, consider mods that prune “unimportant” dead characters. CK3 tracks the DNA and history of every person who ever lived; after 400 years, this database bloat slows down the game’s daily “tick.”

Key Performance Parameters

Parameter	Recommended Value	Impact
Advanced Shaders	No	Fixes the “Zoom-In” lag spikes.
Shadow Map Size	1024	Stabilizes CPU usage during camera movement.
Character SSAO	No	Improves 1% low FPS in the Royal Court.
Map Objects	Low / Off	Removes non-essential trees/houses for faster panning.

Frequently Asked Questions (FAQ)

Conclusion and Expected Results

By disabling Advanced Shaders and SSAO in your pdx_settings.txt, you are removing the heaviest post-processing layers of the Clausewitz engine. You can expect a significant reduction in map-panning stutter, faster transitions between zoom levels, and a more stable “Speed 5” experience during the late-game centuries.