Hey guys,
has been a while since we are deep in development
As I thought this is just a material trick with the opacity mask of PolygonRasterOverlays. The collision actually does get cut. But how does the collision cutting actually work?
Iām highly interested since we probably enhance this for our own needs. I will for sure share the outcome if its worth.
What youāre seeing is the result of a setting on CesiumPolygonRasterOverlay called Exclude Selected Tiles. Whenever a tile falls completely inside the polygon, it is excluded from loading, hence why the mesh and its collisions are missing.
However, when a tile falls partially inside the polygon, the plugin still has to load the entire tile, and thus creates a full mesh for it. We can achieve a clean polygon cut using the opacity mask, as you noted, but thatās only a visual effect. To remove collisions from the tile, weād have to do an extra step of cutting the geometry from the tile itself, and that has yet to be added to the plugin.
I hope that explanation makes sense ā let us know if you have any follow-up questions!
Hey Janine,
thank you. Iām working with these polyogons for a good while already.
Thatās exactly the point I donāt get - How can the Polygon actually cut collision (even though the Tileset is not fully inside and itās just the opacity mask
(I did study all the Cesium materials etcā¦))
We do already work for years with this ācollision cutting featureā ā We place glb/glTF on Cesium3DTiles and cut the geometry to be able to go in the basement e.f.