-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Support for glTF 2.0 #4009
Comments
Copying from #605 to track progress in Cesium.
|
@pjcozzi Do we want to completely pull support from |
Remove it completely from glTF since it was never used, but do not remove it from the lower-level Cesium renderer. |
1.1 spec pull request: KhronosGroup/glTF#784 |
I tested the display of the tutorial model of glTF 1.1 with Cesium 1.29.
|
Thanks @cx20. glTF 1.1 support is not integrated into mainline Cesium yet |
I confirmed that the model of glTF 2.0 will be displayed by Cesium 1.36 (not 1.35). |
@cx20 very nice, thanks for checking so quickly (also, I think you mean 1.36)! |
gltf-pipeline roadmap for glTF 2.0 - CesiumGS/gltf-pipeline#330 |
@lilleyse can you please update the above tasklist? Some of the items are finished. |
@lilleyse can you please update the tasklists in this issue? What's left? |
Updated the task list. The major things left are:
|
|
@ggetz could you please update the tasklists above? Perhaps we can close this and submit/update other issues. |
I guess this can safely be closed since a while :) |
Changes from 1.0 to 2.0 are here: KhronosGroup/glTF#605
The 2.0 spec still needs a bit more work, but is converging quickly.
Cesium / glTF Pipeline / COLLADA2GLTF / 3D Tiles updates
scene
isn't required, The glTF.scene should be optional #4793Separate gltf-pipeline pull request to use 2.0 internally for each stage.(part of the gltf-pipeline changes above)TBA
[ ] Update Cesium, gltf-pipeline, obj2gltf, COLLADA2GLTF, and sample models to use final version of KHR_materials_common, see Finishing KHR_materials_common KhronosGroup/glTF#632.The text was updated successfully, but these errors were encountered: