Not the case with Potree

[akharroubi]

Thank you for making this project available,

In fact I have a remark on the fact that the nodes are loading continuously and remain in the scene even if the camera does not point towards them, which causes an overload of the memory by points will not be visible to the user ... which is not the case with Potree

thank you in advance
@tentone

[tentone]

Hello

Thanks a lot for this reamark this is something that i have to fix.

Thanks a lot

[Albanbrice]

Hello,
Thanks a lot for this adaptation. I do not know if it's related to the same issue, but I found out that the same pointcloud displayed in both Potree and Potree-core is pretty much laggy with the last one, not only the frame rate of the 3D itself, but also all the other interactions I overlayed over the 3D canvas (such as very simple CSS animations, onMouseover, etc).
Is there any idea how to fix this issue? Thanks in advance.

[yohnniebabe]

Hi,

Yeah experiencing the same lagging issue as well, the same point cloud rendered in potree is not laggy, but when run using potree-core it is choppy and slow.

[lymperis-e]

Hi,

Yeah experiencing the same lagging issue as well, the same point cloud rendered in potree is not laggy, but when run using potree-core it is choppy and slow.

Late to the party but I made an observation which might be useful to some: using a plain threejs scene, and adding potree-core in the render loop I also experienced very laggy behaviour when zooming/panning/rotating. You have to explicitly define a three.Controls object and call its update() method in the render loop.

const threeControls = new OrbitControls(
      threeCamera,
      threeRenderer.domElement
    );


// render/animation loop
...
threeControls.update();
threeRenderer.clear();
threeRenderer.render(threeScene, threeCamera);
...