It *is* scriptable (insofar as you can modify it with a pre-render script). However we can't make it support expressions.
Nope; there are too many options already
#### is dangerous as it is a valid file/directory name character and believe or not, people use it in folder names (we've gotten into trouble for that reason before).
That leaves %0nd as a possible variant, but again, it is somewhat ambiguous as to what should happen. I think it would work best if %0nd is replaced with the first frame that gets rendered in the particular rendering process. For example, if you put something like imap_%003d.vrmap and render frames 50 through 70, you'll get one irradiance map file named imap_050.vrmap that contains the baked map for the entire sequence (frames 50 through 70). Would that work for you?
That would be awesome!
EDIT:
Just to double-check: That means I could just set the autosave filepath to ".../path/to/renderjob/vrmaps/imap.%04d.vrmap", and depending on the framerange of each "chunk", the resulting vrmap file will have a unique name on disk, right?
So:
imap.%04d.vrmap -> imap.0001.vrmap for framerange 1-100
imap.%04d.vrmap -> imap.0101.vrmap for framerange 101-200
...right?
Comment