[midnightclubbed]

Nvidia are also leaning very hard into USD with their meta- verse project. In that case USD matches requirements perfectly.

glTF 2.0 is widely supported although the quality of that support is variable. The spec is fairly large and every tool that exports glTF does so in a subtly different way.

For instance Blender adds a rotation transform node before every mesh to convert from Y-up (Blender) to Z-up (glTF). Animations run in Y-up space and target the node before that final rotation node. The BabylonJs exporter for 3dsMax converts its meshes and animations to z-up as part of the export process. Many glTF loader implementations get tripped up on this (failing to support more than one model mesh or failing to respect the full transform hierarchy or failing to support animations). There are similar complexities and support issues around vertex data formats, buffer layouts, punctual lights etc

My limited reading of the USD format is that it has an even wider specification. My concern is that browser support will splinter even worse than it would with glTF. The' model' proposal doesn't dig into what USD nodes will and won't be supported and exactly how the data is expected to be rendered.

[moron4hire]

Blender is Z-up and glTF is Y-up, but regardless, this is a long standing issue of Blender. These problems exist for all of the model export formats coming out of Blender. How is that glTF's fault?