Creating 3D Environment Models for Mobile Games
Environment in mobile 3D games isn't a collection of pretty objects. It's a system of modular meshes that level designers can assemble like building blocks, with batched materials, proper occlusion, and polygon budget allowing 60fps scene rendering on iPhone 13.
Modularity as Core Principle
Modular approach—creating basic blocks (floor, wall, corner, doorway, ceiling) assembled into any level. It's not just convenience—it directly impacts performance through Draw Call Batching.
In Unity: Static Batching combines static objects with identical material into one draw call. Condition: same Material (same instance). 50 walls from one prefab with one material = 1 draw call instead of 50. GameObjects → Static must be enabled. Increases RAM (combined meshes stored in memory), so be cautious with total static geometry size on mobile.
GPU Instancing—for repeating objects (trees, stones, vegetation) that can still move. One GPU call renders N copies with different transformation matrices. In Unity: Material.enableInstancing = true.
Snap grid: all modules created to common grid—1m, 0.5m, 0.25m. Snap vertices on module edges. In Blender—Snap to Vertex setting during modeling, Unit Scale = 1.0 (not 0.01, or scale won't match Unity's 1 unit = 1 meter).
Environment Optimization Techniques
Occluder and occludee. Large walls, buildings should be occluders—objects hiding what's behind them. In Unity Occlusion Culling—bake data through Window → Rendering → Occlusion Culling → Bake. Objects behind walls don't render at all. For mobile game with interiors (dungeon crawler, RPG) this is critical—without occlusion every room loads GPU, even if invisible.
Collision mesh. Collision shouldn't match visual mesh. For complex object (gnarled tree, ruins)—simple Box/Capsule Collider sufficient for gameplay, saves Physics CPU. In Unity: Mesh Collider with Convex = true for convex objects, Box/Capsule Collider for simple shapes.
Detail meshes vs terrain. Unity Terrain + Detail Meshes for grass and fine vegetation—built-in system with LOD and culling. For mobile: Detail Distance no more than 30–50 units, Detail Density limited (1.0 density grass creates thousands of objects). Billboard detail type (flat texture grass) faster than full 3D meshes.
Light Baking (Light Baking)
Real-time Global Illumination on mobile is too expensive. Standard—baked lighting via Unity Lightmapper (built-in or Progressive GPU Lightmapper). Lightmap Resolution 10–20 texels/unit for environment, 40+ for important objects. Lightmap Size maximum 2048 on mobile—multiple atlases for large scenes.
URP Baked Global Illumination: objects with Contribute Global Illumination participate in bake. Dynamic objects (characters) receive GI via Light Probes—placed in editor where characters move.
Ambient Occlusion for environment—baked into texture (Substance Painter or Blender bake), not real-time SSAO. SSAO on mobile is luxury not in performance budget.
From practice: mobile runner, Unity URP. City block scene: 300 draw calls, FPS 35 on Xiaomi Redmi 10. Issue: each modular block had own material instance (due to random color change in inspector on some objects). Materials weren't identical—static batching broke. After resetting all materials to original shared instance: 45 draw calls, stable 60 FPS.
Style and Detail Level
Hero props—key objects player sees close-up: chests, doors, altars. High detail, quality textures 1024×1024 or 2048×2048.
Secondary props—furniture, décor, regular environment elements. Medium detail, atlased textures (multiple objects on one atlas).
Filler / background props—distant background, extras. Minimal detail, LOD2 or billboard.
Trim sheets—one texture atlas with strips of different materials (brick, metal, wood), applied to modular meshes. Allows one atlas to cover entire location environment. Popular technique in AAA, applicable to mobile.
What's Included
- Modular geometry set for location (floor, walls, ceilings, transitions, décor)
- Hero props with complete texture set
- LOD0 + LOD1 for environment objects
- UV setup for light baking (Lightmap UV, second UV channel)
- Optimized collisions
- Export in FBX/glTF with correct pivot points
- Engine test: Draw Calls, batching, Occlusion Culling
Timeline
Modular kit for one location (20–40 unique modules)—4–8 weeks depending on style complexity and hero props quantity. Full environment for mid-size mobile game (3–5 locations)—2–4 months. Cost calculated individually.