In a normal render, the OWL 360 Camera will render the complete output in a single job which at resolutions below 8K increases rendering speed substantially.
However, Unreal has a limit of around 6kx6k per 'face' rendered in Movie Render Queue around which it will give a VRAM crash.
This means that for renders 12kx12k and above it is essential to use tiling.
In practice from around 8kx8k tiling is useful, especially in heavy scenes where VRAM allocation is high.
To add tiling to your render:
N.B. When you do tiled renders, you will only output final frames whenthe tiles for ALL your frames have been completed. For this reason, you may want to split your sequence into sections - see below for a guide.
- Ensure that your Output Settings (Frame Rate, File Directory) for your final render are all set. All the tiles will use these settings so they cannot be changed later on unless you want to generate a new set of tiles.
- Go to the High Resolution Renders section in the OWL Movie Render Queue settings:
- There will be two phases to the render:
- Generation of the intermediate files which contain the metadata for each of the tiles.
- A 'stitching' phase which joins together the tiles and creates a the final render.
- When creating your render please set:
- Intermediate Output directory: This is the file path for where your intermediate files will be saved. These files will be large and should be saved on a hard drive. They will have the extension .OWLI and cannot be viewed as images.
-
Intermediate File prefix: You can change this if required for your filing.
- Job Name Prefix: You can change this if required for your filing.
- Tiles: This means the number of horizontal and vertical sections.
- If it is set to 1:1 that means you will render each of the 6 cube faces separately and then stitch.
- If it is set to 1:2 that means you will split each of the six faces into two vertical tiles.
- You can keep increasing the number of tiles as your render size increases. We recommend to keep each tile below 4kx4k to ensure no VRAM issues.
- Tile Overlap Percent: This is a blend between tiles to soften the transition between them and remove visible seams. This should be kept at the default of 5 for most cases.
- Delete Intermediates After Stitch: This will delete the intermediate files mentioned above.
- If you are just doing a single render then you can select this to save file space.
- However, if you want to use the stitch phase to downscale your render or play around with different resolutions then you should have this unticked as you will use the intermediate files to do so.
- Max Concurrent Stitches: This is an important setting for the final stitch phase as stitching multiple faces is RAM intensive.
- For higher resolutions (+16kx16k) or intensive scenes reduce this to 1.
- For lower resolutions you can experiment with increasing this. 5 might be possible.
- When you click 'Generate Jobs' you will see all of your tiles appear in your Movie Render Queue output like this:
- You should save this queue as an asset in your content browser like this:
- Notice that the original render is disabled (because that would be a render without tiles and so is too high resolution for your machine.
- Each of the jobs represents the rendering of an individual tile.
- The final job 'FinalStitch' is the stitch phase which will create your final render.
- You should save this queue as an asset in your content browser like this:
- You shouldn't modify any of the tile jobs because that will stop the job working.
- However, you can modify the 'FinalStitch' job or add additional jobs if you want:
- To downscale your final render: Do this if you want to render the tiles at a higher resolution but output your render at a lower resolution (this can give a higher level of detail and so a better looking render).
- If you want to output at multiple resolutions, you can do so by adding a second Stitch Job. To do so:
- Go to your Final Stitch job, right click and select 'Duplicate':
- Now click the config button to open the MRQ settings and in the OWL Stitch section reset the Resolution you want:
- Don't change any other settings (the intermediate file path etc. must be the same).
- Go to your Final Stitch job, right click and select 'Duplicate':
Rendering Sections of Tiles
If your render gets interrupted, the final stitch phase will not be initiated but you don't need to restart the render from the beginning, you can start from the frame where the render stopped.
To do so, you need to check in your Intermediate File folder (see above) what was the last frame that you rendered:
- Go to your intermediate file folder (this is the repository you selected above in step 4.1 and find the last file rendered.
- The file name is formatted as follows: LS_02_SU_020_E_c_000.fm_000002.sv_00.e_0.f_0.t_0-0
LS (Level Sequence name), c(camera), fm (frame),sv(Scene view, any PP passes)e(eye),f(Face),t(Tile). - Check the eye, face and tile number to know which tile the job stopped at and then check the frame number of that tile.
- You can now reload saved queue from step 5.1 which will bring up all the tiles.
- You can delete or disable all the tiles above the one where the job stopped:
- Now open the config for the tile where the job stopped and go to Output in settings and in Custom Start Frame, start the render from the frame after the final one rendered:
- Custom End Frame can either be blank or should be the last frame in your sequence.
- Now you can Accept and go back to the main render page and start your render again.
- This will render any remaining tiles and also complete the stitch phase.
Splitting Large Renders into Sections
Rendering using tiles will only produce final frames once ALL tiles have been completed. This means that if there is an issue with one of the tiles then you need to start the render again from the missing tile.
To avoid this, you can render the tiles in sections of frames as follows:
- Select your tiling settings in the OWL 360 Rendering section as normal, but don't click 'Generate Jobs':
- Go to Output settings, tick 'Use Custom Playback Range' and select a range of frames to render, for example 0-99:
- Now go back to the OWL 360 Rendering Settings and click 'Generate Job' in the high resolution section:
- This will generate a job only for frames 0-99 which includes all tiles and a final stitch phase:
- Now you can go back to the Output Settings and set another range of frames (for example 100-199):
- Go back to OWL 360 Rendering and click 'Generate Jobs' again and it will create the tiles and final stitch jobs for these frames:
- You can repeat this as many times as you need for your final job.
-
N.B. Remember to save this queue once you have added all these different jobs so you don't have to generate it again!