hz-unity-meta-interaction-sdk

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Meta XR Interaction SDK (com.meta.xr.sdk.interaction.ovr)

Meta XR Interaction SDK (com.meta.xr.sdk.interaction.ovr)

Use ISDK for interaction on Meta VR

在 Meta VR 上使用 ISDK 进行交互

The Core SDK (
com.meta.xr.sdk.core
) gives you the headset - camera rig, tracking,
OVRManager
. It does not give you interaction. ISDK is the interaction layer. Don't hand-roll grabbing on
OVRInput
, raycasts, or trigger colliders: ISDK already models hover/select state, pose conforming, throw velocity, and interactor arbitration, and a hand-rolled version drifts from platform behavior.
TargetWhat to do
Meta VR / Horizon OS, or platform not statedOVR backend (
com.meta.xr.sdk.interaction.ovr
) - the rest of this skill
Cross-platform, still on ISDKUnityXR backend (Essentials + Unity XR Hands). Same model, different entry points - look them up, don't assume the OVR ones
Cross-platform not using ISDKStop. This skill does not apply.
Do not infer cross-platform intent - default to OVR, switch only if the user says so, and state which backend you used.
Set interactions up through the Quick Actions APIs, not by hand.
OVRQuickActionsAPI
builds the rig;
QuickActionsAPI
makes objects interactive and equips interactors. Reach for manual prefab assembly only when a Quick Action cannot express what you need - and say so.
Meta's own guidance too: Quick Actions are "the fastest and recommended way" to add the rig (docs).
Core SDK(
com.meta.xr.sdk.core
)负责提供 headset——camera rig、tracking 和
OVRManager
,但不提供交互。**ISDK 才是交互层。**不要基于
OVRInput
、raycast 或 trigger collider 自行实现抓取:ISDK 已经对 hover/select 状态、pose conforming、throw velocity 和 interactor arbitration 进行了建模,手工实现会逐渐偏离平台行为。
目标应执行的操作
Meta VR / Horizon OS,或未说明平台OVR backend(
com.meta.xr.sdk.interaction.ovr
)——本 skill 的其余内容均以此为准
跨平台,但仍使用 ISDKUnityXR backend(Essentials + Unity XR Hands)。模型相同,但入口不同——请查阅对应 API,不要假设它们与 OVR API 相同
跨平台且不使用 ISDK停止。本 skill 不适用。
不要推断用户有跨平台意图——默认使用 OVR,只有用户明确提出时才切换,并说明使用了哪个 backend。
通过 Quick Actions API 设置交互,不要手工完成。
OVRQuickActionsAPI
用于构建 rig;
QuickActionsAPI
让对象可交互并装备 interactor。只有当某个 Quick Action 无法表达需求时,才手动组装 prefab——并明确说明这一点。
Meta 官方指南也指出:Quick Actions 是添加 rig“最快且推荐的方式” (文档)。

Quick start

快速开始

csharp
using Oculus.Interaction.Editor.QuickActions;         // QuickActionsAPI
using Oculus.Interaction.OVR.Editor.QuickActions;     // OVRQuickActionsAPI

// Delete the default Main Camera first - ISDK brings its own camera rig.

// 1. Rig: comprehensive interaction rig (hands + controllers + every interactor + visuals),
//    plus an OVRCameraRig if the scene has none.
OVRQuickActionsAPI.AddOVRInteractionRig();

// 2. Interactable: adds Rigidbody + Grabbable + a HandGrab/Grab interactable child.
var cube = GameObject.CreatePrimitive(PrimitiveType.Cube);
cube.transform.localScale = Vector3.one * 0.1f;
cube.transform.position = new Vector3(0f, 1.0f, 0.4f);   // in reach at a FloorLevel origin
QuickActionsAPI.AddGrabInteraction(cube);
Every method returns the root GameObjects it created - not the target you passed. Use that to find what to configure or rename.
csharp
using Oculus.Interaction.Editor.QuickActions;         // QuickActionsAPI
using Oculus.Interaction.OVR.Editor.QuickActions;     // OVRQuickActionsAPI

// Delete the default Main Camera first - ISDK brings its own camera rig.

// 1. Rig: comprehensive interaction rig (hands + controllers + every interactor + visuals),
//    plus an OVRCameraRig if the scene has none.
OVRQuickActionsAPI.AddOVRInteractionRig();

