Support Apple Sharp preview in 3d node

[jtydhr88]

as testing https://github.com/PozzettiAndrea/ComfyUI-Sharp, preview 3d node doesn't perform well as https://github.com/yichengup/ComfyUI-gaussian_preview

currently it is missing extrinsics and intrinsics from output, we need to find it out how to support it

┆Issue is synchronized with this Notion page by Unito

[dosubot]

To support Apple SHARP in the 3D node with proper camera intrinsics and extrinsics output (for better preview and downstream processing), you’ll need to extend the current 3D preview node logic. Right now, the frontend nodes (like Load3D and Preview3D) only output basic camera state—position, target, zoom, camera type, and field of view—under the camera_info field. They do not expose the full camera projection (intrinsics) or view (extrinsics) matrices needed for high-fidelity 3D visualization or for matching the SHARP/gaussian_preview outputs.

The core camera logic is managed by the CameraManager class, which already maintains all the necessary data internally (using THREE.js). To expose full intrinsics and extrinsics, you should:

1. Update the serialization logic in the 3D node (e.g., in sceneWidget.serializeValue for Load3D/Preview3D) to include the camera’s projection matrix (intrinsics) and view matrix (extrinsics) in the output, alongside the current camera state.
2. Extend CameraManager to provide methods for retrieving these matrices in a serializable format (e.g., as arrays).
3. Add these matrices to the node’s output (e.g., as camera_intrinsics and camera_extrinsics fields in the output object).

This will allow downstream nodes or external tools to consume accurate camera parameters for rendering or further processing, similar to what’s needed for SHARP or gaussian splatting workflows. The frontend’s 3D infrastructure is already centralized, so these changes can be made in the Load3D/Preview3D node and CameraManager without major refactoring. For reference, see the relevant code and structure in the frontend’s core 3D node implementation and camera manager logic (source, source).

This approach will bring the 3D node’s output in line with what’s needed for accurate SHARP/gaussian preview and enable better 3D scene understanding and visualization.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

  

[PozzettiAndrea]

If I may add some helpful context, this could also be due to output format channel ordering, sometimes gaussians are written wxyz and sometimes xyzw

[jtydhr88]

Oh great! Thanks for the update!