Repository navigation
Conversation
Preview approval requiredThis pull request comes from a fork, so Mintlify won't build a preview until someone with write access approves commit |
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
…views Adds a section for the templates_mjm_image_to_3d template: one photo goes in, Nano Banana 2 renders the side and rear views, and the Tripo image-to-model node builds the mesh from the background-removed photo. Also restores the Cloud, download and input cards on the Korean page so its structure matches the English source.
02cbae2 to
cb39eea
Compare
@lin-bot23
Adds the missing docs for the
templates_mjm_image_to_3dworkflow, which is live in Comfy Cloud and in the template library but had no mention anywhere in the docs.What is documented
A new section, Single-Image to Model with Generated Views, on
tutorials/partner-nodes/tripo/model-generation.mdx(en, zh, ja, ko, es):ComfyUI/output/3d/).Korean page restoration
The Korean page was missing the Cloud card, download card and input card for the Image-to-Model workflow (it still used the old raw link button). Restored to match the English structure, with the same hrefs.
Fact sources
workflow_templates/templates/templates_mjm_image_to_3d.json: node list and wiring.BatchImagesNode.image0is the background-removed original (link 28) and feedsTripoImageToModelNode.image(link 5); the side and rear frames are slots 1 and 2 and are only wired toSaveImage. ThreeGeminiNanoBanana2nodes,Preview3D, andSaveGLBwith prefix3d/tripo_image2model.comfy_api_nodes/nodes_tripo.py:TripoImageToModelNodetakes a singleimageinput and callsupload_images_to_comfyapi(cls, image, max_images=1), which is why the generated views do not reach the API.TripoMultiviewToModelNodeis the node that accepts separate front, left, back and right images.comfy_api_nodes/nodes_gemini.py: the Nano Banana 2 display name.Verification
check-structure-parity.ts --base=upstream/main: OK. The remaining Korean h3 difference is pre-existing drift and is reported as such.check-anchors.pyon the five page files: OK.##headings and 3###headings in every locale, identical CardGroup/Card/img counts, no em dashes, no leading pipes.Note for reviewers:
templates/index.jsonlistsMeshyundermodelsfor this template and its description says the views are used with Meshy, while the template JSON uses the Tripo node. The page follows the actual workflow. The template also ships the legacy Tripo image-to-model node (is_deprecated=True) and batches three images into a single-image input, so the side and rear views are generated but unused. Worth fixing in the template rather than in the page.