Issue · demo-history · official
Nightly Reports and Reloading — Demo Archive
Last checked: · UPDATE 049
Direct answer
Historical Demo data, not a verified 1.0 walkthrough. UPDATE 049 preserves nightly logs and reports after reloading a save. That makes them useful for comparing an overnight outcome with the setup you left, without assuming the public patch number identifies every minor binary revision.
Historical Demo evidence boundary
The mechanics below were documented for Demo 049, not independently retested in release 1.0. Keep their original source dates and numbers separate from current prices, scenarios and hotfixes. Check the updates timeline before applying an old workaround to a release save.
Use the report to separate outcomes
Note the machine inputs, power and intended service before sleeping, then compare the reported result. Keep a short record of what changed between nights so a failed production cycle is not confused with a missed purchase or exchange.
| Current change | Logs and reports persist after reload |
|---|---|
| Ultrawide fix | Calendar and nightly report no longer open oversized after loading |
Keep a baseline outside risky tests
The patch also improves save resilience and loading performance, but no save system is a substitute for an untouched backup before imports or unusual tests. If report contents vanish or differ after reload, capture the before-and-after state and the installed build rather than repeatedly overwriting the same slot.