It would be nice if the 6.1 region assembler used the bounds of the regions for the assembled EXR instead of the entire EXR. The entire EXR creates a very heavy file.
Hey Gavin,
Thanks for the suggestion, I’ll pass this along to the devs.
Cheers,
I’d like to make sure that I understand your request. I assume that this is related to the OpenEXR Display Window (rectangle that is displayed) and Data Window (rectangle that contains actual pixel data). I also assume that you are using the Draft Tile Assembler.
In your case, once you have combined all of the tiles, is the combined Data Window smaller than the Display Window?
Preserving the OpenEXR Data Window is on our wish list for Draft. I’ll add a note that we should make sure that it works in the Draft Tile Assembler too.
Correct. When you perform a regular render in Max it’ll by default crop the data-window to be a subset of the display window. It would be nice if the assembled EXR was able to similarly minimize the size of the data window for fast nuke loading and storage savings.
++1