3d-production-workflow

3D Production Workflow

Move from a generated model to a playable work or deliverable film. Use the project's chosen engine and technical skills; this workflow does not install tools, grant spending permission or establish production readiness.

Decompose the work before generating assets

• List subjects, environment, interactions, cameras and motion from the target frame or gameplay. With reference images, distinguish occlusion, perspective, silhouette and lighting; a hidden back surface is unknown, not established geometry.
• Keep a small production manifest: stable asset ID, purpose, reuse, provenance/license status, creation method, scale/axes, material style, performance limits and acceptance viewpoints.
• Prove space, camera framing, reachability and gameplay with a graybox first. Prefer procedural geometry for simple platforms, crystals and collision shapes. Consider generated/external assets when complex silhouettes matter to recognition, not for every object.
• If references are absent, make a composition sketch or graybox and record design choices. Do not buy or upload material merely to satisfy a reference step.
• Test the delivery path with a minimal sample before expensive production: authentication, accepted formats/MIME, CSP, size limits, playback/download. Local rendering success is not hosted delivery. If unsupported, preserve the original files and report local-file delivery limits; do not bypass login, modify the host without approval, or call a frame preview MP4 playback.

Generation is not assembly

• Confirm model/quality, expected cost, task count and retry limits before generation. Without spending approval, continue only with grayboxing and free steps.
• For optional Tripo, use the configured UXC interface and local connection instructions. Discover operations, inspect schemas and verify current official pricing; do not guess parameters from tutorials or mix API versions. Require both UXC ok == true and Tripo data.code == 0.
• Distinguish request acceptance, remote terminal success, download and scene import. Record the task ID before waiting. After uncertain submission, reconcile known tasks/usage before retrying a chargeable request.
• Preserve original models and reproducible import settings. Record provenance, generation parameters, actual credits and license status, not keys or signed download URLs. Downloading from a third-party CDN must not forward the service API key.
• Inspect readable meshes/textures, bounds, units, up/forward axes, origin, color space and triangle count. Normalize scale/orientation in an explicit scene adapter rather than repeatedly destructively editing the source.