Draco UV Issue
See original GitHub issueHi,
We’ve previously operated a 3dsMax -> glTF
workflow but changed to Blender
recently. The Draco compression that came with the Babylon exporter for 3dsMax
produced a working and optimized result, however the in-built glTF exporter for Blender
is not working for us when we check the “Draco mesh compression
” box in the glTF export UI. We can’t open the model due to various errors.
We’re therefor very curious about what Draco version that’s being used with Blender 2.8 so that we can add support for it with our app.
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (3 by maintainers)
Top Results From Across the Web
Multiple UV Sets Getting Lost With Draco Compression
We are seeing strange behavior when dealing with Draco compressed GLTF files that use multiple UV sets. When compressing with Draco, any UV...
Read more >Misaligned UV coordinates after Draco compression
However, when dealing with a lot of objects this manual process may cause some issues as it will require a lot of manual...
Read more >Observations of Diffuse Ultraviolet Emission from Draco - arXiv
Abstract: We have studied small scale (2 arcmin) spatial variation of the diffuse UV radiation using a set of 11 GALEX deep observations...
Read more >Conquest Journals Harry Potter Draco Vinyl Stickers, Set of 50 ...
✔️ High Quality - These officially licensed stickers are made of high grade vinyl and sealed to provide superior waterproofing and UV protection....
Read more >Export gLTF 2.0 (draco compression not including multiple ...
glb), include selected objects and enable Compression under Geometry. If you view you exported file with https://sandbox.babylonjs.com/ you should see the issue ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I don’t think the version of Draco is related here. The Draco file specification is standardized, and does not simply change without warning. The decoder in my viewer is pretty old, too, and wouldn’t have any recent bug fixes. It sounds to me like https://github.com/KhronosGroup/glTF-Blender-IO/issues/993 is causing your issue.
@donmccurdy do you happen to know what version of Draco your r116 viewer is using? I think that’s interesting in regard of the bug i am pursuing, as r117 and the newest version of Draco might have these bugs fixed. Thank you so much