-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Document that VisionOS is supported #11140
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
base: master
Are you sure you want to change the base?
Conversation
dfed556
to
aae99bb
Compare
Fixed |
aae99bb
to
e780869
Compare
Fixed |
poke @BastiaanOlij |
A list of supported platforms can be found on the list of features page :ref:`here <doc_xr_support>`. | ||
Supported interfaces register themselves with the :ref:`XRServer <class_xrserver>` | ||
and can be queried with the ``find_interface`` method on the :ref:`XRServer <class_xrserver>`. | ||
When the desired interface is found it can be initialized by calling ``initialize`` |
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.
Owh dang, this is a little outdated now. It's still correct and how it was designed to work, but for OpenXR we've had to early initialise in the core. While we talk about that elsewhere, wonder if we should add a note about it here.
Totally offtopic for VisionOs though so something to do separately.
My main concern here is that in 4.5, we don't really have any XR specific functionality for VisionOS. In 4.6 when we actually should get specific XR functionality added to this, the doc changes here will already become outdated. Might still be worth adding as this is where people will look but IDK.. |
- Out of the box limited support for visionOS Apple headsets. | ||
|
||
- Currently only exporting an application for use on a flat plane within the | ||
headset is supported. Immersive experiences are not supported. | ||
|
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.
Apple describes iPhone and iPad apps compiled for visionOS as Compatible Apps:
-
Note: People can also run your existing iPadOS or iOS app as a compatible app in visionOS. Your app appears as a single, scalable window in the person’s surroundings.
We could include these links to give developers more information.
Yes but since it's in the engine now, we should be telling people somewhere that it's not full support. The stuff in this PR also isn't hard to update when full support comes. The XR page change is just pointing at the list of features for supported platforms, which I think we should have been doing anyway, and we'd just have to update a small amount of text in the list of features when full XR functionality is available. |
@skyace65 I agree we should have mention of VisionOS support in the manual, the question is whether this belongs in the XR sections of the manual as we do not have specific XR functionality yet. I was under the impression we already had manual changes addressing VisionOS support around the platform that either Recardo or Stuart submitted. Or maybe those are still outstanding PRs? |
@BastiaanOlij there have been no opened or merged documentation PRs for the manual regarding visionOS other than this one. I think it makes sense to mention it in the XR system requirements section. If we leave it out I think people will just assume that it wasn't updated, rather than assume it doesn't actually have full functionality |
Pretty much does what the title says. I've added VisionOS to the list of features page in the XR section, I've also linked to that page from the Intro to XR page. It seemed less clunky than adding a note or warning box to the intro page. I've also updated a screenshot on the exporting projects page.
This PR does NOT cover exporting to VisionOS itself right now. I assume the process is near identical to what's on the iPhone export page but I'm not comfortable setting up a page based on a guess. There's also some odd stuff related to exporting that should be documented. Since it's built on top of what's already in place for iPhone's there's options in the VisionOS export that only make sense in that context such as "Performance Gaming Tier" and "Performance A 12".