// 2. Interactable: adds Rigidbody + Grabbable + a HandGrab/Grab interactable child.
var cube = GameObject.CreatePrimitive(PrimitiveType.Cube);
cube.transform.localScale = Vector3.one * 0.1f;
cube.transform.position = new Vector3(0f, 1.0f, 0.4f);   // in reach at a FloorLevel origin
QuickActionsAPI.AddGrabInteraction(cube);
每个方法返回的是它创建的根 GameObject,而不是传入的 target。请使用返回值来查找需要配置或重命名的对象。

Which call for which interaction

各交互功能对应的调用

FeatureCall
Interaction rig (+ camera rig)
OVRQuickActionsAPI.AddOVRInteractionRig()
Hand grab (near)
QuickActionsAPI.AddGrabInteraction(go)
Distance grab
QuickActionsAPI.AddDistanceGrabInteraction(go, mode)
Ray grab
QuickActionsAPI.AddRayGrabInteraction(go)
Gaze grab (eye tracking)
QuickActionsAPI.AddGazeInteraction(go)
Teleport surface
QuickActionsAPI.AddTeleportInteraction(go, surfaceType)
Poke / ray / gaze a Canvas
QuickActionsAPI.AddPokeCanvasInteraction(go)
·
AddRayCanvasInteraction
·
AddGazeCanvasInteraction
Interactors on a hand / controller
QuickActionsAPI.AddHandInteractors(go, types)
·
AddControllerInteractors
·
AddControllerHandInteractors
Touch hand grab, plain poke, plain rayno API - menu item only
Every one of these takes a
GameObject target
- never a component. Passing a
Canvas
to a Canvas call is a compile error (
cannot convert from 'UnityEngine.Canvas' to 'UnityEngine.GameObject'
); pass
canvas.gameObject
or the result of
GameObject.Find
. Likewise the interactor calls take the GameObject that carries the
Hand
/
Controller
, not the component.
Signatures, parameters, and what each call builds: quick-actions-api.md · ovr-quick-actions-api.md. Per-feature Meta docs: documentation.md.
The interactor calls are only for a hand-built rig -
AddOVRInteractionRig()
already ships every interactor, so after it they are redundant.
功能调用
Interaction rig(+ camera rig)
OVRQuickActionsAPI.AddOVRInteractionRig()
手部抓取(近距离)
QuickActionsAPI.AddGrabInteraction(go)
距离抓取
QuickActionsAPI.AddDistanceGrabInteraction(go, mode)
射线抓取
QuickActionsAPI.AddRayGrabInteraction(go)
凝视抓取(眼动追踪)
QuickActionsAPI.AddGazeInteraction(go)
表面传送
QuickActionsAPI.AddTeleportInteraction(go, surfaceType)
对 Canvas 执行 poke / ray / gaze
QuickActionsAPI.AddPokeCanvasInteraction(go)
·
AddRayCanvasInteraction
·
AddGazeCanvasInteraction
手部/控制器上的 interactor
QuickActionsAPI.AddHandInteractors(go, types)
·
AddControllerInteractors
·
AddControllerHandInteractors
触摸式手部抓取、普通 poke、普通 ray无 API——只能使用菜单项
**所有这些调用都接收一个
GameObject target
,绝不能传入 component。**将
Canvas
传给 Canvas 调用会引发编译错误(
cannot convert from 'UnityEngine.Canvas' to 'UnityEngine.GameObject'
);应传入
canvas.gameObject
或
GameObject.Find
的结果。同样,interactor 调用要接收承载
Hand
/
Controller
的 GameObject,而不是 component。
方法签名、参数以及每个调用所构建的内容: quick-actions-api.md · ovr-quick-actions-api.md。 各功能的 Meta 文档:documentation.md。
Interactor 调用仅用于手工构建的 rig——
AddOVRInteractionRig()
已自带全部 interactor,因此调用它后再使用这些方法是冗余的。

When the rig isn't in your scene

当 scene 中没有 rig 时

