Personal replays, timeline & files

A replay reconstructs saved movement and state. It does not recalculate a new tour with your current rules every time it plays. Seeking restores the recorded moment, allowing the same halt, corner or incident to be viewed repeatedly.

Reassigning orders, choosing another incident outcome, buying vehicles or resuming a playable run from a past moment are not replay operations. Play another delivery to obtain a different result. A replay is also not a save game that restores a playable run.

Playback uses a shared timeline adapted for filming. Very fast movement from the management game can be stretched, and brief fleet-wide pauses can be made easier to read. The displayed replay duration therefore need not match the time originally spent at your computer. Vehicles, stops and events remain aligned to the same timeline.

Closely spaced stops may occupy almost the same screen position. Repeated clicks cycle through such a marker cluster so individual events remain reachable. Read the detail line to identify the selected event.

A marker identifies the recorded stop event, not automatically the beginning of an attractive approach shot. Seek back slightly and play again. Leave enough lead-in for the camera movement and subject to develop before the main moment.

Seeking leaves the scene paused. If nothing moves after a click, press Space to continue. Attempts to seek beyond the beginning or end are limited to the available timeline.

Camera speed and playback speed are independent. Camera speed changes how quickly you move your viewpoint. The 0.25× to 4× setting changes the scene’s passage of time. To obtain gentler camera movement, you do not necessarily need to slow the vehicles down.

Completed recordings are saved in “CreatorReplays” inside the local Cargo Tempo data directory. A typical Windows installation uses %USERPROFILE%\AppData\LocalLow\koppwerk\Cargo Tempo\CreatorReplays. Finished files end in .ctreplay. A media player cannot open them as though they were MP4 videos.

Temporary files or folders ending in .recording or .incomplete may exist while recording and finalisation are underway. They are not substitutes for a completed .ctreplay file. Renaming their extension does not repair an interrupted recording or supply missing data.

For a backup, copy the finished file after saving has completed. Do not overwrite your only original during troubleshooting. The current visible interface provides neither a general import/file picker nor a normal entry for browsing all old replays. The existence of a saved file alone therefore does not constitute an offered reopening workflow.

Opening a replay checks the file format, build identity and content. The same visible version number is not always sufficient: a newly created build or changed game resources can also change compatibility. A replay from another installation or an older release is not automatically compatible.

“This replay belongs to another game version.” indicates a compatibility mismatch. Use the original corresponding release if it is still available to you, or make a new recording in the current build. Do not edit metadata to bypass the check.

“The required game data does not match this replay.” indicates missing or mismatched resources. Check that your installation and selected Creator branch are complete. Bundled scenarios are prepared for their particular build; their availability does not imply compatibility with personal files.

Recording has protective limits, including two hours of recorded duration, two million movement records, 250,000 events and 512 MiB of expanded data. Loading also limits the packed file to 256 MiB. These are technical upper bounds, not a promise that every recording can reach them: a dense fleet may exhaust a data limit sooner than a short single-vehicle day.

The Creator menu has no repair function for incomplete recordings. For a repeatable problem, report the version, time, scenario or day, vehicle count and exact error text.