# 3D & Gaming Focus 2D generative models are very helpful for a diversity of use cases from level design to marketing video generation, but one thing that sets Atlas apart is a focus on 3D and gaming specific AI tools. The platform integrates a diverse range of AI technologies all driven by gaming workflows, but the core focus (and where most of our proprietary technology sits) is in helping 3D generations move from simple prototypes to game ready assets. This includes technologies and workflows that: * Split objects into separate parts (pre and post generation) for higher 3D quality and bespoke editability * Retopology controls that deliver optimization specific to different engines and control for manual editing * Multi-view texturing and UV unwrapping capabilities to uprez, edit or even replace textures * Full PBR material generation (including 8K+ textures) * Automatic pivot, scale, and alignment fixes based on an understanding of real-world constraints and artist inputs * Parallel and batch processing for multiple generations at once * Engine-specific presets and automatic geometry / texture checks * Integration of AI workflows directly into game dev pipelines (via API) ## Why a 3D-and-gaming focus matters Generic AI 3D tools optimize for "make a 3D model from text or an image." That works for individual creators making one-off assets. It fails at the production scale studios need, because shipping a real game asset is not a single-step generation problem. It's a chain of decisions about topology, UVs, materials, scale, pivot, LODs, engine targets, and integration that an asset has to survive before it lands in a level. Atlas treats every one of those steps as a first-class capability. The result is a platform that produces assets which actually ship into Unreal Engine or Unity, not just demos that look good in a presentation. ## Use cases by studio function * **Technical artists** use Atlas to build reusable asset pipelines: image-to-3D with the right backend, automatic retopology to a target polycount, baked normal maps, engine-specific export presets. Once built, the same workflow runs on every new asset. * **Art directors** use Atlas to maintain style consistency across asset libraries: a shared reference image plus style-conditioning means every new asset matches the established direction. * **Engine programmers** use the exported API to trigger generation from inside Unreal Engine or Unity, often via the [official plugins](/atlas-ai-studio-overview/node-index/api-nodes.md). Players or designers request assets; the engine receives game-ready GLB output. * **Production leads** use parallel and batch processing to compress timelines. A workflow that handles a single asset in 30 seconds can run 100 in parallel for asset library expansion. * **Studio CTOs and innovation teams** use Atlas to evaluate AI integration with concrete production metrics, not generic claims. The integration-first architecture means Atlas slots into existing pipelines rather than replacing them. ## Production patterns worth knowing * **Generate → optimize → bake → texture.** The canonical chain for hero assets. Generate at high detail, retopologize to a low-poly target, bake high-detail features as normal and PBR maps onto the low-poly mesh. See [3D Generation Best Practices](/atlas-ai-studio-overview/node-index/mesh-nodes/3d-generation-best-practices.md) for the deep dive. * **Multi-view conditioning for character work.** Single-image generation hallucinates backs and occluded surfaces. For characters, use Multi-View → 3D from [Mesh Nodes](/atlas-ai-studio-overview/node-index/mesh-nodes.md) with front, side, and back references. * **Style-locked batch generation.** Use a canonical reference image extracted via Describe Image (in [Utility Nodes](/atlas-ai-studio-overview/node-index/utility-nodes.md)) to lock style, then batch-generate variants of a hero asset that share visual direction. * **Engine-aware export.** Atlas's automatic geometry and texture checks catch issues before they reach the engine. Combined with the engine-specific presets, this is the difference between assets that import cleanly and assets that need manual fixes. ## Related pages * [Node Index](/atlas-ai-studio-overview/node-index.md) — complete reference for every node, organized by category * [Atlas AI Agent](/atlas-ai-studio-overview/atlas-ai-studio-overview.md) — how the multi-agent system helps build production workflows * [Atlas x GCP](/atlas-ai-studio-overview/atlas-x-gcp.md) — the Google Cloud Marketplace deployment story * [3D Generation Best Practices](/atlas-ai-studio-overview/node-index/mesh-nodes/3d-generation-best-practices.md) — the depth-first guide to 3D generation * [API Nodes](/atlas-ai-studio-overview/node-index/api-nodes.md) — exporting workflows as callable APIs for engine integration ## Frequently asked questions **How is Atlas different from Meshy, Tripo, or other AI 3D generators?** Atlas is an orchestration layer that runs many models, including Meshy, Tripo, Hunyuan, Trellis, and others, as backends. The platform's value is in the production-grade workflow built around the model layer: retopology, UV unwrapping, PBR generation, engine export, integration plugins. Single-model generators produce raw output; Atlas produces shippable assets. **Which game engines does Atlas target?** Unreal Engine 5.5+, Unity 2023.1+, and Blender via official plugins. Custom engines and other tools integrate via API. The platform is engine-agnostic by design; the export format (GLB) and the API surface work with anything HTTP-capable. **Does Atlas support PBR materials at production resolution?** Yes. The platform supports full PBR material generation including 8K+ texture resolutions. Texture size and resolution are exposed as workflow parameters, so studios can dial in the right level of detail for the target engine and platform. **How does retopology work in Atlas?** Retopology is a built-in capability via the [Mesh Nodes](/atlas-ai-studio-overview/node-index/mesh-nodes.md). Options include target polycount, target topology (triangles or quads), and engine-specific presets that respect the polycount and UV layout conventions of each target engine. **Can Atlas produce game-ready characters with rigs and animations?** Yes. The full pipeline is: Multi-View → 3D for the character mesh, Rig Humanoid Mesh for skeleton, Retarget Rigged Mesh and Animate Rigged Model for motion. The Character Workflow node chains all of these into a single automated step. See [Animation Nodes](/atlas-ai-studio-overview/node-index/mesh-nodes/animation-nodes.md) for the full guide. **What's the typical asset turnaround time?** Depends on the workflow. Concept-to-game-ready for a single asset typically takes 1 to 5 minutes end-to-end, compared to days or weeks for traditional pipelines. Hero assets that require extensive baking and refinement take longer. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.atlas.design/atlas-ai-studio-overview/3d-and-gaming-focus.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.