An interaction needs a matching interactor at runtime, in the loaded scene set. It does not need the rig present at author time.
Quick ActionNeeds a rig in the scene?
Interactables (grab, distance grab, ray grab, gaze, canvas, teleport)No - everything they require is on the target itself
Interactors (
AddHandInteractors
and siblings)
Yes -
target
must carry the
Hand
/
Controller
AddOVRInteractionRig()
It creates the rig
So all of these are fine: the rig is instantiated at runtime, lives in a bootstrap scene under
DontDestroyOnLoad
, arrives from an additive scene, or you are authoring a prefab.
The consequence. An interactable Quick Action also tops up the rig with matching interactors when it finds one - silently skipped when there is no rig. Nothing breaks, but nobody added those interactors, so the rig that eventually loads must already carry the types your interactable needs. A
DistanceHandGrabInteractable
with no
DistanceHandGrabInteractor
on the runtime rig is inert and logs nothing. When you author against an absent rig, say which interactor types the runtime rig must provide.
每项交互在运行时都需要匹配的 interactor,并且必须位于已加载的 scene 集合中。编辑时,scene 中无需存在 rig。
Quick Actionscene 中需要 rig 吗?
Interactable(grab、distance grab、ray grab、gaze、canvas、teleport)否——所需的一切都挂在 target 本身
Interactor(
AddHandInteractors
及其同类方法)
是——
target
必须承载
Hand
/
Controller
AddOVRInteractionRig()
它会创建 rig
因此,以下情况都没有问题:rig 在运行时实例化、存放在
DontDestroyOnLoad
下的 bootstrap scene 中、从 additive scene 加载进来,或者你正在编写 prefab。
**由此带来的影响。**当 interactable Quick Action 找到 rig 时,它还会向 rig 补充匹配的 interactor;如果没有 rig,则会静默跳过。不会直接破坏任何功能,但也没有人添加这些 interactor,因此最终加载的 rig 必须已经包含 interactable 所需的类型。运行时 rig 中没有
DistanceHandGrabInteractor
时,
DistanceHandGrabInteractable
将完全失效,而且不会记录任何日志。针对编辑时不存在 rig 的情况编写代码时,请说明运行时 rig 必须提供哪些 interactor 类型。

Baking interaction into a prefab

将交互烘焙到 prefab 中

Verified: run the interactable call on a scene instance, then save. The wiring is self-contained - the interactable's
_pointableElement
resolves to the
Grabbable
inside the prefab, with no leaked scene reference.
csharp
var go = GameObject.CreatePrimitive(PrimitiveType.Cube);
QuickActionsAPI.AddGrabInteraction(go);                       // no rig needed
PrefabUtility.SaveAsPrefabAsset(go, "Assets/Grabbable.prefab", out bool ok);
Object.DestroyImmediate(go);
  • Don't verify a prefab asset via
    interactable.PointableElement
    - it is assigned in
    Awake()
    , which never runs on an asset, so it is always null there even when the prefab is correct. Read the serialized field:
    new SerializedObject(interactable).FindProperty("_pointableElement").objectReferenceValue
    .
  • Canvas calls: pass
    fixPointableCanvasModule: false
    when the
    PointableCanvasModule
    comes from a prefab or an unloaded additive scene, or you get a second one in the open scene.
已验证:先在 scene instance 上运行 interactable 调用,然后保存。接线是自包含的——interactable 的
_pointableElement
会解析到 prefab 内的
Grabbable
,不会泄漏 scene 引用。
csharp
var go = GameObject.CreatePrimitive(PrimitiveType.Cube);
QuickActionsAPI.AddGrabInteraction(go);                       // no rig needed
PrefabUtility.SaveAsPrefabAsset(go, "Assets/Grabbable.prefab", out bool ok);
Object.DestroyImmediate(go);
  • 不要通过
    interactable.PointableElement
    验证 prefab asset
    ——该字段在
    Awake()
    中赋值,而 asset 上永远不会运行
    Awake()
    ,因此即使 prefab 正确,它也始终为 null。请读取序列化字段:
    new SerializedObject(interactable).FindProperty("_pointableElement").objectReferenceValue
    。
  • **Canvas 调用:**当
    PointableCanvasModule
    来自 prefab 或尚未加载的 additive scene 时,请传入
    fixPointableCanvasModule: false
    ,否则当前 scene 中会出现第二个
    PointableCanvasModule
    。

Running the calls - both APIs are Editor-only

运行这些调用——两个 API 都仅限 Editor 使用

