[Collaboration] Tripo DevRel: the image-to-3D step in game-build

[Tracy-Huang3D]

Hi @pitechen,

I've been reading through NovelToGame, especially Project Plateau. The asset ledger is a good piece of work: every adopted asset carries its source files, fallback and rights note, and the field camera, rifle and both creature meshes are traced back to an ImageGen reference reconstructed with Hunyuan 3D. The Blender reference in game-build has the same discipline, reading the export back through the target loader and keeping the original if a candidate doesn't improve the approved goal.

I'm Tracy from the Developer Relations team at Tripo. We work on 3D generation: text or image to 3D models, exported as GLB.

What stood out is that the image-to-3D step carries a lot of the Plateau example, but the skills don't have a reference for it yet. game-build has on-demand guidance for Blender and for dynamic media, and the media contract already says the tool is decided by the environment. I'm wondering whether you'd want that step covered in the same tool-neutral way, with Tripo as one option a user could pick next to Hunyuan, not a replacement or a default.

Two things I'd like to understand first:

• Would a short on-demand reference for "approved concept image to mesh" fit how you want game-build to grow, or do you prefer to leave that step entirely to the environment?
• The ledger asks to keep "the applicable provider output-rights records". If a user picked a second provider, which fields would you want recorded, so the rights boundary stays as clear as it is now?

We'd love to explore whether there might be an opportunity to collaborate, in whatever way makes the most sense for your project. Would you be open to a quick conversation about it?

Best,
Tracy Huang
Developer Relations
Tripo AI
huangyichen@vastai3d.com