You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for all the work you've put in Threebox. It has been very useful for an internal app we're building.
We're trying to implement a section tool, and it appears that we cannot add a clipping plane (THREE.Plane()) to tb, via tb.Object3D() or tb.add(). I'm assuming it's because a THREE.Plane is more of a math concept than a 3D geometry.
This has the unfortunate consequence that the clipping plane does not pan with the rest of the view. So when the map is panned, the clipping planes start cutting other things.
Is there any ways around this in tb, where the clipping plane would stay fixed ?
Hi Jesus,
Thanks for all the work you've put in Threebox. It has been very useful for an internal app we're building.
We're trying to implement a section tool, and it appears that we cannot add a clipping plane (THREE.Plane()) to tb, via tb.Object3D() or tb.add(). I'm assuming it's because a THREE.Plane is more of a math concept than a 3D geometry.
This has the unfortunate consequence that the clipping plane does not pan with the rest of the view. So when the map is panned, the clipping planes start cutting other things.
Is there any ways around this in tb, where the clipping plane would stay fixed ?
You can see a very simple reproduction of that issue here :
https://codesandbox.io/p/sandbox/vue-threebox-sample-forked-qtf92k
The text was updated successfully, but these errors were encountered: