@jdultra/threedtiles 13.1.6 → 13.1.7

package/README.md

@@ -648,52 +648,3 @@ you'll want to avoid updating every single tileset on every frame.
 #### Mobile performance 
 just a note because this is valid for any heavy webgl app. mobiles throttle automatically when it deems the app heavy.
 if you control frame-rate manually by only doing updates and renders at 30fps, mobile apps will run more smoothly because the automatic throttling, which is very un-smooth, doesn't kick in as much.
-
-### Memory
-This is especially important for iOS that limits the memory per tab quite harshly and doesn't allow growing the memory allocated to a tab.
-
-Once a mesh is loaded, the mesh and texture data stays in CPU memory which isn't necessary unless one intends to modify it.
-A nice trick is to allow this data to be garbage collected. However, three.js doesn't have API for this and the internal references are hard to find but this code
-seems to free a limited amount of memory:
-
-```
-const tileLoader = new TileLoader({
-        ...
-        const previousOnAfterRender = mesh.onAfterRender; 
-        mesh.onAfterRender = () => {
-            if(previousOnAfterRender) previousOnAfterRender();
-            if(mesh.geometry && mesh.geometry.attributes){
-                if (mesh.geometry.attributes.position) {
-                    mesh.geometry.attributes.position.array = undefined;
-                    if (mesh.geometry.attributes.position.data) {
-                        mesh.geometry.attributes.position.data.array = undefined;
-                    }
-                }
-                if (mesh.geometry.attributes.uv){
-                    mesh.geometry.attributes.uv.array = undefined;  
-                    if (mesh.geometry.attributes.uv.data) {
-                         mesh.geometry.attributes.uv.data.array = undefined;
-                    }
-                } 
-                if (mesh.geometry.attributes.normal) {
-                    mesh.geometry.attributes.normal.array = undefined;
-                    if (mesh.geometry.attributes.normal.data) {
-                        mesh.geometry.attributes.normal.data.array = undefined;
-                    }
-                }
-            }
-            if (mesh.material && mesh.material.map) {
-                mesh.material.map.mipmaps = undefined;
-                if (mesh.material.map.source) {
-                    mesh.material.map.source.data = undefined;
-                }
-            }
-
-            mesh.onAfterRender = previousOnAfterRender;
-        }
-    });
-```
-
-Be sure to call this in the mesh onAfterRender callback to make sure the data is already on GPU.
-
-Depending on the mesh and texture type, different properties might hold data to be nullified so it can be garbage collected. It's up to the user to debug and see what geometry or material properties hold references to large data.