Define Gameplay Function
Specify dimensions, camera distance, interaction, movement, collision, breakage, sockets, and whether the prop is hero, modular, repeated, or background content.
Design generation briefs around a prop’s gameplay role, then review consistency, scale, construction, materials, and batch behavior before Unreal import.
Prepare the handoff
Direct answer
For Hyper3D Rodin text-to-3D or image-to-3D props, start with the gameplay function rather than appearance alone. Define real-world size, view distance, interaction, material family, movable parts, and budget. Generate a small comparison set, select against those criteria, then normalize scale and pivots, repair geometry and maps, and validate the whole prop family together in Unreal.
Starter prompts
Choose a scoped brief, then replace its assumptions with measurements from the real exported asset and your Unreal project.
Workflow
A strong generation brief connects the reference to construction, gameplay, and batch constraints.
Specify dimensions, camera distance, interaction, movement, collision, breakage, sockets, and whether the prop is hero, modular, repeated, or background content.
Describe silhouette, construction, materials, wear, reference certainty, forbidden details, and how variants should remain recognizably related.
Compare multiple generations on proportions, completeness, topology, UVs, map usefulness, editability, consistency, rights, and estimated cleanup effort.
Align scale, pivots, naming, material families, texel density, collision, and budgets, then review the full batch inside one Unreal test scene.
Outputs
Each output names an asset decision, its supporting evidence, and the work that remains inside Unreal or the source pipeline.
A text or image-to-3D prompt grounded in dimensions, construction, materials, gameplay role, constraints, and required variants.
Comparable evidence for choosing one result based on production fit rather than the most attractive preview render.
Shared scale, pivot, naming, material, texel-density, collision, and budget rules for a coherent Unreal set.
A test scene and checklist that exposes inconsistent proportions, shading, density, materials, and performance across many generated props.
Decision guide
| Asset or issue | Review focus | Approval evidence |
|---|---|---|
| Text-to-3D hero prop | Strong function, dimensions, construction, and material hierarchy | Reject attractive results that cannot support gameplay or editing |
| Single-image reconstruction | Explicit uncertainty for hidden sides, depth, thickness, and unseen parts | Have a human design the missing construction |
| Variant batch | Shared visual grammar plus controlled silhouette and wear changes | Review all variants side by side for drift |
| Modular kit | Exact connection dimensions, pivots, grid rules, seams, and material reuse | Assemble the kit before investing in polish |
Trust boundary
FAQ
Neither input is universally better. Text can define function, dimensions, construction, and variants, while images can anchor silhouette and surface appearance. A single image also leaves depth and hidden sides ambiguous. Use the input that carries the most reliable constraints, then document uncertainty and compare multiple results against an Unreal-focused scorecard.
Include the prop’s role, real-world dimensions, view distance, interaction, silhouette, construction, materials, movable parts, damage level, pivot expectations, and variant rules. Avoid ornamental detail that conflicts with gameplay or budget. The prompt should help select a usable asset, not merely produce a dramatic isolated render with unclear scale.
A single photo does not reveal every dimension, hidden surface, thickness, or internal construction, so an exact reconstruction should not be assumed. Treat visible evidence separately from inferred design, add more views or measured references where possible, and have a human resolve unseen areas before the model is used for accurate product, gameplay, or safety-critical representation.
Lock shared dimensions, material families, construction logic, texel density, edge treatment, naming, and lighting-neutral review criteria. Generate a small anchor set first, then compare every new variant beside it. Batch review is essential because isolated previews can hide drift in scale, proportions, roughness, detail density, and wear language.
A modular prop needs more than a matching look. It requires exact connection dimensions, predictable pivots, grid alignment, clean seams, consistent normals and texel density, reusable materials, collision rules, and a test assembly. Generate and approve modules as a kit; otherwise small inconsistencies accumulate into visible gaps and level-design friction.
Inspect individual defects, but set budgets and approve performance as a batch. Repeated props share the same frame, memory, shader, collision, and streaming environment. A mesh that looks inexpensive alone may become costly at realistic counts. Build a representative Unreal test scene and profile the expected mix, distances, and materials together.
Bring the exported asset, target platform, intended scene role, and known constraints. SEELE can help organize inspection, cleanup, conversion, optimization, and review notes without claiming to replace engine validation.
Open SEELE AI