Replies: 1 comment 1 reply
-
Hi @zrshannes! I've converted this issue into a discussion. I would recommend implementing your extension by using one of the existing extensions as a reference. Another material extension that includes textures, like I would note that the JSON structure you've included would be a bit non-standard, usually a goal of extension authors is that if the extension were to disappear (and all its properties added to the base material object) the names would still make sense. Instead, consider... {
"materials": [
{
"extensions": {
"MYPREFIX_materials_lightmap": {
"lightmapIntensity": 3.14,
"lightmapTexture": { "index": 0 }
}
}
}
]
} ... which I think you may find easier, as the |
Beta Was this translation helpful? Give feedback.
-
I have a material with texture, texCoord, and intensity.
i wrote myself a extension for gltf-transform so "lightmap" Material will be read and writeable.
write:
read:
when i process a glb the processed glb is missing the texture, buffers etc.
material is copied and image is also present and converted.
what am i missing to handle the given material correctly?
Beta Was this translation helpful? Give feedback.
All reactions