Open
Conversation
Contributor
|
Still in wip? Or ready to be review? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
AR – Passthrough Integration
Summary
This PR introduces passthrough AR support in both Editor mode and Build mode.
The implementation mainly relies on Meta Building Blocks, which may still be unstable. Please use with caution.
This feature has only been tested on Meta Quest 3 and is not guaranteed to work with other headset brands.
Important Notes
Uses Meta Building Blocks for AR setup
Potential instability depending on Meta SDK updates
Tested exclusively on Meta Quest 3
Setup Tutorial :
A step-by-step guide to configure your Unity project for AR is available here: https://1drv.ms/b/c/be5f27fe3492f55f/IQBbvQ4_wEsPTbofBoLAWrYmAeMo-YYwc14wNcWVZ9v3rpk?e=MCpffc
fix #38