janine
November 18, 2024, 4:20pm
2
Hi @qhl , welcome to the community!
Thank you for the bug report. I wonder if this is similar to a post from another user:
Dear Cesium Team,
We are currently using Cesium version 2.6, and everything was running smoothly. However, after upgrading to version 2.10, we encountered some unexpected issues. The specific behavior is as follows:
When we added a WMS RasterOverlay to a CesiumWorldTerrain, everything worked fine.
However, after adding a CesiumPolygonRasterOverlay to the CesiumWorldTerrain, the texture rendering for the previously added WMS RasterOverlay became incorrect.
If we remove the CesiumPolygonRasterO…
Can you please confirm the version of Cesium for Unreal you’re using? It’ll help to have this so we can confirm if they’re the same bug. In any case, I’ve opened a Github issue below so that we can track this problem.
opened 04:19PM - 18 Nov 24 UTC
bug
Reported on the forum here:
- https://community.cesium.com/t/cartographicpolygo… n-clipping-cause-terraintile-rendering-abnormal/36628
- https://community.cesium.com/t/cesiumworldterrain-with-multi-rasteroverlays-rendering-error/36636
I was able to reproduce this myself in UE 5.3, v2.10.0 by doing the following:
- In CesiumForUnrealSamples, go to 02_CesiumMelbourne.
- Add the WMS overlay from this [Sandcastle](https://sandcastle.cesium.com/?src=Web%20Map%20Service%20(WMS).html) to Cesium World Terrain, with key Overlay1.
- Zoom out and go to an area where the WMS is showing (over some of the blue dots). Rebase the georeference origin for convenience.
- Add a Cartographic Polygon over the area rendering the WMS. Then add it to a Polygon Raster Overlay on Cesium World Terrain.
You'll see some weird glitchy artifacts in the area affected by the polygon. When you remove the WMS, the artifacts won't disappear right away, but you can refresh and the clipping will appear as normal.
![image](https://github.com/user-attachments/assets/386de257-d627-4114-bef3-8c6e0aa04ef5)
For curiosity's sake, I tried it the other way around, by adding the WMS after the polygon overlay. The polygon clipping works, but the WMS shows up as this blocky blue gradient over a lot of the tiles. 🤔
![image](https://github.com/user-attachments/assets/4d47aa13-df6c-42fe-b72b-97b7df296d47)
I have not tested this, but this reportedly happens as far back as v2.8.0. The behavior works as expected in v2.6.0. It might be prudent to check if this happens with v2.7.0 -- that release introduces some CesiumPolygonRasterOverlay bugfixes, as well as custom ellipsoids.