Tweet
I have a region setup in the VFB in Max. When I render it only renders the region (of course). When I export to .vrscene and render with standalone it renders without the region enabled. Also, when I export to Deadline it renders without the region enabled. Is there a way to force it to use the region I already set in the Max VFB?
The docs say:
-region=x0;y0;x1;y1 – Sets а region to render. The integer values are in pixels, relative to the upper-left corner of the image. A region might be specified in the .vrscene file itself and it will be used in the rendering, unless the -region flag is used to override it or the -region=none flag is used to disable it.
-region=none – Ignores any region specified in the .vrscene file
However I guess the region is not being embedded in the .vrscene file. I guess I should try Deadline' region support. I had assumed that only work in Max and not tested it with Standalone... EDIT: Not assumed. Saw that that entire Tiles tab is disabled. So there seems to be no built in support.
Thoughts? Thanks.
The docs say:
-region=x0;y0;x1;y1 – Sets а region to render. The integer values are in pixels, relative to the upper-left corner of the image. A region might be specified in the .vrscene file itself and it will be used in the rendering, unless the -region flag is used to override it or the -region=none flag is used to disable it.
-region=none – Ignores any region specified in the .vrscene file
However I guess the region is not being embedded in the .vrscene file. I guess I should try Deadline' region support. I had assumed that only work in Max and not tested it with Standalone... EDIT: Not assumed. Saw that that entire Tiles tab is disabled. So there seems to be no built in support.
Thoughts? Thanks.
Comment