Limits & FAQ限制与常见问题
Real or preview真实还是预览
| In the app应用中 | Status状态 |
|---|---|
| Worlds 01 to 04世界 01 至 04 | Real: Manycore-hosted splats and voxel grids, streamed from the CDN真实:由 Manycore 托管的高斯点与体素网格,从 CDN 流式加载 |
| World 05, coffee bar世界 05,咖啡吧 | Real: our SpatialGen job (world 3FO4K4V99KMD), mirrored into the repo真实:我们的 SpatialGen 任务(世界 3FO4K4V99KMD),已镜像到仓库 |
| Espresso machine, parts and joints意式咖啡机及其部件与关节 | Real: Lux3D tasks 8353478, 8354166 and 8354168真实:Lux3D 任务 8353478、8354166 和 8354168 |
| The actor and its eight clips角色及其 8 个动作片段 | Real: Lux3D tasks 8354807, 8355123 and 8359816真实:Lux3D 任务 8354807、8355123 和 8359816 |
| Patrol drone and holo-terminal props巡逻无人机与全息终端道具 | Procedural previews, hand-built and labelled in the app程序化预览,手工搭建,并在应用中标注 |
| Text to 3D drop-in without a key无密钥时的文生 3D 投放 | Cached: the stored G1-Turbo result of task 8353472, labelled缓存结果:任务 8353472 存储的 G1-Turbo 结果,并有标注 |
| Other jobs without a key无密钥时的其他任务 | Preview receipts; nothing is sent to Aholo预览调用回执;不向 Aholo 发送任何内容 |
| Co-directorAI 副导演 | Real plan, deterministic keyword planner; it does not start jobs真实的规划,来自基于关键词的确定性规划器;不会启动任务 |
| LuxReal videoLuxReal 视频 | Hand-off only: Holorra exports the prompt, camera data and frames仅负责交接:Holorra 导出提示词、镜头数据和画面帧 |
How keys are handled密钥如何处理
- Server key (
AHOLO_API_KEY) stays on the server. It is never sent to the browser, and/api/aholo/statusreports only whether one is present.服务端密钥(AHOLO_API_KEY)只留在服务端,永远不会发送到浏览器;/api/aholo/status只报告是否存在密钥。 - Your key, if you paste one, is stored in your browser's local storage and sent only to Holorra's own
/api/aholo/*routes asx-aholo-api-key. The routes pass it to the SDK for that request and do not log or store it.你的密钥(如果粘贴了)保存在浏览器的本地存储中,只会以x-aholo-api-key的形式发送到 Holorra 自己的/api/aholo/*接口。接口只在该次请求中把它交给 SDK,不会记录日志,也不会保存。 - The asset proxy is not an open proxy: https only, a fixed list of Aholo result hosts, every redirect re-checked, 60 s and 120 MB limits. See HTTP API.资源代理不是开放代理:仅限 https,只放行固定的 Aholo 结果主机列表,每次重定向都重新校验,并有 60 s 和 120 MB 的限制。见 HTTP API。
- The repository contains no keys;
.env.localis git-ignored and.mcp.jsonships a placeholder.代码仓库不包含任何密钥;.env.local已被 git 忽略,.mcp.json中只有占位符。
Known limitations已知限制
- Collision exists only in the loft and the plaza. The concourse, turntable and coffee bar use a fixed floor height, so you can walk through their walls.碰撞只在公寓和广场中生效。枢纽大厅、物体转台和咖啡吧使用固定的地面高度,所以可以直接穿墙。
- New SpatialGen worlds are not added to the world tabs automatically; adding one means mirroring its splat file and writing a preset, as we did for world 05.新的 SpatialGen 世界不会自动出现在世界切换栏中;要添加一个,需要镜像它的高斯点文件并编写预设,就像我们为世界 05 做的那样。
- Drop-ins are cosmetic: they fall and settle but are not saved with the scene and do not collide with the actor.投放的模型只是视觉效果:它们会下落并停稳,但不会随场景保存,也不会与角色发生碰撞。
- Retarget results come back as one GLB with generic clip names (
animation_1...); the studio maps them by request order.动画重定向结果以单个 GLB 返回,动作片段名称是通用的(animation_1...);创作台按请求顺序把它们对应起来。 - Heavy worlds on phones. The 41.8M-splat plaza streams by LOD but can be slow on older devices.手机上的重型世界。拥有 41.8M 个高斯点的广场虽然按 LOD 流式加载,在旧设备上仍可能较慢。
FAQ常见问题
Do I need an API key to try it?试用需要 API 密钥吗?
No. Worlds, play mode, explode, articulation, the actor, the camera path and the bench all work without one. A key is only needed to start new Aholo jobs.不需要。世界、游玩模式、爆炸视图、关节化、角色、镜头路径和测试台都无需密钥即可使用。只有发起新的 Aholo 任务时才需要密钥。
Why does a live job take minutes?为什么实时任务要几分钟?
Generation runs on Aholo's cloud. Our runs took 81 s to 343 s for Lux3D and 625 s for a SpatialGen world. The studio stays playable while you wait, and Text to 3D results drop into the scene when they are done.生成在 Aholo 云端运行。我们实测 Lux3D 任务耗时 81 s 至 343 s,SpatialGen 世界耗时 625 s。等待期间创作台照常可玩,文生 3D 的结果完成后会直接投放到场景中。
Which browsers work?支持哪些浏览器?
Any browser with WebGL2 and module Web Workers: current Chrome, Edge, Safari and Firefox. The chunk-LOD worlds are heavy; on phones the loft and coffee bar are the smoothest.任何支持 WebGL2 和模块化 Web Workers 的浏览器都可以,包括当前版本的 Chrome、Edge、Safari 和 Firefox。分块 LOD 世界负载较重;在手机上,公寓和咖啡吧最流畅。
Can I use my own model?可以用我自己的模型吗?
Yes. Send a GLB URL to part split, articulation, auto-rig or export from the Lux3D tab. Hosts must be reachable by the Aholo API.可以。在 Lux3D 标签页中把 GLB URL 提交给部件拆分、关节化、自动绑骨或导出即可。文件所在的主机必须能被 Aholo API 访问。
Why is there only one actor?为什么只有一个角色?
Manycore's demo GLBs had root scales of 1.78e-5 and 0.0035 and rendered invisibly on this stage, so we removed them rather than ship a broken option. The actor you get is our own Lux3D result.Manycore 的示例 GLB 根节点缩放分别为 1.78e-5 和 0.0035,在这个舞台上渲染出来完全看不见。与其提供一个坏掉的选项,我们选择移除它们。你现在使用的角色是我们自己的 Lux3D 结果。