Cities: Skylines II is two workloads in one application: a city simulator and a very large asset loader. When the simulation speed collapses after a mod update, it is tempting to blame the graphics settings. That is usually wrong. The tick rate is CPU and simulation logic; the frame rate is a separate question.
The 1.5.2f1 patch improved mod platform behaviour and simulation stability, not mod compatibility. A load order built for the launch version can still break a 2026 city. This file gives you a dependency-first order and a way to measure what each layer costs.
The safe post-patch sequence
Copy the save first- Duplicate the city save before changing the mod set. Never experiment on the only copy.
- Disable all mods except the core framework and launch. If the city loads, the base is healthy.
- Enable dependencies first, then content packs, then traffic or simulation overhauls.
- Pause the simulation and compare 30 simulated minutes at the same speed after each batch.
- If a mod is incompatible, disable it rather than leaving it “half loaded.”
A dependency-first load order
Cities: Skylines II / mod staging order
Top → bottom- 01 Core framework and mod platform Must match the game build Core
- 02 Shared libraries and dependency packs Load before any mod that requires them Needs core framework
- 03 Map and asset packs Memory-heavy; not always simulation-heavy
- 04 UI and quality-of-life mods Usually low simulation cost
- 05 Traffic and pathfinding mods Can dominate the simulation tick Vs other traffic overhauls
- 06 Economy and gameplay overhauls Load last; high conflict potential Vs other economy overhauls
When two mods touch the same system, the later one does not magically “win” in every case. The mod platform may disable one, surface a conflict, or let both apply unpredictably. Read the conflict list before you launch a 200,000-person city.
Where the files live
.cache\ # local cache and logs
Logs\ # game and mod logs
Saves\ # city saves
ModsData\ # local mod data, if used
%USERPROFILE%\AppData\LocalLow\Colossal Order\Cities Skylines II\
# Mod platform data can also live here depending on the install. Open the newest log after a failed load and search for the mod name or a null-reference error. A city that crashes on load often names the missing prefab or dependency. That is more useful than re-ordering every folder alphabetically.
Measure simulation speed, not just FPS
Use a fixed city, pause the simulation, record the population and cash, then run 30 in-game minutes at the same speed. Note real elapsed time and the simulation tick rate. Repeat after each mod batch. A traffic mod that adds 15% to the tick cost is a measurable result; “feels slower” is not.
Black: average / Blue: 1% low
Bench: 13900K / RTX 4080 SUPER / 32 GB DDR5. 120,000-population test city, 30 simulated minutes per run, paused camera. CPU frame time and wall-clock simulation time recorded separately.
The benchmark chart’s “average” is the rendered frame rate, not simulation speed. The traffic-overhaul run also increased wall-clock simulation time by 23% on this city. Both numbers matter; a beautiful camera view does not compensate for a city that takes twice as long to advance.
Built locally in your browser. Nothing is uploaded.
; GamePathHub baseline // Cities: Skylines II ; Unity players usually persist display settings in the registry. ; Prefer the in-game menu, then use launch options for display overrides. ; ; Suggested in-game baseline: ; VSync ................ Off ; Target FPS ........... 60 ; Texture Quality ...... High ; Shadow Distance ...... Medium ; Upscaling ............ DLSS Quality ; ; Recommended launch options: ; -screen-fullscreen 1 -high
Unity’s configuration is deliberately conservative here because Cities: Skylines II manages its own settings and mod platform. Treat the generated file as a checklist; the in-game options and mod manager are authoritative.
CS2 city / mod stabilisation
0 / 7 completeThe hardware truth
Cities: Skylines II is CPU-sensitive as the city grows. A 16 GB card can run out of VRAM with a large asset library, but the simulation slowdown after mods is usually a CPU cost. Do not buy a GPU to fix a tick-rate problem. If your city is large, more memory and a faster CPU architecture matter more than another 5% GPU clock.
The rule for a long-lived city
A city is a save file with dependencies. Treat every mod as a library that must be available for that save. Keep a manifest, copy before each change, and do not update a dependency in the middle of a build. The simulation speed you save may be your own evening.
Did this fix work on Patch 1.5.2f1 — simulation and mod platform fixes?
One click. No account. Your vote is stored in this browser and de-duplicated per file.
Verified against 1.5.2f1 — simulation and mod platform fixes. Votes are local-only telemetry.
Cities: Skylines II: bench questions
3 answersDo more mods always slow down Cities: Skylines II?
Where is the Cities: Skylines II mod load order?
Can I move a save to a new mod set?
Modding & Load Order
This field file was tested against the patch context above. If a launcher update changed your menu labels, include the exact build number in a report to the desk.
Cities: Skylines II: CTD, DXGI_ERROR_DEVICE_HUNG & Black-Screen Launch Fixes
Stabilise Cities: Skylines II on PC: diagnose crash-to-desktop loops, DXGI device-hung resets, black-screen starts, and anti-cheat or DLL launch blocks on Unity.
Cities: Skylines II: Shader Stutter, Frame Pacing & Unity Config Tuning
A measured stutter-hunting routine for Cities: Skylines II: shader compilation warm-up, frame-pacing limits, upscaler presets, and the exact Unity settings file to edit.
Cities: Skylines II: Safe Mod Install, Load Order & Post-Patch Conflict Recovery
Install mods on Cities: Skylines II without breaking the build: framework order, script conflicts after a patch, and a clean rollback path that keeps your saves intact.