[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KRFE5BR2PSD08ZKDAS66R7":3,"skill-same:01M6KRFE5BR2PSD08ZKDAS66R7":96},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M6KRFE5BR2PSD08ZKDAS66R7","xr-development",null,"Use when building VR\u002FAR\u002FXR applications — OpenXR setup, XROrigin3D, hand tracking, controllers, passthrough, and Meta Quest deployment in Godot 4.3+","jame581\u002FGodotPrompter","jame581","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F21112138?v=4","01M6KR3KEQ9Z30WVJRR2E2ZVXE","Jan Mesarč","01M6KR3KJVRMPDSMASQPBCBVK3",964,"MIT","https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter\u002Fblob\u002Fmaster\u002Fskills\u002Fxr-development\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"xr development","development","quest","deployment","applications","Meta","use","hand","ar","godot 4","tracking","setup","vr","godot","when","2026-11-10 10:12:30",false,"---\nname: xr-development\ndescription: Use when building VR\u002FAR\u002FXR applications — OpenXR setup, XROrigin3D, hand tracking, controllers, passthrough, and Meta Quest deployment in Godot 4.3+\n---\n\n# XR Development in Godot 4.3+\n\nAll examples target Godot 4.3+ with no deprecated APIs. GDScript is shown first, then C#.\n\n> **Related skills:** **3d-essentials** for 3D rendering and environment, **physics-system** for 3D physics interactions, **input-handling** for non-XR input patterns, **export-pipeline** for platform exports.\n\n---\n\n## 1. XR Setup\n\n### Enabling OpenXR\n\n1. OpenXR is built into the engine — there is no plugin to enable.\n2. **Project Settings → XR → OpenXR → Enabled** → `true`\n3. **Project Settings → XR → Shaders → Enabled** → `true` (for XR shader support)\n4. **Rendering:**\n   - Use **Forward+** or **Mobile** renderer (Compatibility also works for simpler scenes)\n   - Set **Project Settings → Display → Window → VSync Mode** to `Disabled` (the XR runtime controls frame timing)\n\n### Core Scene Structure\n\n```\nMain (Node3D)\n├── XROrigin3D                    ← Player's physical space origin\n│   ├── XRCamera3D                ← Head-mounted display\n│   ├── XRController3D (left)     ← Left controller\n│   │   └── LeftHandModel (MeshInstance3D or hand tracking)\n│   ├── XRController3D (right)    ← Right controller\n│   │   └── RightHandModel\n│   └── (XRBodyTracker via XRServer — optional full body tracking)\n├── WorldEnvironment\n└── GameWorld (Node3D)\n    └── ... level geometry\n```\n\n### Starting XR Session\n\n```gdscript\nextends Node3D\n\nfunc _ready() -> void:\n    var xr_interface: XRInterface = XRServer.find_interface(\"OpenXR\")\n    if xr_interface and xr_interface.is_initialized():\n        get_viewport().use_xr = true\n    else:\n        push_error(\"OpenXR not available\")\n```\n\n```csharp\npublic partial class XRMain : Node3D\n{\n    public override void _Ready()\n    {\n        var xrInterface = XRServer.FindInterface(\"OpenXR\");\n        if (xrInterface != null && xrInterface.IsInitialized())\n            GetViewport().UseXR = true;\n        else\n            GD.PushError(\"OpenXR not available\");\n    }\n}\n```\n\n---\n\n## 2. Controllers and Input\n\n`XRController3D` nodes (one per hand, child of `XROrigin3D`) expose buttons via the OpenXR action map. Default action map names: trigger (`trigger` float, `trigger_click`), grip (`grip`, `grip_click`), thumbstick (`primary` Vector2, `primary_click`). Apply thumbstick locomotion velocity to `XROrigin3D` (not the camera).\n\n> See [references\u002Fcontrollers-and-input.md](references\u002Fcontrollers-and-input.md) for full XRController3D wiring, OpenXR button reference, and thumbstick locomotion recipe.\n\n---\n\n## 3. Hand Tracking\n\nWhen the headset supports hand tracking (Quest 2+, Pico 4, some SteamVR setups), the runtime publishes `XRHandTracker`s (`\u002Fuser\u002Fhand_tracker\u002Fleft` \u002F `right`); an `XRHandModifier3D` poses a hand skeleton from them, and `XRController3D` still gets select \u002F grip actions through the hand interaction profiles. Sample finger joints for gesture detection.\n\n> See [references\u002Fhand-tracking.md](references\u002Fhand-tracking.md) for hand-tracking node setup, joint sampling, and gesture-driven interactions.\n\n---\n\n## 4. Grabbing Objects\n\nStandard pattern: an `Area3D` on the controller detects nearby `RigidBody3D` objects; on grip-press, parent the body to the controller and freeze it; on grip-release, restore the parent and apply the controller's velocity to launch.\n\n> See [references\u002Fgrabbing-objects.md](references\u002Fgrabbing-objects.md) for the full physics-based grabbing implementation (GDScript + C#).\n\n---\n\n## 5. XR UI Interaction\n\nFor UI in VR, render a `Control` tree to a `SubViewport`, map its texture onto a `Quad` mesh placed in 3D space. Pointer: a `RayCast3D` from the controller hits the quad, the hit position is converted back to 2D viewport coords, an `InputEventMouseMotion` is forwarded into the SubViewport.\n\n> See [references\u002Fxr-ui.md](references\u002Fxr-ui.md) for the SubViewport-on-quad recipe and pointer\u002Fray interaction.\n\n---\n\n## 6. Passthrough (Mixed Reality)\n\nFor headsets that support it (Quest 2+, Pico 4), set the interface's `environment_blend_mode` to `XRInterface.XR_ENV_BLEND_MODE_ALPHA_BLEND` and clear the `WorldEnvironment` background to transparent. The user sees the real world with virtual content composited on top.\n\n> See [references\u002Fpassthrough.md](references\u002Fpassthrough.md) for the full enabling steps and Quest-specific notes.\n\n---\n\n## 7. Meta Quest Export\n\n### Setup\n\n1. Install the Android build template: **Project → Install Android Build Template...** (4.8: **Project → Setup Android Build...**)\n2. Install OpenXR Vendors plugin: **Project → Project Settings → Plugins** (**Project Settings → Addons → Plugins** on 4.8) → enable `Godot OpenXR Vendors` (or install from AssetLib)\n3. **Export → Add → Android**\n4. In the Android export preset:\n   - **XR Features → XR Mode** → `OpenXR`\n   - **Meta XR Features → Hand Tracking** \u002F **Passthrough** (added by the vendors plugin; shown once the matching OpenXR extension is enabled)\n   - **Architectures → arm64** → enabled (Quest is ARM)\n5. Set the min SDK to what Meta's store requires (29+ when this was written)\n\n### Performance Settings for Quest\n\n| Setting | Recommended Value |\n|---------|-------------------|\n| Renderer | Mobile |\n| MSAA | 2x or 4x (VR needs antialiasing) |\n| Texture Compression | ETC2\u002FASTC |\n| Target FPS | 72 (Quest 2) or 90 (Quest 3) |\n\n> **Critical:** VR must maintain consistent frame rate. Dropped frames cause nausea. Profile aggressively and keep draw calls low.\n\n> ⚠️ **Changed in Godot 4.7:** New project settings `xr\u002Fopenxr\u002Ffoveation_eye_tracked` and `xr\u002Fopenxr\u002Ffoveation_with_subsampled_images` both default to `true` — when the foveation level is not \"Disabled\", eye-tracked foveation is used where the headset supports it, and subsampled images are used on Vulkan for a bigger foveation win. Subsampled images are incompatible with many screen-space features (e.g., FXAA, glow); if any are enabled, subsampled images are automatically disabled with a log warning. Set either setting to `false` to opt out. See [GH-117868](https:\u002F\u002Fgithub.com\u002Fgodotengine\u002Fgodot\u002Fpull\u002F117868).\n\n---\n\n## 8. Godot 4.5+ XR Features\n\nGodot 4.5 adds a D3D12 OpenXR backend on Windows (Quest Link \u002F SteamVR alternative to Vulkan), foveated rendering on the Mobile Vulkan renderer, Application SpaceWarp frame synthesis for Quest\u002FPico, OpenXR Render Models for platform-native controller meshes, and windowed visionOS export via a dedicated visionOS preset. All are core Project Settings except SpaceWarp, which needs the Godot OpenXR Vendors plugin — no engine-level code changes.\n\n> See [references\u002Fgodot-4-5-features.md](references\u002Fgodot-4-5-features.md) for enabling steps, GDScript + C# render-model snippets, and per-feature caveats.\n\n---\n\n## 9. Godot 4.6+ XR Features\n\n### OpenXR 1.1 Support (Godot 4.6+)\n\nGodot 4.6 requests OpenXR 1.1 from the runtime, unlocking 1.1 features (promoted interaction profiles and paths, etc.) without any project-level change, and falls back to 1.0 if the runtime rejects it.\n\n> **Note:** To force a version, set `xr\u002Fopenxr\u002Ftarget_api_version` (e.g. `1.0.48`; empty by default).\n\n---\n\n### Spatial Entities — Anchors, Plane Tracking, Marker Tracking (Godot 4.6+)\n\nGodot 4.6 adds the OpenXR **Spatial Entities** extensions (experimental API): **spatial anchors** that persist virtual object positions across sessions, **plane detection** for floors, walls and ceilings, and **marker tracking** for QR codes and image markers. Enable them under **XR → OpenXR → Extensions → Spatial Entity** (all off by default; anchors with the default `RID()` context also need **Enable Spatial Anchors** and **Enable Builtin Anchor Detection**). Create an anchor with `OpenXRSpatialAnchorCapability.create_new_anchor(local_transform, RID())`, which returns an `OpenXRAnchorTracker`, and show it with an `XRAnchor3D` whose `tracker` is that tracker's name. There is no `XRSpatialAnchor` class.\n\n> See [references\u002Fspatial-entities.md](references\u002Fspatial-entities.md) for the GDScript + C# anchor placement recipe, the C# singleton lookup, anchor persistence across sessions, and the 4.7 `next` parameter on `create_new_anchor()`.\n\n---\n\n## 10. Godot 4.7+ XR Features\n\nGodot 4.7 adds the OpenXR user presence extension: `OpenXRInterface.user_presence_changed(is_user_present: bool)` fires when the headset is put on or taken off (not during startup or shutdown), with `is_user_presence_supported()` and `is_user_present()` to check and poll. Typical use: pause the game and mute audio while the headset is off. `OpenXRCompositionLayer` also gains `eye_visibility` (`EYE_VISIBILITY_BOTH`, `_LEFT`, `_RIGHT`) to show a layer to one eye only, and `create_new_anchor()` gains an optional `next` parameter for vendor create-info structs.\n\n> See [references\u002Fgodot-4-7-features.md](references\u002Fgodot-4-7-features.md) for the user presence and eye visibility recipes (GDScript + C#), and [references\u002Fspatial-entities.md](references\u002Fspatial-entities.md#spatial-anchor-extensibility-godot-47) for the anchor `next` parameter.\n\n---\n\n## 11. Common Pitfalls\n\n| Symptom | Cause | Fix |\n|---------|-------|-----|\n| Black screen in headset | `use_xr = true` not set on viewport | Set in `_ready()` after checking XR interface |\n| Controller input not firing | Wrong signal name for the platform | Check OpenXR action map bindings in Project Settings |\n| Objects scale wrong in VR | Scene not built at real-world scale | Use 1 unit = 1 meter throughout the scene |\n| Motion sickness from locomotion | Smooth rotation | Use snap turning (30° increments) or add a vignette during movement |\n| UI unreadable in VR | Panel too far away or too small | Place UI at 1–2m distance, use SubViewport at 1024+ resolution |\n| Hand tracking jittery | Raw joint data used directly | Apply smoothing (lerp toward new position each frame) |\n| Export fails on Quest | Missing Android build template or wrong architecture | Install the Android build template (4.8: **Setup Android Build...**); enable arm64; set API level 29+ |\n\n---\n\n## 12. Implementation Checklist\n\n- [ ] OpenXR is enabled in Project Settings\n- [ ] Scene uses `XROrigin3D` → `XRCamera3D` + `XRController3D` hierarchy\n- [ ] XR session is started with `get_viewport().use_xr = true` after interface check\n- [ ] World is built at 1 unit = 1 meter scale\n- [ ] Controller input uses OpenXR action names (`trigger_click`, `grip_click`, etc.)\n- [ ] Fallback exists for hand tracking → controller tracking\n- [ ] UI panels use SubViewport rendered on a 3D mesh\n- [ ] Locomotion includes comfort options (snap turn, vignette)\n- [ ] VSync is disabled (XR runtime handles frame timing)\n- [ ] Quest export uses Mobile renderer, arm64 architecture, API level 29+\n- [ ] On Windows Quest Link \u002F SteamVR builds, consider D3D12 backend if Vulkan drivers are problematic (Godot 4.5+)\n- [ ] Foveated rendering enabled via `xr\u002Fopenxr\u002Ffoveation_level` on the Mobile renderer for standalone Quest\u002FPico targets (Godot 4.5+)\n- [ ] Application SpaceWarp evaluated for performance budget on Meta Quest \u002F Pico targets (Godot 4.5+)\n- [ ] `OpenXRRenderModelManager` + `xr\u002Fopenxr\u002Fextensions\u002Frender_model` used for controller visuals where supported (Godot 4.5+)\n- [ ] visionOS export uses the dedicated visionOS preset; windowed apps only through 4.7 (Godot 4.5+)\n- [ ] Spatial anchors are created with `OpenXRSpatialAnchorCapability` and shown with `XRAnchor3D`, with the spatial entities extension enabled (Godot 4.6+)\n- [ ] Headset on\u002Foff handled via `OpenXRInterface.user_presence_changed` — pause\u002Fmute when the user is away (Godot 4.7+)\n- [ ] Foveation defaults reviewed — `xr\u002Fopenxr\u002Ffoveation_eye_tracked` and `xr\u002Fopenxr\u002Ffoveation_with_subsampled_images` are on by default; disable subsampled images if you rely on FXAA\u002Fglow (Godot 4.7+)\n","# XR Development in Godot 4.3+\n\nAll examples target Godot 4.3+ with no deprecated APIs. GDScript is shown first, then C#.\n\n> **Related skills:** **3d-essentials** for 3D rendering and environment, **physics-system** for 3D physics interactions, **input-handling** for non-XR input patterns, **export-pipeline** for platform exports.\n\n---\n\n## 1. XR Setup\n\n### Enabling OpenXR\n\n1. OpenXR is built into the engine — there is no plugin to enable.\n2. **Project Settings → XR → OpenXR → Enabled** → `true`\n3. **Project Settings → XR → Shaders → Enabled** → `true` (for XR shader support)\n4. **Rendering:**\n   - Use **Forward+** or **Mobile** renderer (Compatibility also works for simpler scenes)\n   - Set **Project Settings → Display → Window → VSync Mode** to `Disabled` (the XR runtime controls frame timing)\n\n### Core Scene Structure\n\n```\nMain (Node3D)\n├── XROrigin3D                    ← Player's physical space origin\n│   ├── XRCamera3D                ← Head-mounted display\n│   ├── XRController3D (left)     ← Left controller\n│   │   └── LeftHandModel (MeshInstance3D or hand tracking)\n│   ├── XRController3D (right)    ← Right controller\n│   │   └── RightHandModel\n│   └── (XRBodyTracker via XRServer — optional full body tracking)\n├── WorldEnvironment\n└── GameWorld (Node3D)\n    └── ... level geometry\n```\n\n### Starting XR Session\n\n```gdscript\nextends Node3D\n\nfunc _ready() -> void:\n    var xr_interface: XRInterface = XRServer.find_interface(\"OpenXR\")\n    if xr_interface and xr_interface.is_initialized():\n        get_viewport().use_xr = true\n    else:\n        push_error(\"OpenXR not available\")\n```\n\n```csharp\npublic partial class XRMain : Node3D\n{\n    public override void _Ready()\n    {\n        var xrInterface = XRServer.FindInterface(\"OpenXR\");\n        if (xrInterface != null && xrInterface.IsInitialized())\n            GetViewport().UseXR = true;\n        else\n            GD.PushError(\"OpenXR not available\");\n    }\n}\n```\n\n---\n\n## 2. Controllers and Input\n\n`XRController3D` nodes (one per hand, child of `XROrigin3D`) expose buttons via the OpenXR action map. Default action map names: trigger (`trigger` float, `trigger_click`), grip (`grip`, `grip_click`), thumbstick (`primary` Vector2, `primary_click`). Apply thumbstick locomotion velocity to `XROrigin3D` (not the camera).\n\n> See [references\u002Fcontrollers-and-input.md](references\u002Fcontrollers-and-input.md) for full XRController3D wiring, OpenXR button reference, and thumbstick locomotion recipe.\n\n---\n\n## 3. Hand Tracking\n\nWhen the headset supports hand tracking (Quest 2+, Pico 4, some SteamVR setups), the runtime publishes `XRHandTracker`s (`\u002Fuser\u002Fhand_tracker\u002Fleft` \u002F `right`); an `XRHandModifier3D` poses a hand skeleton from them, and `XRController3D` still gets select \u002F grip actions through the hand interaction profiles. Sample finger joints for gesture detection.\n\n> See [references\u002Fhand-tracking.md](references\u002Fhand-tracking.md) for hand-tracking node setup, joint sampling, and gesture-driven interactions.\n\n---\n\n## 4. Grabbing Objects\n\nStandard pattern: an `Area3D` on the controller detects nearby `RigidBody3D` objects; on grip-press, parent the body to the controller and freeze it; on grip-release, restore the parent and apply the controller's velocity to launch.\n\n> See [references\u002Fgrabbing-objects.md](references\u002Fgrabbing-objects.md) for the full physics-based grabbing implementation (GDScript + C#).\n\n---\n\n## 5. XR UI Interaction\n\nFor UI in VR, render a `Control` tree to a `SubViewport`, map its texture onto a `Quad` mesh placed in 3D space. Pointer: a `RayCast3D` from the controller hits the quad, the hit position is converted back to 2D viewport coords, an `InputEventMouseMotion` is forwarded into the SubViewport.\n\n> See [references\u002Fxr-ui.md](references\u002Fxr-ui.md) for the SubViewport-on-quad recipe and pointer\u002Fray interaction.\n\n---\n\n## 6. Passthrough (Mixed Reality)\n\nFor headsets that support it (Quest 2+, Pico 4), set the interface's `environment_blend_mode` to `XRInterface.XR_ENV_BLEND_MODE_ALPHA_BLEND` and clear the `WorldEnvironment` background to transparent. The user sees the real world with virtual content composited on top.\n\n> See [references\u002Fpassthrough.md](references\u002Fpassthrough.md) for the full enabling steps and Quest-specific notes.\n\n---\n\n## 7. Meta Quest Export\n\n### Setup\n\n1. Install the Android build template: **Project → Install Android Build Template...** (4.8: **Project → Setup Android Build...**)\n2. Install OpenXR Vendors plugin: **Project → Project Settings → Plugins** (**Project Settings → Addons → Plugins** on 4.8) → enable `Godot OpenXR Vendors` (or install from AssetLib)\n3. **Export → Add → Android**\n4. In the Android export preset:\n   - **XR Features → XR Mode** → `OpenXR`\n   - **Meta XR Features → Hand Tracking** \u002F **Passthrough** (added by the vendors plugin; shown once the matching OpenXR extension is enabled)\n   - **Architectures → arm64** → enabled (Quest is ARM)\n5. Set the min SDK to what Meta's store requires (29+ when this was written)\n\n### Performance Settings for Quest\n\n| Setting | Recommended Value |\n|---------|-------------------|\n| Renderer | Mobile |\n| MSAA | 2x or 4x (VR needs antialiasing) |\n| Texture Compression | ETC2\u002FASTC |\n| Target FPS | 72 (Quest 2) or 90 (Quest 3) |\n\n> **Critical:** VR must maintain consistent frame rate. Dropped frames cause nausea. Profile aggressively and keep draw calls low.\n\n> ⚠️ **Changed in Godot 4.7:** New project settings `xr\u002Fopenxr\u002Ffoveation_eye_tracked` and `xr\u002Fopenxr\u002Ffoveation_with_subsampled_images` both default to `true` — when the foveation level is not \"Disabled\", eye-tracked foveation is used where the headset supports it, and subsampled images are used on Vulkan for a bigger foveation win. Subsampled images are incompatible with many screen-space features (e.g., FXAA, glow); if any are enabled, subsampled images are automatically disabled with a log warning. Set either setting to `false` to opt out. See [GH-117868](https:\u002F\u002Fgithub.com\u002Fgodotengine\u002Fgodot\u002Fpull\u002F117868).\n\n---\n\n## 8. Godot 4.5+ XR Features\n\nGodot 4.5 adds a D3D12 OpenXR backend on Windows (Quest Link \u002F SteamVR alternative to Vulkan), foveated rendering on the Mobile Vulkan renderer, Application SpaceWarp frame synthesis for Quest\u002FPico, OpenXR Render Models for platform-native controller meshes, and windowed visionOS export via a dedicated visionOS preset. All are core Project Settings except SpaceWarp, which needs the Godot OpenXR Vendors plugin — no engine-level code changes.\n\n> See [references\u002Fgodot-4-5-features.md](references\u002Fgodot-4-5-features.md) for enabling steps, GDScript + C# render-model snippets, and per-feature caveats.\n\n---\n\n## 9. Godot 4.6+ XR Features\n\n### OpenXR 1.1 Support (Godot 4.6+)\n\nGodot 4.6 requests OpenXR 1.1 from the runtime, unlocking 1.1 features (promoted interaction profiles and paths, etc.) without any project-level change, and falls back to 1.0 if the runtime rejects it.\n\n> **Note:** To force a version, set `xr\u002Fopenxr\u002Ftarget_api_version` (e.g. `1.0.48`; empty by default).\n\n---\n\n### Spatial Entities — Anchors, Plane Tracking, Marker Tracking (Godot 4.6+)\n\nGodot 4.6 adds the OpenXR **Spatial Entities** extensions (experimental API): **spatial anchors** that persist virtual object positions across sessions, **plane detection** for floors, walls and ceilings, and **marker tracking** for QR codes and image markers. Enable them under **XR → OpenXR → Extensions → Spatial Entity** (all off by default; anchors with the default `RID()` context also need **Enable Spatial Anchors** and **Enable Builtin Anchor Detection**). Create an anchor with `OpenXRSpatialAnchorCapability.create_new_anchor(local_transform, RID())`, which returns an `OpenXRAnchorTracker`, and show it with an `XRAnchor3D` whose `tracker` is that tracker's name. There is no `XRSpatialAnchor` class.\n\n> See [references\u002Fspatial-entities.md](references\u002Fspatial-entities.md) for the GDScript + C# anchor placement recipe, the C# singleton lookup, anchor persistence across sessions, and the 4.7 `next` parameter on `create_new_anchor()`.\n\n---\n\n## 10. Godot 4.7+ XR Features\n\nGodot 4.7 adds the OpenXR user presence extension: `OpenXRInterface.user_presence_changed(is_user_present: bool)` fires when the headset is put on or taken off (not during startup or shutdown), with `is_user_presence_supported()` and `is_user_present()` to check and poll. Typical use: pause the game and mute audio while the headset is off. `OpenXRCompositionLayer` also gains `eye_visibility` (`EYE_VISIBILITY_BOTH`, `_LEFT`, `_RIGHT`) to show a layer to one eye only, and `create_new_anchor()` gains an optional `next` parameter for vendor create-info structs.\n\n> See [references\u002Fgodot-4-7-features.md](references\u002Fgodot-4-7-features.md) for the user presence and eye visibility recipes (GDScript + C#), and [references\u002Fspatial-entities.md](references\u002Fspatial-entities.md#spatial-anchor-extensibility-godot-47) for the anchor `next` parameter.\n\n---\n\n## 11. Common Pitfalls\n\n| Symptom | Cause | Fix |\n|---------|-------|-----|\n| Black screen in headset | `use_xr = true` not set on viewport | Set in `_ready()` after checking XR interface |\n| Controller input not firing | Wrong signal name for the platform | Check OpenXR action map bindings in Project Settings |\n| Objects scale wrong in VR | Scene not built at real-world scale | Use 1 unit = 1 meter throughout the scene |\n| Motion sickness from locomotion | Smooth rotation | Use snap turning (30° increments) or add a vignette during movement |\n| UI unreadable in VR | Panel too far away or too small | Place UI at 1–2m distance, use SubViewport at 1024+ resolution |\n| Hand tracking jittery | Raw joint data used directly | Apply smoothing (lerp toward new position each frame) |\n| Export fails on Quest | Missing Android build template or wrong architecture | Install the Android build template (4.8: **Setup Android Build...**); enable arm64; set API level 29+ |\n\n---\n\n## 12. Implementation Checklist\n\n- [ ] OpenXR is enabled in Project Settings\n- [ ] Scene uses `XROrigin3D` → `XRCamera3D` + `XRController3D` hierarchy\n- [ ] XR session is started with `get_viewport().use_xr = true` after interface check\n- [ ] World is built at 1 unit = 1 meter scale\n- [ ] Controller input uses OpenXR action names (`trigger_click`, `grip_click`, etc.)\n- [ ] Fallback exists for hand tracking → controller tracking\n- [ ] UI panels use SubViewport rendered on a 3D mesh\n- [ ] Locomotion includes comfort options (snap turn, vignette)\n- [ ] VSync is disabled (XR runtime handles frame timing)\n- [ ] Quest export uses Mobile renderer, arm64 architecture, API level 29+\n- [ ] On Windows Quest Link \u002F SteamVR builds, consider D3D12 backend if Vulkan drivers are problematic (Godot 4.5+)\n- [ ] Foveated rendering enabled via `xr\u002Fopenxr\u002Ffoveation_level` on the Mobile renderer for standalone Quest\u002FPico targets (Godot 4.5+)\n- [ ] Application SpaceWarp evaluated for performance budget on Meta Quest \u002F Pico targets (Godot 4.5+)\n- [ ] `OpenXRRenderModelManager` + `xr\u002Fopenxr\u002Fextensions\u002Frender_model` used for controller visuals where supported (Godot 4.5+)\n- [ ] visionOS export uses the dedicated visionOS preset; windowed apps only through 4.7 (Godot 4.5+)\n- [ ] Spatial anchors are created with `OpenXRSpatialAnchorCapability` and shown with `XRAnchor3D`, with the spatial entities extension enabled (Godot 4.6+)\n- [ ] Headset on\u002Foff handled via `OpenXRInterface.user_presence_changed` — pause\u002Fmute when the user is away (Godot 4.7+)\n- [ ] Foveation defaults reviewed — `xr\u002Fopenxr\u002Ffoveation_eye_tracked` and `xr\u002Fopenxr\u002Ffoveation_with_subsampled_images` are on by default; disable subsampled images if you rely on FXAA\u002Fglow (Godot 4.7+)\n",{"name":5,"description":7},"master","60c28fdc40706a24576731e9fb3508b9c95258ad","skills\u002Fxr-development",63,"https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter","https:\u002F\u002Fgithub.com\u002Fjame581","https:\u002F\u002Fjanmesarc.online\u002F","Software engineer. My biggest passion is game development.","2026-11-14 20:45:49",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add jame581\u002FGodotPrompter --skill xr-development",{"tool":54,"command":55},"bunx","bunx skills add jame581\u002FGodotPrompter --skill xr-development",{"tool":57,"command":58},"pnpm","pnpm dlx skills add jame581\u002FGodotPrompter --skill xr-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter\u002Fblob\u002Fmaster\u002Fskills\u002Fxr-development\u002FSKILL.md",true,[62,68,72,76,80,84,88,92],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fcontrollers-and-input.md","REFERENCE","参考文档",3271,"https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter\u002Fblob\u002Fmaster\u002Fskills\u002Fxr-development\u002Freferences\u002Fcontrollers-and-input.md",{"path":69,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fgodot-4-5-features.md",5842,"https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter\u002Fblob\u002Fmaster\u002Fskills\u002Fxr-development\u002Freferences\u002Fgodot-4-5-features.md",{"path":73,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fgodot-4-7-features.md",2393,"https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter\u002Fblob\u002Fmaster\u002Fskills\u002Fxr-development\u002Freferences\u002Fgodot-4-7-features.md",{"path":77,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fgrabbing-objects.md",4197,"https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter\u002Fblob\u002Fmaster\u002Fskills\u002Fxr-development\u002Freferences\u002Fgrabbing-objects.md",{"path":81,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fhand-tracking.md",2612,"https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter\u002Fblob\u002Fmaster\u002Fskills\u002Fxr-development\u002Freferences\u002Fhand-tracking.md",{"path":85,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fpassthrough.md",1322,"https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter\u002Fblob\u002Fmaster\u002Fskills\u002Fxr-development\u002Freferences\u002Fpassthrough.md",{"path":89,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fspatial-entities.md",4080,"https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter\u002Fblob\u002Fmaster\u002Fskills\u002Fxr-development\u002Freferences\u002Fspatial-entities.md",{"path":93,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fxr-ui.md",1985,"https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter\u002Fblob\u002Fmaster\u002Fskills\u002Fxr-development\u002Freferences\u002Fxr-ui.md",[97,118,148,172,190,206],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":34},"01M6KRF8GZTG1TAS506MFBSGFC","web-services","Use when a Godot game calls a web server — HTTPRequest, downloads, REST\u002FJSON APIs, auth headers, WebSocketPeer clients, TLS, retries, and keeping secrets out of the build. Not for game networking\u002FRPCs (multiplayer-basics) or browser export (web-export)","https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-services\u002FSKILL.md",[],[104,105,106,33,107,32,108,109,110,111,112,113,25,114,115,116,117],"services","web","web services","retries","clients","headers","secrets","json","build","REST","tls","calling","auth","downloads",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":129,"publishedAt":34},"01M6KRF38Q4WSKAYFS56PG87T0","web-export","Use when shipping a Godot game to the browser — Web export preset options, threads vs no-threads and COOP\u002FCOEP headers, hosting on itch.io or your own server, PWA, JavaScriptBridge, user:\u002F\u002F persistence, audio and input limits, and load size","https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-export\u002FSKILL.md",[124],{"categoryNo":125,"categoryName":126,"taxonomyType":127,"taxonomyTypeDesc":128},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[130,131,105,132,133,134,135,136,137,138,139,140,25,141,142,143,144,33,145,146,109,147],"web export","export","shipping","threads","server","Coop","preset","browser","game","io","load","pwa","Audio","size","limits","input","hosting","options",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":162,"publishedAt":34},"01M6KREYFETEBH62ZTN6EZH2X3","using-godot-prompter","Bootstrap skill — establishes how to find and use GodotPrompter skills, with platform-specific tool mapping","https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter\u002Fblob\u002Fmaster\u002Fskills\u002Fusing-godot-prompter\u002FSKILL.md",[154,157],{"categoryNo":155,"categoryName":156,"taxonomyType":127,"taxonomyTypeDesc":128},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":158,"categoryName":159,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[163,32,164,165,25,166,167,168,169,170,171],"using godot prompter","find","with","tool","platform","mapping","how","how to","bootstrap",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":178,"publishedAt":34},"01M6KRER5G7EQWKGAFN8QJKQ69","tween-animation","Use when implementing tweens — property animation, method tweening, chaining, parallel sequences, easing, and common UI\u002Fgameplay motion recipes","https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter\u002Fblob\u002Fmaster\u002Fskills\u002Ftween-animation\u002FSKILL.md",[],[179,180,181,182,33,25,183,184,185,186,187,188,189],"Animation","tween animation","parallel","sequences","motion","gameplay","chaining","ui","recipes","common","implementing",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":196,"publishedAt":34},"01M6KREKGCQMVDV8WX7HWX8BZG","state-machine","Use when building a state machine or refactoring logic into one — enum, node, and resource-based FSM patterns with trade-offs. Not for adding states to an existing one","https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter\u002Fblob\u002Fmaster\u002Fskills\u002Fstate-machine\u002FSKILL.md",[],[197,198,199,200,201,202,165,25,189,203,204,33,32,205],"state machine","state","machine","fsm","state machines","trade","trade-offs","node","patterns",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":210,"categories":211,"keywords":212,"publishedAt":34},"01M6KREE370Y80QK838PCRBA0S","shader-basics","Use when implementing shaders — Godot shader language, visual shaders, common visual recipes, and post-processing effects","https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter\u002Fblob\u002Fmaster\u002Fskills\u002Fshader-basics\u002FSKILL.md",[],[213,214,215,187,33,32,216,217,218,219,188,220,221,25,189,222],"shader","shader basics","basics","language","post-processing","shaders","post","visual","effects","processing"]