ARCore integration boundaries
What an ARCore adapter must provide and what XR settings do not enable.
ARCore integration boundaries
ARCore is Google's augmented-reality platform. Its SDK supplies motion tracking, environmental understanding and light estimation. Capabilities and supported devices are covered in Google's documentation; SDK features do not automatically become available in Reckfell.
The current built-in module tree has no separate ARCore module. A clean project in installed Reckfell 1.0.0 for Windows exposed no ARCore class family or exact ARCore interface name. This guide establishes no ready-made Reckfell integration. The check did not inspect a separate Android project with external plugins or determine every third-party package's status.
Identify the required data first
| Task | What the integration must supply |
|---|---|
| Show camera imagery behind virtual objects | A frame/texture, camera parameters and synchronized presentation. |
| Keep an object in physical space | Pose, tracking state, coordinate space and anchor lifetime. |
| Place an object on a surface | Detected-surface data or a hit test, transformed into gameplay space. |
| Match virtual lighting | Light estimates explicitly applied to Environment/lights. |
These are adapter requirements, not features implemented here. Adding an Entity, Camera3D or transparent Viewport creates none of this data. The ARCore SDK still needs a bridge to gameplay code and rendering.
Distinguish the XR paths
Passthrough describes composition with an XR-runtime-provided environment; enabling it does not start an ARCore session. MobileVRInterface is a separate phone stereo-VR interface without built-in positional room tracking. It does not replace ARCore.
If the project already has an ARCore adapter, use its verified class names, events and resource-ownership model. On the target device check session startup/shutdown, permissions, tracking loss and return from the background. Without a specific adapter there is no honest universal C# example or compatible package version to promise.
Verification scope
Current module sources and the registry of a clean headless project without external-extension loading were checked. Platform capabilities were checked against Google's official overview. No ARCore SDK was installed; Android hardware, camera textures, anchors, surfaces, light estimates and export were not tested. Unverified claims about a ready-made plugin and its development status were removed; engine source was unchanged.