Use a repeatable comparison
Record the hardware, display resolution, scene and setting you change. Compare the same station or street after the update. An uncontrolled before/after observation cannot establish an exact percentage improvement.
Loading failures need save context
#20 addressed loading errors, and #21 describes a potential fix for major crashes during loading. Keep the affected save and report whether the crash occurs before a menu, while loading or after entering the world. Do not diagnose every crash as shader cache corruption.
Movement problems are not always performance
A Clinic respawn inside a wall (#9), a worker unable to reach a shelf and a queue of blocked traffic are separate issue types. Use the matching fix rather than lowering graphics settings as a universal response.
Patch evidence
Updated . Historical demonstrations retain their original dates; a patch label is not a numeric build ID.
Frequently asked questions
Are the official minimum specs an FPS guarantee?
No benchmark result is established by the listed components. Use the requirements to compare hardware, then investigate the actual scene and symptom separately.