Build an AI 3D game prototype by combining generated props and worlds with collision, controls, interaction, and a tested Unity or Unreal export path.
Direct answer
Build an AI 3D game prototype by defining one playable loop, generating only the assets and environment needed for that loop, importing them into Unity or Unreal, then adding collision, controls, triggers, feedback, and a measurable performance budget.
| Prototype need | Suggested lane | Output | Engine work still required |
|---|---|---|---|
| Props or pickups | Tripo, Meshy, Rodin, Hunyuan3D | GLB or provider-native FBX | Scale, pivot, collision, materials, LOD |
| Explorable visual world | Marble or Hunyuan World | Mesh, splat, or world package | Collision, navigation, lighting, optimization |
| Fast environment shell | Skybox AI | Panorama, cubemap, or GLB | Camera limits and foreground geometry |
| Playable loop | Unity or Unreal | Project build | Controls, state, goals, failure, feedback |
Output formats
SPZ stores compressed 3D Gaussian splats rather than a conventional polygon mesh. It retains splat attributes such as position, scale, rotation, opacity, color, and spherical harmonics while reducing file size. Use an SPZ-compatible splat viewer and confirm coordinate-system handling before moving the scene between tools.
SOG means Spatially Ordered Gaussians. It is a lossy, compact container made from a metadata file and compressed image data that stores the properties of a Gaussian-splat scene. Treat the download as a file set and keep its files together when hosting or importing it.
PLY is an openly documented format for vertices and optional polygon faces with custom per-element properties. In a world-generation workflow, a PLY may contain Gaussian-splat point attributes rather than a ready-made triangle mesh. Inspect the header and use a compatible splat tool before assuming it will behave like an OBJ or GLB.
DRC is a raw file compressed with Google Draco, a library for meshes and point clouds. It is optimized for storage and transmission, but it is not a complete scene package by itself: materials, textures, cameras, and other world data may be delivered separately or omitted.
WORLD labels the primary scene file returned by the Hunyuan World provider; it is not a universal interchange standard like glTF. Preserve the original filename and any companion files, then use the provider's documented workflow or convert the result before opening it in a general 3D tool.
A world GLB uses the same binary glTF container as an object GLB, but the contents can be very different: it may be an environment mesh, depth mesh, or a provider-specific scene export. It does not automatically preserve the view-dependent appearance or navigational behavior of a Gaussian-splat world.
Scope the loop
A useful scope sounds like: walk through one room, find three parts, repair a device, and exit before the timer ends. That sentence identifies the environment, interactive props, player controller, game state, and feedback required. It also prevents a prototype from turning into an uncontrolled asset-generation exercise.
Choose a visual target and a performance target. Decide platform, camera, expected session length, input method, and whether the prototype must run on web, desktop, mobile, or XR. Generate temporary assets only after those constraints exist.
Assemble
Import one object first and fix units, orientation, pivot, textures, and collision. Then import the environment and decide whether it is background, visual geometry, or editable level structure. Gaussian splats need a compatible renderer; skyboxes remain background shells; generated meshes may require separate simplified collision.
Add a controller, spawn point, one interaction, a goal state, and a failure or reset path before polishing. Use primitive colliders and placeholder UI where they make iteration faster. The generated world supplies appearance, while the engine owns deterministic rules and player feedback.
Test the build
Run the complete loop with someone who did not build it. Watch where they get stuck, where collision fails, and whether generated detail obscures interactive objects. Record import time, cleanup time, frame rate, memory, file size, and the number of manual fixes needed per asset.
Replace only the assets that block the test. If a generated environment is expensive or difficult to navigate, keep it as a distant visual layer and rebuild the playable path with simple geometry. The prototype succeeds when it answers a design question quickly, not when every surface is final art.
It can create visual assets or an explorable scene, but the engine still needs controls, collision, state, objectives, interaction, UI, and performance work.
Start with the element that tests the core loop. Use generated props for object-centered mechanics and a generated world for spatial mood or navigation, but validate one complete import path before scaling.
Decision tables
Discussion
Add source-backed corrections, questions, or notes for this page.
Loading comments...