HYWorld2 Workspace
The anchor every HY-World2 scene hangs from
- panorama
- workspace
- info
If the rest of this pack is the car, this is the garage. HYWorld2 Workspace is the entry node for the whole HY-World2 scene pipeline, and honestly it does almost nothing - which is exactly the point. It defines where on disk one scene lives and what it's called, then hands that bundle to every heavier node downstream. It's the shared address book for the scene, and nearly every other HYWorld2 node (Trajectories, Memory Bank, World Expansion, GS Data, Train 3DGS) takes this HYWORLD2_WORKSPACE as its first input.
This pack is AHEKOT's ComfyUI integration of Tencent's HY-World 2.0 / WorldMirror - the world-model family that reconstructs an explorable 3D scene (gaussian splats, point clouds) from a single image or panorama. The pipeline is long and heavy; the Workspace node is deliberately boring so the interesting nodes don't have to agree on a folder path with each other.
How it works
You give it a workspace_name, and optionally a root_dir and scene_dir. If scene_dir is empty it resolves one under the pack's workspaces root for you. The result_name (default worldstereo-memory-dmd) is the results-folder name later stages write into - think of it as the scene's project name. The node resolves paths, makes sure the folder structure exists, and passes a workspace dict forward. It also has an IS_CHANGED keyed on scene_dir, so Comfy won't re-run your whole world pipeline just because you bumped a widget somewhere upstream.
The inputs that matter
You only really set three things as a beginner:
workspace_name- pick a stable, descriptive scene name. This is your project folder.scene_dir/root_dir- leave empty until you have a reason to move scenes off the default root.panorama- optional, but drop your equirectangular image here so the downstream stages know the source. There's also ascene_typehint (unknown/indoor/outdoor) and theresult_namementioned above.
Outputs
workspace(HYWORLD2_WORKSPACE) - wire this intoTrajectories,Memory Bank, and friends.info- a JSON string describing the resolved paths, handy for the debug-minded.
Install
The pack installs through ComfyUI Manager (search HY-World 2.0) or manually:
cd ComfyUI/custom_nodes
git clone https://github.com/AHEKOT/ComfyUI_HYWorld2
cd ComfyUI_HYWorld2
pip install -r requirements.txt
python install.py
install.py is not optional decoration - it builds the vendored gsplat fork and the recast navmesh wheel that trajectory planning needs. Do not install upstream gsplat separately, or you'll break every HYWorld2 node that rasterizes. Expect a CUDA toolkit matching your PyTorch, ninja, and (on Windows) MSVC build tools. First runs of the real nodes pull models from Hugging Face automatically; this node itself needs nothing.
Common issues
Because it's the shared root, most failures show up here as symptoms of bad wiring, not causes. If a downstream node complains that the workspace and trajectory_set come from "different scene directories", you reused a workspace for two scenes - make one Workspace per scene and stick to it. If info shows missing_or_unresolved, your scene_dir never resolved; point it at a real path. There's genuinely not much else that can break in a path resolver, which is a nice change of pace from the rest of this pack.
Inputs (6)
| Name | Type | Default | Description |
|---|---|---|---|
| workspace_name | STRING | comfy_worldgen | — |
| root_diropt | STRING | — | |
| scene_diropt | STRING | — | |
| panoramaopt | IMAGE | — | |
| scene_typeopt | COMBO | unknown | 3 options: unknown, indoor, outdoor |
| result_nameopt | STRING | worldstereo-memory-dmd | — |
Outputs (2)
| Name | Type | Description |
|---|---|---|
| workspace | HYWORLD2_WORKSPACE | — |
| info | STRING | — |