THREE.Cache enabled for repeat loader requests vs. disabled for mid-session asset freshness
An application uses TextureLoader and GLTFLoader to pull assets into a three.js scene, and the art pipeline can publish updated textures or models while users remain connected. The documented choice is between enabling THREE.Cache to short-circuit repeated FileLoader requests for the same URL, or leaving it disabled so later loads are not blocked by the in-m
threejs