@Kevin_Ring and Cesium Team,
How can I ensure that the Cesium Tiles show up when rendering a 360 Panoramic shot inside of Unreal Engine 5 using the method shown in this video (Using Extra Render Passes and Panoramic Rendering inside of Movie Render Queue)? Currently, the Cesium Terrain disappears in the final render, while everything else remains- looking for some help here, thanks!
@M_T,
The Movie Render Queue is a bit difficult to work with because it goes outside the normal Unreal rendering, meaning it’s difficult or impossible for Cesium for Unreal to automatically get access to its camera parameters, which are necessary for 3D Tiles selection. There are a few more details here:
It may help to turn off frustum culling on the tileset, and set the culled screen space error to the same as the normal SSE (16).
You may also find it helpful to use the Cesium Camera Manager Actor to manually provide cameras to drive tile selection.
But the short version is that this isn’t a use-case we’ve explored before, so you’ll have to play around yourself and see what can be done to make it work. Including, potentially, making changes to the Cesium for Unreal plugin.
Kevin
(Settings)
Aw man. I just did an hour long 8K Pano render just to have the Cesium terrain still not show up… same results as when frustum culling was enabled.
(Viewport)
(Render Section)
Where is some info to use this Cesium Camera Manager you speak of? Internet searches aren’t obvious with answers (currently), could you point me in the general reading on how to utilize it properly for an application like this?
Thanks!
Hi @M_T ,
Edit: I was typing out instructions on how to use the Cesium Camera Manager, but it stood out to me that you are using the LOD transitions option. Unfortunately, that is not supported for movie rendering currently. If you disable that, Kevin’s original suggestion may help.
The Cesium Camera Manager might still be necessary though:
As Kevin mentioned, we attempt to pick up common camera types such as player cameras, VR eyes, and scene capture actors, but it isn’t exhaustive. This was the PR that originally introduced the Cesium Camera Manager feature: Blueprint API for Registering Custom Cameras by nithinp7 · Pull Request #734 · CesiumGS/cesium-unreal · GitHub
There are some screenshots in the link showing how to use the Blueprint API to register and update custom camera views with Cesium tilesets. You will need to access camera information from the panoramic renderer and feed it to the Cesium Camera Manager as the panoramic camera is sweeping around. I’m not sure about the details of how to retrieve that camera information though, since I’m not familiar with the panoramic renderer - but hopefully it shouldn’t be too difficult to figure out.
-Nithin
I might be your salvation here. I had the same issue, and came to this forum with no success… after thinking about it, I came to “maybe ue5 isn’t giving the tiles long enough to load”… I was right, and the solution is in movie render queue. click on the +setting button, then antialiasing. Inside of antialiasing, theres an area under advanced with “render warm up count” and “engine warm up count”. I made both 500 (you can make it more if needed), which gave it time to load the cesium tile set, then render correctly. no blueprint mods, just render queue. Hope this helps, maybe finally I can give back to the unreal community.
Now to find out if anyone has found the solution to why all of a sudden we see the messed up half loaded CESIUM tiles floating in the sky in the reflections of my building windows when using path traced rendering…
