-
Notifications
You must be signed in to change notification settings - Fork 470
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
Reference glTF 2.0 spec #94
Comments
What is the status of b3dm? If there is no immediate plan to adopt GLTF 2.0 then perhaps this spec should be considered abandonware and a deprecation notice added. |
@nitrologic Cesium's 3D Tiles renderer implementation supports glTF 2.0 - and converts glTF 1.0 to 2.0 on-the-fly for backwards compatibility - this issue is a reminder to update the b3dm/i3dm spec before we put the finishing touches on it for a final 1.0. |
Thanks for the prompt reply Patrick. I have yet to see a 2.0 based b3dm in the wild so was concerned my failure to create a conforming asset was due to not reading the fine print which currently states "Batched 3D Model uses glTF 1.0 with the KHR_binary_glTF extension." |
I believe the same tilesets in the Cesium repo are glTF 2.0. |
Exactly which tilesets in what repo? |
I actually don't think they have been updated yet. I have a branch in |
Resolved in #301 |
For example, update here and elsewhere to be glTF 2.0, not glTF 1.0.
glTF 2.0 updates: KhronosGroup/glTF#605
Also consider if there are any other glTF extensions, like unsigned int indices, that we want to include.
The text was updated successfully, but these errors were encountered: