docs: clarify that body tracking requires Pico 4 Ultra Enterprise#804
Merged
Merged
Conversation
PICO only exposes WebXR body tracking on the Pico 4 Ultra Enterprise; the consumer Pico 4 Ultra cannot stream body tracking data even with Motion Trackers paired. The docs only hinted at this via an '(Enterprise enabled)' note on the browser version, which readers missed (NVIDIA#789). - ecosystem: lead the Pico Motion Tracker notes with the Enterprise headset requirement and link the Enterprise product page - body_tracking: state the Enterprise requirement up front in an 'important' admonition and add a troubleshooting entry for the consumer edition Fixes NVIDIA#789 Signed-off-by: Jiwen Cai <jiwenc@nvidia.com>
Contributor
|
📝 Docs preview is not auto-deployed for fork PRs. A maintainer with write access to |
Contributor
📝 WalkthroughWalkthroughThe documentation now specifies that body tracking requires a PICO 4 Ultra Enterprise headset, supported PICO Browser software, and paired PICO Motion Trackers. It explicitly states that the consumer PICO 4 Ultra does not grant the Estimated code review effort: 1 (Trivial) | ~3 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
yanziz-nvidia
approved these changes
Jul 18, 2026
yanziz-nvidia
left a comment
yanziz-nvidia
left a comment
Contributor
There was a problem hiding this comment.
I think wording is a bit strong. e.g. you can ask user to contact PICO to activate enterprise on consumer devices.
jiwenc-nv
enabled auto-merge (rebase)
July 18, 2026 20:39
jiwenc-nv
disabled auto-merge
July 18, 2026 20:39
Consumer devices are not a dead end: PICO can activate enterprise features on them, via the 'Activate enterprise account' option in the headset settings. Soften the wording accordingly instead of stating body tracking is impossible on consumer devices. Signed-off-by: Jiwen Cai <jiwenc@nvidia.com>
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.
Fixes #789
PICO ships WebXR body tracking as an enterprise feature: it works out of the box on the Pico 4 Ultra Enterprise, while a consumer Pico 4 Ultra does not grant the
body-trackingWebXR feature by default — even with Motion Trackers paired. Consumer devices can gain it through enterprise activation (contact PICO, then Activate enterprise account in the headset settings). Our docs only hinted at this via a(Enterprise enabled)parenthetical on the browser-version requirement, which the reporter of #789 (reasonably) missed.Changes
overview/ecosystem.rst(the page linked from the issue)(Enterprise enabled)parenthetical is gone.device/body_tracking.rstimportantadmonition at the top of the page stating the enterprise-feature requirement and the activation path for consumer devices.Docs build clean with Sphinx (no new warnings); the Enterprise product page URL was verified live.