RimWorld: Best Prefs.xml for High Colony FPS Fix

While most players rely on mods like RocketMan or Performance Fish, the Prefs.xml provides a baseline override to disable engine-level rendering tasks. Disabling “Plant Sway” and “Shadows” directly in the config can provide a $10–15\%$ FPS boost on lower-end CPUs by reducing the number of draw calls per frame.

File Path

RimWorld’s preferences are stored separately from the game installation to preserve settings across updates.

%APPDATA%\..\LocalLow\Ludeon Studios\RimWorld by Ludeon Studios\Config\Prefs.xml

Technical Note: Always make a backup before editing. If the file becomes corrupted, RimWorld will generate a new default one on the next launch.

Optimized Performance Configuration Block

Locate the following boolean tags in your Prefs.xml and set them to false. These settings significantly reduce the GPU/CPU overhead during 3x speed gameplay.

Tag	Recommended Value	Technical Purpose
<plantSway>	false	Stops the calculation of wind-based plant movement for every grass/tree tile.
<showShadows>	false	Removes real-time shadows, which are costly for large, complex bases.
<runInBackground>	true	Allows the game to keep ticking consistently if you Alt-Tab.
<vSync>	false	Reduces input lag; use a frame-rate cap via GPU software instead.
<textureCompression>	true	Reduces VRAM usage, which is essential for heavy modlists.

<Prefs DataFormatVersion="1">
    <plantSway>false</plantSway>
    <showShadows>false</showShadows>
    <vSync>false</vSync>
    <textureCompression>true</textureCompression>
    <runInBackground>true</runInBackground>
    <maxSimulatedTicksPerFrame>10</maxSimulatedTicksPerFrame>
</Prefs>

HowTo: Engineering Late-Game TPS Stability

To truly fix RimWorld lag on GameEngineer.net, follow these auxiliary technical steps:

1. The “Adaptive” Mod Method: Use RocketMan. In 2026, it remains the gold standard. When you first load your colony, let it run in “Adaptive Mode” for 30 minutes. It learns your modded pathfinding patterns and caches them, restoring up to $200–300 \text{ TPS}$.
2. Pathfinding Bottlenecks: Avoid “narrow” corridors. The AI struggles with “Pawn Collision” in 1-tile hallways. Designing 3-tile wide main arteries reduces the CPU cost of pathfinding calculations.
3. Animal Management: Every animal on the map is a “Pawn” with its own ticking logic. Use the “Mothballed” setting in performance mods or cull non-essential livestock to save hundreds of ticks per second.
4. Work Zone Scoping: Reduce the “Search Radius” on your workbench bills. Instead of searching the “Whole Map” for steel, set it to “50 squares.” This prevents the CPU from scanning every tile on the map every time a pawn starts a job.
5. Clean the World: Use RuntimeGC or a similar 2026 tool to “Clean World Pawns.” The game remembers every dead raider’s family tree, which eventually bloats the save file and slows down the social AI.

Technical Explanation: Ticks vs. Frames

In RimWorld, the game runs at a nominal 60 TPS on Speed 1. On Speed 3, it aims for 360 TPS. When your colony grows, the CPU cannot complete 360 logic cycles in one second, causing the game to “stutter” even if your FPS is high.

By setting <plantSway>false</plantSway> in the Prefs.xml, you remove a per-tile shader calculation. While this seems minor, on a $250 \times 250$ map ($62,500$ tiles), reducing the overhead of environmental animations allows the CPU to dedicate more “nanoseconds” to the Pathfinding Job System. This is why your game feels “smoother” even though the graphics look static; you are effectively increasing the Simulation Ceiling.