Feature: Add scene variables 'image_start_column', 'image_end_column, 'image_s… #311
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've got a large scene that uses much more memory than I have installed in my machine. My initial solution was to render parts of the image at a time, using +SC/+EC/+SR/+ER and put
Declare
s on the command line to indicate what these parameters are set to. The scene file used this information to omit objects that aren't needed, freeing up memory.I decided it would be beneficial to have variables available that automatically tracked these command line parameters, as it would simplify the process and reduce errors when adding the command line options. It is a simple change with no side effects that I have found, and probably useful to others working with large scenes.