They live in Editor assemblies and cannot run from a
MonoBehaviour
or anything in a build.
1. Live Editor via
unity-cli
(preferred when one is open - drive it instead of editing scene YAML):
bash
unity status --format json          # look for state "ready"
unity command run_script --project-path <proj> --file /abs/path/DoTheThing.cs --entry MyClass.Run --format json
Use
run_script
with a
.cs
file rather than
eval
: shell quoting mangles C# char literals (
' '
), the file is re-runnable, it can live outside
Assets/
, and
--timeout_ms
awaits async entry points.
2. A project Editor script under
Assets/Editor/
(or an Editor-only asmdef referencing
Oculus.Interaction.Editor
and
Oculus.Interaction.OVR.Editor
), exposed as a
[MenuItem]
- when a human should be able to repeat the setup.
3. MCP, if a Unity MCP server is connected. Its harness constraints (no
using System.Reflection;
, no
BindingFlags
overloads, package Editor assemblies not referenced) apply there and not to
unity-cli
's Roslyn
run_script
— see unity-mcp-fallback.md.
Finish by saving the scene (
EditorSceneManager.MarkSceneDirty
+
SaveScene
), then verify.
它们位于 Editor assemblies 中,无法在
MonoBehaviour
或构建产物中的任何代码中运行。
1. 通过
unity-cli
操作实时 Editor
(Editor 已打开时优先采用——直接驱动它,而不是编辑 scene YAML):
bash
unity status --format json          # look for state "ready"
unity command run_script --project-path <proj> --file /abs/path/DoTheThing.cs --entry MyClass.Run --format json
使用
run_script
配合
.cs
文件,不要使用
eval
:shell quoting 会破坏 C# 字符字面量(
' '
),文件可重复运行,可以放在
Assets/
之外,而且
--timeout_ms
可以等待异步入口点。
2. 项目 Editor 脚本:放在
Assets/Editor/
下(或使用引用
Oculus.Interaction.Editor
和
Oculus.Interaction.OVR.Editor
的 Editor-only asmdef),并公开一个
[MenuItem]
,便于人工重复执行设置。
3. MCP:如果连接了 Unity MCP server。其 harness 限制(禁止
using System.Reflection;
、禁止
BindingFlags
overload、不能引用 package Editor assemblies)仅适用于 MCP,不适用于
unity-cli
的 Roslyn
run_script
——参见 unity-mcp-fallback.md。
最后保存 scene(
EditorSceneManager.MarkSceneDirty
+
SaveScene
),然后进行验证。

Installing

安装

Install
com.meta.xr.sdk.interaction.ovr
- it pulls in Essentials and the Core SDK. Check
Packages/manifest.json
first; if it is listed, do not re-add. Installing only
com.meta.xr.sdk.interaction
is the classic misinstall: interaction model, no OVR binding, no rig, no
OVRQuickActionsAPI
.
csharp
using UnityEditor.PackageManager;
var request = Client.Add("com.meta.xr.sdk.interaction.ovr");   // async - poll request.IsCompleted
Or against a live Editor:
unity command package_add --identifier com.meta.xr.sdk.interaction.ovr --confirm true --wait true
.
A successful add forces a recompile and domain reload - never install a package and use its API in the same script. Details: installation.md.
安装
com.meta.xr.sdk.interaction.ovr
——它会引入 Essentials 和 Core SDK。先检查
Packages/manifest.json
;如果已经列出,则不要重复添加。只安装
com.meta.xr.sdk.interaction
是典型的错误安装:这样只有 interaction model,没有 OVR binding、rig 或
OVRQuickActionsAPI
。
csharp
using UnityEditor.PackageManager;
var request = Client.Add("com.meta.xr.sdk.interaction.ovr");   // async - poll request.IsCompleted
或者针对实时 Editor 执行:
unity command package_add --identifier com.meta.xr.sdk.interaction.ovr --confirm true --wait true
。
成功添加会强制触发 recompile 和 domain reload——绝不要在安装 package 的同一个脚本中继续使用其 API。详情:installation.md。

Finding the truth: source first, docs second

查明真相:源码优先,文档其次

