[Feature Request] Supported Unity/Android client path for a native Meta Quest robot teleoperation app
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
首先检查现有的浏览器客户端和 examples/isaac_teleop_to_so101 工作流，以及所引用的 CloudXR.js 文档。确定是否存在适用于 CloudXR Runtime 6.x 和 Isaac Teleop 的受支持 Unity/Android 客户端路径。完成标准是具备一条有文档说明或有示例支持的原生 Quest 路径，涵盖流式传输、控制器操作、机器人摄像头视图和安全断开连接。
由索引模型根据 Issue 内容生成。
描述
Is your feature request related to a problem? Please describe.
I would like to build a native Unity/OpenXR application for the Meta Quest Store that allows users to:
- view low-latency live video from a real robot;
- control the robot using Quest Touch controllers;
- use clutch, gripper, stop/hold, and disconnect controls inside the application.
I have already successfully tested the following real-hardware workflow:
Quest 3S Touch Plus controllers
→ CloudXR Runtime 6.2.0
→ NVIDIA Isaac Teleop 1.3.131
→ LeRobot v0.6.0 official examples/isaac_teleop_to_so101 example
→ SO-101 Follower robot
Test system:
- Ubuntu 24.04
- NVIDIA RTX 4080
- Quest 3S
- SO-101 robot arm
The Quest controller poses and buttons reached the Ubuntu host correctly. Grip/Squeeze worked as the clutch, Trigger controlled the gripper, and the SO-101 followed the controller successfully.
The existing browser client is excellent for validating the workflow. However, for an application that can be distributed through the Meta Quest Store, I need a native Unity/Android client with its own UI, connection flow, camera layout, robot selection, and safe-disconnection behavior.
My understanding is that the current CloudXR 6.
https://github.com/user-attachments/assets/e5cf9dcf-1734-42d9-aee0-9f998278e5ad
x documentation supports Quest through CloudXR.js in the browser, but I could not find a supported, redistributable native Unity/Android client path compatible with CloudXR Runtime 6.x and Isaac Teleop.
Please correct me if an existing supported option already covers this use case.
Describe the solution you'd like
Ideally, NVIDIA would provide one of the following:
- A supported CloudXR Unity package or Android client SDK compatible with CloudXR Runtime 6.x; or
- A stable and documented client API, together with a minimal Unity/OpenXR sample.
The Quest client should ideally support:
- receiving the low-latency streamed XR view;
- displaying one or two real robot camera views;
- sending HMD and Touch-controller poses and actions upstream;
- Unity OpenXR integration;
- connection, reconnection, latency, and streaming-quality status;
- Grip-to-clutch and Trigger-to-gripper mappings;
- a clear stop/hold state after clutch release or connection loss;
- redistribution as part of a Meta Quest Store application.
A first MVP could be LAN-only:
Robot camera(s)
→ camera_viz / Televiz
→ CloudXR Runtime
→ Native Unity app on Quest
Quest controller poses and buttons
→ CloudXR
→ Isaac Teleop
→ LeRobot
→ SO-101- 主要语言
- Python
- 星标
- 393
- 派生
- 93
- 平均合并
- 2 天 5 小时
- 30 天内合并 PR
- 95
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
NVIDIA/IsaacCapture 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
NVIDIA/IsaacCapture#910 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 88/100
NVIDIA/IsaacCapture#891 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 25/100
NVIDIA/IsaacCapture#1217 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 20/100
NVIDIA/IsaacCapture#1214 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 50/100
NVIDIA/IsaacCapture#1181 ·
维护者通常 1 天内回复
查看 NVIDIA/IsaacCapture 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
task
难度 2/5 1-3 小时 新手友好度 78/100
danparshall/claude_researcher#87 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 85/100
datajoint/datajoint-python#1586 ·
维护者通常 1 天内回复
-
1D intercept of length 1 is accepted as `fix_params` in population GLM with more than 1 unit可能已有人在做 @dhvani7014 今天认领。 未关闭bug good first issue
难度 2/5 1-3 小时 新手友好度 72/100
flatironinstitute/nemos#642 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 78/100
uniswap-python/uniswap-python#487 ·