-
Notifications
You must be signed in to change notification settings - Fork 384
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
[WIP] MSC3815: 3D Worlds #3815
base: main
Are you sure you want to change the base?
[WIP] MSC3815: 3D Worlds #3815
Conversation
|
||
```json | ||
{ | ||
"type": "m.world", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what's the state key? presumably we should be able to support multiple GLBs per world in order to represent the compose hierarchy?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd imagine glTF composition will likely happen within the glTF itself. This allows us to reference and parent glTF scenes to nodes, override properties, and more. That'll be dependent on a glTF spec proposal. I think that's more desirable than just trying to merge multiple glTFs into one scene and allows us to hopefully eventually specify this within the correct standards body.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
kk. if you compose like that, will the GLTFs (or GLB) binary diff nicely against each other?
This is a draft spec for specifying Third Room's 3D environments and avatars. It may very well end up in a vendor specification. The spec is still under heavy development and not ready for review.
Rendered