Don't answer ISDK questions from memory. The installed package is authoritative for behavior; Meta's docs for intent and design guidance.
Search for the API sources by filename pattern - this works regardless of install form (registry cache, embedded, or local):
**/com.meta.xr.sdk.interaction*/Editor/QuickActions/Scripts/QuickActionsAPI.cs
**/com.meta.xr.sdk.interaction.ovr*/Editor/QuickActions/Scripts/OVRQuickActionsAPI.cs
Then use the resolved package roots for all subsequent lookups.
Inside Unity,
AssetDatabase
paths work regardless of install form:
Packages/com.meta.xr.sdk.interaction.ovr/Runtime/Prefabs/...
.
For docs, query
metavr
-
vr_docs_search(query, scope="unity")
for the
doc_path
, then
vr_docs_get_page
, and
vr_api_search(query, engine="unity")
for signatures. Never hand-construct a doc URL; the namespace varies. Curated map: documentation.md.
The two APIs are the supported entry points; the machinery under them is not public API. If you are reaching for reflection to invoke a wizard, you have probably missed a method - re-read the two files first. The same actions exist under the
GameObject > Interaction SDK
menu as blocking wizard windows; open one when you want to see what a call will create.
**不要凭记忆回答 ISDK 问题。**已安装的 package 对行为具有权威性;Meta 文档用于说明意图和设计指导。
按文件名模式搜索 API 源码——无论安装形式是 registry cache、embedded 还是 local,这一点都适用:
**/com.meta.xr.sdk.interaction*/Editor/QuickActions/Scripts/QuickActionsAPI.cs
**/com.meta.xr.sdk.interaction.ovr*/Editor/QuickActions/Scripts/OVRQuickActionsAPI.cs
然后在后续所有查找中使用解析得到的 package roots。
在 Unity 内,无论安装形式如何,
AssetDatabase
路径都可用:
Packages/com.meta.xr.sdk.interaction.ovr/Runtime/Prefabs/...
。
对于文档,使用
metavr
查询——通过
vr_docs_search(query, scope="unity")
获取
doc_path
,再调用
vr_docs_get_page
;使用
vr_api_search(query, engine="unity")
查询签名。绝不手动拼接文档 URL;namespace 会发生变化。整理后的映射: documentation.md。
**这两个 API 才是受支持的入口;其下的实现机制不是 public API。**如果你试图通过 reflection 调用 wizard,很可能只是漏掉了某个方法——先重新阅读这两个源文件。相同的操作也位于
GameObject > Interaction SDK
菜单下,形式是阻塞式 wizard 窗口;当你想查看某个调用会创建什么时,可以打开相应窗口。

What the docs don't tell you

文档不会告诉你的内容

Each of these is visible only from the source or from a runtime failure.
  • You get the optional components too. A call is equivalent to clicking Fix All and Add All in the wizard.
    AddDistanceGrabInteraction
    additionally creates a root
    ISDK_SnapZone (<target>)
    that pulls the object back after it goes untouched - delete it to opt out. Detail: quick-actions-api.md.
  • Grab calls make the Rigidbody kinematic (
    useGravity = false; isKinematic = true
    ). Objects float where you put them; that is intended.
  • Created names come from the wizard -
    ISDK_HandGrabInteraction
    ,
    ISDK_SnapZone (...)
    . Rename afterwards if it matters; components track by reference, so renaming is safe.
  • Interactor calls target the
    Hand
    /
    Controller
    object itself.
    Hand
    -derived components on child objects log
    Could not execute HandInteractorWizard
    ; filter with
    .Where(h => h.GetType() == typeof(Hand))
    .
  • Enum names don't match the components they select.
    DistanceGrabMode
    vs. the Movement Provider in the scene vs. Meta's doc label are three vocabularies - never guess the mapping.
  • The wizards expose settings the APIs don't. If you need one that isn't a parameter, use the menu item or post-process the result. Smooth Locomotion on the rig is the common case.
  • Building Blocks are another route to the same result, not a better one. Prefer the APIs: no block-tracking components, no project-setup side pass, readable names.
  • No API means no API. If there is no method for what you want, use the menu item or build it from components - don't reflect into the wizard.
