Creator: FAQ

The small loop, The city in motion, Criss-cross and Across the districts. The scenes differ in size, vehicle count, stops and routes. The scenes chapter describes all four and their conditions.

The documented version has four fixed scenes and no variant selector. Reopening the same scenario does not generate a new seed. Use a different scene or your own completed game day for different material.

There are no scenario controls for country, weather, time of day, vehicle count or seed. These are fixed in the prepared scene. Choose another scene or a personal day replay for different material.

Prepared scenes can start with their own playback speed. The small loop starts at 1×; the other three documented scenes start at 2×. Afterwards, use the speed button or +/− to choose your preferred step.

The accessible interface is a playback and camera tool. It does not include a city, order or fleet editor. Choose another scene or a personal day replay if you need different material.

Recording begins when deliveries start. A playable replay is only created once the day has finished and saving has succeeded. A planning phase on its own is not enough.

The replay may still be saving. Wait for completion and read the displayed status. If saving fails, the actual game day still finishes normally.

Not as a normally completed day replay. Incomplete recordings do not meet the completion and integrity requirements. For a new recording, play a day all the way through.

No. A replay describes a recorded day for playback. It does not resume a playable run, change the original decisions or constitute a video file.

No. Seeking and camera movement only change which part of the recorded sequence you view. For a different route, plan it during an actual game day and then use that day’s replay.

Creator playback stretches fast movement to make captures readable. All vehicles and events remain on the same shared time mapping. The displayed Creator time is therefore not simply the real duration of the original play session.

Normal seeks deliberately pause so that you can check the moment and camera. Press Space to resume. Home is the exception: it jumps to the beginning and plays immediately.

No. The timeline sets the whole scene to a shared time. This preserves the relationships between vehicles, stops and events.

This is not guaranteed. The tool checks the version, required game data and integrity. If the version or data differs, you need a matching build or a new replay. Manually changing the file is not a reliable repair.

A freely accessible archive browser is not connected to the current regular interface. The confirmed personal entry point is the clapperboard on the current completed day’s results. Files existing locally therefore does not mean they can be opened through a general library.

The action requires a subject vehicle, but none is selected. Choose one in the timeline or directly in the city. Manual free movement may have cleared an earlier selection.

Vehicles are only available within their valid section. Seek to a time when it exists in the scene, or choose another vehicle. A number in the list alone does not guarantee availability at every time.

Key 3 belonged to Roadside, which has been removed. The other number keys keep their assignments: 1 Bird’s-eye, 2 Front, 4 Third person, 5 Free, 6 Cockpit.

Position the free camera next to the route. For a fixed view, leave all attachments off. If only the viewing direction should follow the vehicle, select it and enable Keep vehicle in frame while leaving Move with vehicle off.

Manual input takes over camera control and clears both attachment and vehicle selection. Position the camera first, then reselect the vehicle and enable the attachment you want.

Move with vehicle changes the camera’s location to follow the journey. Keep vehicle in frame aims at the subject. You can enable either or both. A fixed camera with a tracking view only needs Keep vehicle in frame.

T enables a rigid camera relative to the vehicle. Position and viewing direction turn with it through corners. This forces movement with the vehicle and disables independent aim tracking.

The Cockpit camera already rotates with the vehicle. An additional switch for the same attachment is unnecessary there and is hidden.

Free also describes a custom camera position with optional attachment. The active attachment switches and T determine its behaviour, not just the perspective name.

An obstacle lies between camera and subject. The capture is not automatically free of buildings. Pause and choose another location, height or a more visible stretch of road.

Use Reset camera. With an available vehicle selected, you get a Bird’s-eye overview of that vehicle; without a subject, a free city overview. Playback time remains independent of this.

A menu for custom saved perspectives is not accessible in this version. For repeatable takes, note the scene, time, vehicle, camera and settings. Do not rely on older instructions for My perspectives.

Possible causes include an open pause menu, an active text field, loading in progress or a restricted tutorial step. Close the menu, leave the text field and check the current task.

WASD moves horizontally even when you look diagonally up or down. Use E to rise and Q to descend. In Free, the mouse wheel moves along the viewing direction.

The mouse-button swap setting also applies in the Creator. By default, the middle button looks around and the right button pans. Follow the current hints in the tool.

This combination changes camera flight speed. Change the scene’s playback speed using +/− or the speed button.

Road routes and building colours are separate display groups. Also turn off that vehicle’s building colours or All building colours.

H hides the Creator interface, including vehicle labels. G hides only the controls and leaves labels visible. With either option, road routes and building colours in the world remain according to their own switches.

First turn off all road routes and building colours, check any other visible information, then press H. H alone is not enough for a completely clean city view.

Press the same key again: H for the whole UI, G for the controls. Esc first restores hidden UI before opening the pause menu.

The tool pauses on focus loss and stops camera input. Return to the game and restart playback. Also check whether the UI has been restored.

The switches for all labels, routes or building colours establish a shared group state. A mixed selection is unified, rather than each vehicle’s setting being inverted independently.

There is no built-in MP4 export. Capture the game image with an external recording application and check the resulting file afterwards. You cannot simply rename a replay file to .mp4.

The documented Creator tool has no dedicated screenshot or GIF export. Use the corresponding capture features of your platform or recording application.

There is no Creator export dialog for aspect ratios. Compose with enough space around your subject and choose the crop and output format in your capture or editing application.

An automatic render queue and a camera keyframe editor are not part of this interface. Record several takes of the same section and edit them together afterwards.

Hiding the UI does not hide the mouse pointer. Check whether your capture application includes the cursor and adjust that option or the cursor position.

The tool does not provide a separate audio stem export. The recorded mix depends on game and capture settings. In particular, check that the microphone or other desktop sources are not being included unintentionally.

Many steps check that an action was actually performed. Pressing a camera key is not enough when visible movement, speed within the requested range or a playing shot is required. Read the task and fulfil it within the enabled area.

The tutorial offers a skip option. The complete controls overview remains available as help, and the tutorial can be restarted from scene selection.

That help button belongs to the Creator scene interface. A personal day replay does not necessarily show the same introductory help. The controls chapters in this wiki also serve as a reference for it.

Keep the original file. Note the exact message, version and how the replay was created. Check with a freshly completed day whether only this file is affected. Do not alter archive contents to bypass validation.

Compare it with The small loop. If that works, note the affected scene and time. Determine whether the problem is a loading error, a visual issue or a low frame rate; these observations help narrow down the cause.

Game version and Steam branch if applicable, scene or personal day, vehicle number, playback time, perspective and attachment switches, exact steps, expected and observed results, and the error message word for word. If useful, add a short clip and details of display and capture settings.