-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Add additional information about the Godot XR Vendor Plugin #11515
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
50b6bbf to
05efaab
Compare
05efaab to
8f198c9
Compare
dsnopek
left a comment
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.
Thanks! Looks good to me :-)
| * You can look at a number of `XR demos here <https://github.com/godotengine/godot-demo-projects/tree/master/xr>`_. | ||
| * You can find 3rd party tutorials on our :ref:`Tutorials and resources <doc_community_tutorials>` page. | ||
|
|
||
| Godot XR vendor plugin |
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 do think we should try to be consistent when referencing the plugin name so that it matches the name on the asset library.
| Godot XR vendor plugin | |
| Godot OpenXR Vendors plugin |
Now that the vendor plugin is optional, added a note to that in the documentation making clear the vendor plugin is still important.
Also added a section in next steps to underline that the vendor plugin isn't just useful on AOSP devices, but also to unlock vendor extensions on other platforms.
This includes a link to the client support matrix where users can find which OpenXR extensions are supported in core, and which require the vendor plugin.