Where are the speed controls?
The revised June tutorial points to the time controls beneath the minimap. The official material establishes the documented feature, while the dated gameplay examples help show how that feature appeared in a particular build. Keeping those two evidence types together makes it easier to separate a confirmed mechanic from an assumption based on another game. Its narrator demonstrates changing simulation speed rather than changing the game's rendering performance.
A difference between those versions can explain apparently conflicting instructions without proving that one source is universally correct. If a step or value is not demonstrated in the collected sources, treat it as unverified and check a current developer update before relying on it. An October 27 preview also shows a maximum displayed multiplier of x5, providing a later observation of that control range. Use the visible controls in your own build as the starting point.
The collected material does not verify a universal keyboard shortcut, an unlocked higher multiplier or a hidden configuration value. This guide therefore describes the demonstrated interface location without inventing hotkeys or unsupported speed settings. This keeps unrelated editor choices from obscuring what changed. It also gives you a clearer basis for describing a reproducible result to other players, without turning one observation into a guaranteed rule for every save or build.
Why do older guides mention different speeds?
The original tutorial footage often discusses x3, while the June 11 Patch 4 notes document the addition of x4 and x5. The official material establishes the documented feature, while the dated gameplay examples help show how that feature appeared in a particular build. Keeping those two evidence types together makes it easier to separate a confirmed mechanic from an assumption based on another game. These statements refer to different points in the demo's update history.
A difference between those versions can explain apparently conflicting instructions without proving that one source is universally correct. If a step or value is not demonstrated in the collected sources, treat it as unverified and check a current developer update before relying on it. A recording that stops at x3 is not necessarily showing the final available control range. The patch also changed the calendar so that a month lasted one in-game day.
That matters when comparing comments about how long a year takes. A number recorded before the calendar change should not be combined with a later maximum speed to produce a new calculation. This keeps unrelated editor choices from obscuring what changed. It also gives you a clearer basis for describing a reproducible result to other players, without turning one observation into a guaranteed rule for every save or build.
Does a year take 48 real minutes?
The June 11 documentation gives a 48-minute real-time year at x5 for that build's configuration. The official material establishes the documented feature, while the dated gameplay examples help show how that feature appeared in a particular build. Keeping those two evidence types together makes it easier to separate a confirmed mechanic from an assumption based on another game. The revised demo tutorial later repeats that relationship.
A difference between those versions can explain apparently conflicting instructions without proving that one source is universally correct. If a step or value is not demonstrated in the collected sources, treat it as unverified and check a current developer update before relying on it. It is useful historical evidence for the patched demo, not a universal benchmark for all future releases and machines. Other early descriptions of maximum-speed year length disagree, so this page does not blend them into a single present-day promise.
The October preview supports the displayed x5 ceiling and the one-day-per-month observation. It does not establish that every later build and session must reproduce exactly the same wall-clock timing. This keeps unrelated editor choices from obscuring what changed. It also gives you a clearer basis for describing a reproducible result to other players, without turning one observation into a guaranteed rule for every save or build.
Will faster time improve population growth?
A speed multiplier advances simulation time; it does not replace the requirements of the settlement systems. The official material establishes the documented feature, while the dated gameplay examples help show how that feature appeared in a particular build. Keeping those two evidence types together makes it easier to separate a confirmed mechanic from an assumption based on another game. The collected population material links growth to food and documents families, children and aging.
A difference between those versions can explain apparently conflicting instructions without proving that one source is universally correct. If a step or value is not demonstrated in the collected sources, treat it as unverified and check a current developer update before relying on it. Functional housing, a configured city and a healthy settlement are therefore separate questions from how quickly the clock advances. If your goal is to observe population behavior, first check the city's setup instead of assuming that the highest speed guarantees a result.
A house drawn without its House POI is still missing housing functionality. A City Zone without the correct faction relationship is also a different problem from a slow calendar. This keeps unrelated editor choices from obscuring what changed. It also gives you a clearer basis for describing a reproducible result to other players, without turning one observation into a guaranteed rule for every save or build.
Is simulation speed the same as frame rate?
Simulation time describes the rate at which the world's clock and systems advance. The official material establishes the documented feature, while the dated gameplay examples help show how that feature appeared in a particular build. Keeping those two evidence types together makes it easier to separate a confirmed mechanic from an assumption based on another game. Frame rate describes visual rendering performance, and the collected materials do not establish a universal relationship between the two.
A difference between those versions can explain apparently conflicting instructions without proving that one source is universally correct. If a step or value is not demonstrated in the collected sources, treat it as unverified and check a current developer update before relying on it. Setting x5 is therefore not evidence of a particular number of frames per second or a guaranteed performance improvement. Keep those questions separate when comparing videos.
A large or complex world may be presented at a particular speed without the recording proving how another computer will perform. This guide does not supply unsupported hardware benchmarks or recommend undocumented configuration changes. This keeps unrelated editor choices from obscuring what changed. It also gives you a clearer basis for describing a reproducible result to other players, without turning one observation into a guaranteed rule for every save or build.
How should you use time while building?
Historical editor footage shows pausing as part of a worldbuilding session. The official material establishes the documented feature, while the dated gameplay examples help show how that feature appeared in a particular build. Keeping those two evidence types together makes it easier to separate a confirmed mechanic from an assumption based on another game. That is useful context when separating setup work from the period in which you observe the simulation.
A difference between those versions can explain apparently conflicting instructions without proving that one source is universally correct. If a step or value is not demonstrated in the collected sources, treat it as unverified and check a current developer update before relying on it. The sources do not verify a universal pause key or an identical arrangement of controls in every editor version. A practical approach is to finish one small, coherent city setup and then watch how its systems behave as time advances.
Inspect housing, food access and faction ownership before drawing conclusions from a quiet settlement. If you compare your result with a tutorial, match the build date and time configuration before using the video's elapsed time as a reference. This keeps unrelated editor choices from obscuring what changed. It also gives you a clearer basis for describing a reproducible result to other players, without turning one observation into a guaranteed rule for every save or build.
Sources and verification
This answer cross-checks developer and Steam material against independent reporting or gameplay footage. Details from older demos are identified as historical because interfaces and availability can change between builds.