Skip to content

Suggestion: Scaling Timelapse #56

Description

@DeadlyDad

Considering the 8-hour demo took 36GB worth of screenshots, a 180-hour run would require its own hard drive with the current technique. To get around this, I suggest adding an options to take screenshots A) every X structures placed (selectable minor structures--e.g. belts/rails/inserters/etc.--and major structures--e.g. refineries/assemblers/storage tanks/etc.) and/or B) every time the total number of structures (minor and/or major) increases by X%. The latter would have more screenshots taken at the very beginning when each structure is a larger percentage of the total and relatively few near the end. When compiled, this would naturally make the video speed up over time until it freezes with the rocket launch. (...and the camera REALLY should follow the rocket until it disappears!) This would make for a video that gets more and more exciting the longer it goes while minimizing the needed frame storage space.

Also, I would add an option to darken the area in the current frame that is identical to the previous one--barring belts/inserters/etc.--to highlight changes between the two.

Does that sound reasonable?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions