89672ad9e0
Former-commit-id: f7922f49f34ad54f0c3bb5acae3391b2925855ea Former-commit-id: f8c261c5478d0ef9a32124c470f03ad59d8c5d37 |
||
---|---|---|
.. | ||
Documentation~ | ||
Editor | ||
Materials | ||
Runtime | ||
Tests | ||
CHANGELOG.md | ||
CHANGELOG.md.meta | ||
Editor.meta | ||
LICENSE.md | ||
LICENSE.md.meta | ||
Materials.meta | ||
README.md | ||
README.md.meta | ||
Runtime.meta | ||
Tests.meta | ||
package.json | ||
package.json.meta |
README.md
AR Foundation
Use the AR Foundation package to add high-level functionality for working with augmented reality. Unity 2018.1 includes built-in multi-platform support for AR. These APIs are in the UnityEngine.XR.ARSubsystems
namespace, and consist of a number of Subsystem
s, e.g., XRPlaneSubsystem
. Several XR Subsystems comprise the low-level API for interacting with AR. The AR Foundation package wraps this low-level API into a cohesive whole and enhances it with additional utilities, such as AR session lifecycle management and the creation of GameObject
s to represent detected features in the environment.
Branch Guidelines
-
master
==> Target this branch for changes that need to be in the most recent preview package. Then cherry-pick changes from this branch into older, non-staging branches.master
will eventually branch to2.1.x
once work on a newer release begins. -
2.0.x
- Target this branch for changes that should be in the 2.0.x package versions. -
2.0.x-staging
- Only merge to this branch from2.0.x
in preparation for a release. This package should ideally contain the exact contents of the latest release on staging Bintray. So before a new release QA would validate against2.0.x
and then a merge would take place into2.0.x-staging
. -
1.1.x
- Target this branch for changes that should be in the 1.1.x package versions. -
1.1.x-staging
- Only merge to this branch from1.1.x
in preparation for a release. This package should ideally contain the exact contents of the latest release on staging Bintray. So before a new release QA would validate against1.1.x
and then a merge would take place into1.1.x-staging
. -
1.0.x
- Target this branch for changes that should be in the 1.0.x package versions. -
1.0.x-staging
- Only merge to this branch from1.0.x
in preparation for a release. This package should ideally contain the exact contents of the latest release on staging Bintray. So before a new release QA would validate against1.0.x
and then a merge would take place into1.0.x-staging
.