Replies: 1 comment
-
Either way, I think it may be worth it to add those available ones to https://github.com/bevyengine/bevy-crate-reservations |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Now that
RenderTarget::TextureView
has been merged we may start to see external XR crates appearing. It might be worth getting ahead of crate organization sooner rather than later.Current Status
bevy_xr
reserved by bevybevy_openxr
currently owned by @blaindbevy_webxr
currently availablebevy_vision_os
currently availableIt may be possible to cram the implementations into
bevy_xr
but to me that sounds messy. I'm guessingbevy_xr
would contain the common traits etc, and the others would contain implementations and device specific features. If we intend to have internal XR implementation crates should we start transferring and reserving the ones we'd need?Beta Was this translation helpful? Give feedback.
All reactions