以下内容只有通过源码或运行时故障才能看到。
  • **你也会获得可选组件。**一次调用等同于在 wizard 中点击 Fix All 并点击 Add All。
    AddDistanceGrabInteraction
    还会额外创建根节点
    ISDK_SnapZone (<target>)
    ,在对象长时间未被触碰后将其拉回——如需退出此行为,请将其删除。详情:quick-actions-api.md。
  • Grab 调用会将 Rigidbody 设为 kinematic(
    useGravity = false; isKinematic = true
    )。对象会悬浮在放置位置;这是预期行为。
  • 创建的名称来自 wizard——
    ISDK_HandGrabInteraction
    、
    ISDK_SnapZone (...)
    。之后如有需要可以重命名;组件通过引用进行跟踪,因此重命名是安全的。
  • **Interactor 调用以
    Hand
    /
    Controller
    对象本身为目标。**子对象上派生自
    Hand
    的组件会记录
    Could not execute HandInteractorWizard
    ;请使用
    .Where(h => h.GetType() == typeof(Hand))
    过滤。
  • Enum 名称与它们选择的组件并不一致。
    DistanceGrabMode
    、scene 中的 Movement Provider 与 Meta 文档标签是三套不同的词汇——绝不要猜测映射关系。
  • **Wizard 暴露的某些设置无法通过 API 访问。**如果所需设置不是参数,请使用菜单项或对结果进行后处理。Rig 上的 Smooth Locomotion 是常见案例。
  • **Building Blocks 是达成相同结果的另一种方式,并非更优。**优先使用 API:没有 block-tracking 组件,不需要额外的 project-setup 步骤,名称也更易读。
  • **没有 API 就没有 API。**如果不存在满足需求的方法,请使用菜单项或用组件自行构建——不要通过 reflection 进入 wizard。

Always verify in Play mode

始终在 Play mode 中验证

ISDK asserts its wiring in
Start()
, so a scene that looks correct in the Inspector can still throw. Edit-time component checks are not sufficient.
  1. Clear the console, enter Play mode, read the console, exit.
  2. Zero errors and zero exceptions is the bar. Every
    AssertionException
    names the exact component and field - treat it as a real defect.
  3. [MetaXRFeature]: ErrorFormFactorUnavailable xrGetSystem
    only means no headset/XRSIM is attached; OpenXR teardown warnings are benign.
  4. Some failures are silent - see verification.md.
  5. After Play mode is clean, confirm on a real headset: build an APK,
    metavr app install <apk>
    , then stream
    metavr adb logcat --follow --tag Unity
    while exercising each interaction.
ISDK 会在
Start()
中对其 wiring 进行断言,因此一个在 Inspector 中看起来正确的 scene 仍可能抛出异常。仅在编辑时检查 component 并不充分。
  1. 清空 console,进入 Play mode,读取 console,然后退出。
  2. 零错误且零异常才是标准。每个
    AssertionException
    都会指出确切的 component 和 field——应将其视为真实缺陷。
  3. [MetaXRFeature]: ErrorFormFactorUnavailable xrGetSystem
    仅表示没有连接 headset/XRSIM;OpenXR teardown warning 无害。
  4. 有些故障是静默的——参见 verification.md。
  5. Play mode 清理完成后,在真实 headset 上确认:构建 APK,执行
    metavr app install <apk>
    ,然后运行
    metavr adb logcat --follow --tag Unity
    ,同时逐一测试各项交互。

References

参考

  • quick-actions-api.md - signatures, enums, what each call builds
  • ovr-quick-actions-api.md - the rig call and the rig it creates
  • interaction-model.md - interactor/interactable model, rig anatomy, placement
  • installation.md - install paths, dependency chain, assemblies
  • verification.md - Play-mode loop, assertion table, silent failures
  • documentation.md - curated Meta doc map and lookup recipe
  • unity-mcp-fallback.md - running the calls over Unity MCP instead of
    unity-cli
  • quick-actions-api.md——方法签名、enum、每个调用所构建的内容
  • ovr-quick-actions-api.md——rig 调用及其创建的 rig
  • interaction-model.md——interactor/interactable 模型、rig 结构、放置方式
  • installation.md——安装路径、依赖链、assemblies
  • verification.md——Play mode 循环、断言表、静默故障
  • documentation.md——整理后的 Meta 文档映射和查找方法
  • unity-mcp-fallback.md——通过 Unity MCP 而不是
    unity-cli
    运行这些调用

Related skills

相关 skill

  • hz-unity-meta-core-sdk
    - camera rig,
    OVRManager
    , tracking origin, hand tracking support, Project Setup Tool, AndroidManifest
  • unity-cli
    - drive a live Editor
  • hz-xr-simulator-install-and-configure
    /
    hz-vr-debug
    - run and debug beyond Play mode
  • hz-unity-meta-core-sdk
    ——camera rig、
    OVRManager
    、tracking origin、手部追踪支持、Project Setup Tool、AndroidManifest
  • unity-cli
    ——驱动实时 Editor
  • hz-xr-simulator-install-and-configure
    /
    hz-vr-debug
    ——在 Play mode 之外运行和调试