Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gltfpack: EXT_texture_webp support #536

Open
kzhsw opened this issue Feb 9, 2023 · 2 comments
Open

gltfpack: EXT_texture_webp support #536

kzhsw opened this issue Feb 9, 2023 · 2 comments

Comments

@kzhsw
Copy link

kzhsw commented Feb 9, 2023

Spec here.

Model before:
webp_demo.zip

{
"textures":[{"sampler":0,"extensions":{"EXT_texture_webp":{"source":0}}}],
"extensionsUsed":["EXT_texture_webp"],"extensionsRequired":["EXT_texture_webp"]
}

Model after:
webp_demo_gltfpack.zip

{
"extensionsUsed":["KHR_mesh_quantization","KHR_texture_transform"],"extensionsRequired":["KHR_mesh_quantization"],
"textures":[{}]
}
@kzhsw
Copy link
Author

kzhsw commented Mar 21, 2023

A similar thing is the proposal of EXT_texture_avif. Or maybe gltfpack can just keep all unknown extensions of texture for maximum compatibility.

@zeux
Copy link
Owner

zeux commented May 23, 2024

This requires jkuhlmann/cgltf#248; I'm not very interested in implementing this myself and gltfpack can't encode webp images without external dependencies anyway so the best it can do here is to preserve inputs as is, but if the linked issue gets implemented I can take a look at this.

Keeping unknown extensions doesn't work because image files need to be parsed for material transparency optimization.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants