You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when a DRACO encoded glTF file is loaded with the GLTFLoader, the DRACO decoder will only be fetched after all of the mesh and texture data has been loaded.
For non-embedded glTF files would it be better to prefetch the DRACO decoder using THREE.DRACOLoader.getDecoderModule() after loading the .gltf file, causing the DRACO decoder to load in parallel with the mesh and texture data? My thought is that this would decrease the perceived load time for the user, while also allowing the DRACO decoder WebAssembly file to compile while the rest of the model assets are loading.
The text was updated successfully, but these errors were encountered:
Currently when a DRACO encoded glTF file is loaded with the GLTFLoader, the DRACO decoder will only be fetched after all of the mesh and texture data has been loaded.
For non-embedded glTF files would it be better to prefetch the DRACO decoder using
THREE.DRACOLoader.getDecoderModule()
after loading the .gltf file, causing the DRACO decoder to load in parallel with the mesh and texture data? My thought is that this would decrease the perceived load time for the user, while also allowing the DRACO decoder WebAssembly file to compile while the rest of the model assets are loading.The text was updated successfully, but these errors were encountered: