Hugo Duroux

That would imply to freeze the camera to avoid a rerender of the 2D canvas, no? Or the 2D canvas could be generated without much overweight?

We had the same problem, but the PR has never been merged: https://github.com/xeokit/xeokit-sdk/pull/794

```javascript useDataTextures: { // For this model, enable both LOD and VFC mechanisms targetLodFps: 15, enableViewFrustumCulling: true, }, ``` Does this mean LOD and Culling are dependent on data textures?

The LOD mechanism by @tmarti in https://github.com/xeokit/xeokit-sdk/pull/824 could work very well with this. Instead of always hiding objects, it hides objects only if FPS drops below a defined threshold. It...

Don't merge it now. The sphere geometry breaks with xkt v6 models. Is there a way to create the sphere in performance mode to allow big coordinates?

I read the section plane plugin's code and I didn't see anything special. Do you have an idea about why the sphere created like that doesn't render properly with xktv6?...

Should be good now!

The size of the sphere depends on the distance of the pivot point so we can't keep the geometry. I just fixed a bug where the geometry was constantly recreated...

We don't need a very precise sphere, but we can't reduce the resolution: https://github.com/xeokit/xeokit-sdk/blob/b01f6ddef6e33171dc247a7cced3f001570d2c75/src/viewer/scene/geometry/builders/buildSphereGeometry.js#L72 Is there a reason for these limits?

Is there any impact on the xkt size or loading time?