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
Hi there,
I've tested gltfjsx hoping it would let me do some kind of Level of Detail LOD on my mesh geometries & textures - by chaining multiple Suspense with gradually higher geometry polycount or texture resolution.
My glb scenes are pretty simple, often a single mesh with one or two materials referencing one diffuse/emissive colormap (usually 3d-scan data used as shadeless).
Current export therefore looks like below. Since I'd like to load a low-res texture first, then mid-res, then high res async, I think one way to do it would be to declaratively create a meshStandardMaterial which would reference the map as a texture - see the commented-out portions below. To do this, I would edit the component JSX tree myself in order to create that material and set its map by copying the glb material map.
Rather than doing it myself, would it make sense for gltfjsx itself to export the materials within the component tree this way rather than simply exporting nodes and materials? For example via a CLI flag the user could explicitly ask to explode materials and expose material attributes/properties (type/class like meshStandardMaterial or emissive, maps, params etc). Thanks for the feedback!
Hi there,
I've tested
gltfjsx
hoping it would let me do some kind ofLevel of Detail LOD
on my mesh geometries & textures - by chaining multipleSuspense
with gradually higher geometry polycount or texture resolution.My glb scenes are pretty simple, often a single mesh with one or two materials referencing one diffuse/emissive colormap (usually 3d-scan data used as shadeless).
Current export therefore looks like below. Since I'd like to load a low-res texture first, then mid-res, then high res async, I think one way to do it would be to declaratively create a
meshStandardMaterial
which would reference the map as a texture - see the commented-out portions below. To do this, I would edit the component JSX tree myself in order to create that material and set its map by copying the glb material map.Rather than doing it myself, would it make sense for
gltfjsx
itself to export the materials within the component tree this way rather than simply exportingnodes
andmaterials
? For example via a CLI flag the user could explicitly ask to explode materials and expose material attributes/properties (type/class like meshStandardMaterial or emissive, maps, params etc). Thanks for the feedback!The text was updated successfully, but these errors were encountered: