MeshForgeCloud

0.3.x

0.3.0

21 September 2026 · Download (363 KB) · Release on GitHub

Added

• meshy-7.1, and it is the new default for the Standard pipeline. Same fields and the same price as meshy-7, with finer geometry; the vendor has deprecated meshy-7 and now resolves latest to 7.1. A definition that names meshy-7 keeps naming it, and it still runs. meshy-6-lite is offered too, because the vendor accepts it — untested here.
• geometry_resolution — standard, 2k or 4k — replacing ultra_mode, which Meshy deprecated. It is how finely the shape is reconstructed and is easy to confuse with texture_resolution, which is unchanged and separate. standard is what ultra_mode: false gave and 2k is what ultra_mode: true gave, so a saved definition is carried across to 2k on load and keeps producing what it produced. 2k and 4k cost the same five extra credits; 4k needs meshy-7.1 or latest and a single picture, and asking for it elsewhere is refused with the reason rather than sent. Measured why that matters: Meshy accepted 4k on meshy-6 without a word of complaint, produced a mesh, and charged for the run — a setting silently dropped is worse than one refused.
• Tripo can retexture a mesh it did not make. It used to refuse one outright and tell you to go and use the Meshy step instead. POST /v3/files takes a .glb by the same plain multipart the plugin already used for pictures, and /v3/models/texture accepts the token it returns — the endpoint says so itself when refused: "must be a valid task_id (UUID), file_token, or URL". So a CC5 shirt, a kitbash, a corridor somebody modelled all retexture on Tripo now, for the same 10 credits. Measured: a 0.4 MB upload, textured in about a minute. An older note in this family held that our own meshes needed Tripo's STS route and therefore an AWS SigV4 signer; that was true of the v2 API and is not true of v3 — no signing, no S3, no extra dependency.

Changed

• Both retexture steps ask the same question, and a better one. Each used to ask "was the step before me this vendor", which a local step in between silently invalidated. They now ask whether the vendor's copy is still the mesh in hand, and upload whenever it is not.
• An expired task is no longer a failed run. Meshy keeps a task for days, so a fortnight-old take is perfect lineage pointing at nothing — measured: HTTP 404, and the whole chain stopped. The step now uploads the mesh it is already holding and carries on, and says in its summary that it did. Nothing is billed for the refused attempt.
• Tripo asks whether you are building from words or from a picture. Both Tripo generators have a type at the top of their settings: image_to_model shows the picture it will send, with multiview_to_model beneath it for up to four views; text_to_model shows the prompt and sends no picture. It used to be decided for you - any main picture in the definition turned a text request into an image one and dropped the prompt without a word - and the Mesh stage would not run a text request at all without a main picture. text_to_model is 10 credits cheaper on the H-series and P1 models, and the quoted price follows the choice. Existing definitions stay on image_to_model, which is what they were sending.

Fixed

• Tripo's retexture no longer refuses a picture it is looking at. Its style picture was offered in every mode but only accepted beside a written description, so a picture dropped there with the surface set to come from pictures - while image / images held one empty slot - was refused with "one image or exactly four", which read as though the step could not see the mesh. The field is now style_image, shown only with text_style_prompt, and an empty picture list says so.

Compatibility

• Needs MeshForge 0.3.0 or later.

0.2.x

0.2.1

8 September 2026 · Download (350 KB) · Release on GitHub

• Packaging fix: the release now carries everything the register allows. BuildPlugin's filter excludes Config/ and every public_extra path, so earlier zips shipped without them.

0.2.0

7 September 2026 · Download (349 KB) · Release on GitHub

• Migrated the shared Tripo HTTP transport, generation, image pipeline, retexture pipeline and image-generation model IDs to Tripo API v3.
• Added native Tripo v3 generation and P2 provider support; exposed and implemented Tripo P2 pipeline controls.
• Raised the Tripo credit guardrail for P2 pricing; tightened v3 request shapes and cost estimates.
• Allowed v3 Extreme textures on H-series and P1.
• Documented that quads do not survive Unreal import; updated the Tripo docs to match the v3 vendor surface; the Cloud README now admits there are two vendors.
• Restored property hints that had been lost; aligned the Tripo surface with v3 documentation.
• Repointed every plugin's Docs/Support URLs at kovati.dev.
• Folded in the garment-fit prototype work merged from a parallel branch (region-aware fitting, collision correction, async job manager, Blender container, hardened solver, tests) — later split out into the standalone MeshForgeGarment plugin.
• Added a garment generated from the character's own picture, placed rather than fitted; added a generated shirt onto a MetaHuman.
• Merged SurfaceForge (PR #4).

0.1.x

0.1.0

1 September 2026 · Download (357 KB) · Release on GitHub

• Initial release: FMeshyProvider (text-to-image, image-to-3d, multi-image-to-3d, retexture) and FTripoProvider (photoreal + P1 game-ready mesh, image generation, multiview, retexture) both shipped as hosted providers.
• Established Meshy's two-mode quality ladder (Smart Topology vs. Standard) with corrected image pricing.
• Built and proved Tripo against the live v2/openapi API (later superseded by v3), including the discovery that quad topology cannot survive Interchange's FBX import.
• Wired per-vendor keys into the family's shared key store; documented that MeshForge Cloud asks for its own keys.