Our application allows users to generate images and panoramics from a build using MRG (Movie Render Graph). Many of our users can run Lumen well enough at runtime, but run out of VRAM when generating a render, especially a panoramic.
For limiting VRAM crashes while creating an image, we let users enable tiling to reduce the size of any particular batch of work. That mitigates the bulk of issues. We’re also aware of and utilize page to system memory.
For panoramic images, however, we can’t find an equivalent that lets us change the base tile resolution. It seems that increasing the number of horizontal/vertical panes only changes the amount of overlap but not the resolution of any pane.
For example, if we set the target resolution to 10,000 x 5,000, it logs the following:
LogMovieRenderPipeline: Set-up Deferred Panoramic Renderer: DeferredPanoramic Layer: 360 render OutputRes: [5000, 2500] PaneRes: [1250, 1250] PaneCount: [8, 3] bPageToSystemMemory: 0 bAutoExposurePass: 0
If we change the pane count to 10,4, we get the following:
LogMovieRenderPipeline: Set-up Deferred Panoramic Renderer: DeferredPanoramic Layer: 360 render OutputRes: [5000, 2500] PaneRes: [1250, 1250] PaneCount: [10, 4] bPageToSystemMemory: 0 bAutoExposurePass: 0
With no difference in pane resolution.
Is there a way to actually increase the number of tiles in each pane, similar to tiling in a normal render?