qiangge

 function destroyOldObject(objSelector) {
                var objNames = PzLib.retrieveObjectNames(objSelector);
                for (var i = 0; i < objNames.length; i++) {
                    var objName = objNames;
                    if (!objName) continue;
                    var obj = PzLib.getObjectByName(objName);
                    if (!obj || !obj.parent) continue;
                    obj.parent.remove(obj);
                    // _pGlob.objCache = {};
                    _pGlob.objCache = new Map();
                }
            }

Thank you, it has been fixed

Here’s a comparison. Using the same code, calling Three.js and v3d.js produces different effects. I tried to change all the shader fragments I could find to be the same, but I’m not sure why this happened

kdv wrote:

No. I don’t know the reason I just see that when the scene camera is moving the framerate drops to ~20 fps

Thank you for your video. I think the problem lies in the hotspot puzzle, which is very performance consuming for large amounts of data. I will try to optimize it
Also, how does your YouTube video display directly? I tried embedding it in an iframe and it displayed the code. Can you demonstrate it

visualizer wrote:

interesting!
Do you have a working link to check?

Hi Visualizer, Working Link