I hope this message finds you well. I am working on a clipper tool that functions similarly to the one demonstrated here:
However, I have encountered an issue with certain models. While the main mesh is clipped accurately, some objects remain unaffected by the cropping effect. Depending on the position of the clipping tool, these objects either fully appear or disappear, as illustrated in the image below.
In this second case, the floor plane is immediately cropped by approximately 20% at the top (when start clipping),
and about 30% at the bottom only partially shows or disappears (when finishing clipping), rather than being evenly clipped.
Has anyone experienced similar behavior? I would greatly appreciate any insights or suggestions you might have to resolve this issue.
I converted the IFC file using the Cesium Ion web interface,
and I am currently utilizing the built-in CesiumJS ClippingPlane (“Cesium.ClippingPlane”) in my project.
Hi @kharel.valtingojer ,
Thanks for that additional information.
Knowing that, can you possibly provide an example using our sandcastle tool https://sandcastle.cesium.com/ that reproduces the issue. This will make it easier for us to continue helping with investigating and debugging.
I tried this out by tiling the given data sets and in a small test sandcastle, and could not reproduce the issue for now:
In this second case, the floor plane is immediately cropped by approximately 20% at the top (when start clipping),
and about 30% at the bottom only partially shows or disappears (when finishing clipping), rather than being evenly clipped.
Does the “second case” refer to the DigitalHub_FM-HZG_v2.ifc (Heizung, heating system) data? I also tried it with the other data sets, and it seems to cut off the model elements cleanly. (I had suspected that this issue might be caused by Wrong bounding volume computations for model · Issue #12108 · CesiumGS/cesium · GitHub - that’s why I was curious).
Thank you so much for looking into this! Yes, DigitalHub_FM-HZG_v2.ifc was indeed the one giving me trouble.
I’m really impressed that your sample doesn’t seem to exhibit the issues I’m encountering.
Would you be so kind as to share your Sandcastle code sample? I believe it would be incredibly helpful in understanding where I might be going wrong.
I noticed that not only is your clipping more effective, but the plane’s positioning is also far more accurate and perfectly aligned with the mesh orientation.
I’m optimistic that with your example, I’ll be able to pinpoint the discrepancies in my approach and achieve the desired results, and return here to point out the key differences in approach that I find, as it can be helpful for someone else in the future
I did send you a link to that sandcastle via private message (it’s a bit messy, and contains tokens for the tiled versions of the assets in my account, so it may be better to not post this publicly).
If there are any insights or conclusions from that, I’ll definitely post that here (publicly).
