Creating 3D Models of Environment and Props
Environment is not background. In most games the player looks at it 90% of the time. Yet props and environment elements get cut the most: "it's just a box," "it's background," "nobody will notice." They notice. Especially when 40 background objects with unoptimized UV start eating draw calls on mobile.
Technical complexities that aren't obvious at first glance
Modularity and alignment. A level built from modular elements requires planning at modeling stage. If tiled floor sections aren't aligned to grid (grid snapping) with texture-size-multiple steps, seams appear at joints even with perfect tiling. For UE5 standard is 10/100/1000 unit grid. For Unity—depends on project scale settings.
Pivot points. Fundamental detail: if prop pivot isn't at expected point (object base, not geometric center), level designer can't place objects normally in editor. Every time manual position correction needed. Multiply by 200 objects and understand why level designers hate poorly prepared assets.
LOD chain. Standard prop in Unreal Engine should have minimum three LOD levels: LOD0 (full detail), LOD1 (~50% polycount), LOD2 (~25%). For mobile games—stricter. Automatic LOD generation through Unreal LOD Tool or Unity LOD Group works, but for key assets manual LOD is always better quality—algorithm doesn't know where silhouette matters and where it can be cut.
Lightmap UV. In Unreal Engine every static mesh needs separate UV channel for lightmap (channel 1). If done automatically through Generate Lightmap UVs in import—result is predictable: overlapping, uneven distribution, baked lighting artifacts. Manual lightmap UV—separate task often forgotten in specifications.
How prop/environment asset work is structured
Everything starts with context understanding: which engine, which platform, hero prop (foreground) or background filler, will it be static or interactive.
Concept review. If no concept—request references. Modeling without visual specs—most expensive way to get wrong result.
Blockout. Quick blocking of main forms in 3ds Max or Blender. At this stage we agree proportions, silhouette readability, modular joints if needed.
High-poly (for PBR pipeline). For assets that get textures through baking—create high-poly in ZBrush or 3ds Max with chamfer and surface detail work. For stylized games with hand-painted textures high-poly not needed—go straight to low-poly with refined geometry.
Retopology / Low-poly. Within agreed polycount. For modular elements—precise boundary vertex compliance for seamless connection.
UV + Bake. UV with correct texel density, lightmap channel if needed, full PBR set baking in Marmoset Toolbag.
LOD chain. LOD generation with manual critical level check.
Final export. FBX with correct axes (Y-up for Unity, Z-up for Blender, conversion if needed), correct smoothing groups, named material slots.
For large environment sets (dungeon kit, sci-fi corridor kit) work is structured sprite sheet approach: one large UV atlas for entire set to minimize draw calls during level assembly.
Timeline guidelines
| Asset Type | Timeline |
|---|---|
| Simple prop (box, barrel, tool) | 1–3 days |
| Medium prop (furniture, machinery) | 2–5 days |
| Hero prop (transport, unique object) | 5–14 days |
| Modular environment kit (10–20 elements) | 10–25 days |
| Full scene / location | per spec, from 3 weeks |
Cost is calculated individually. For asset sets—discuss package conditions.
What needs to be specified in requirements
- Engine and version (UE4/UE5/Unity 2022+/Godot/other)
- Platform (PC, console, mobile)
- Whether LOD chain is needed and how many levels
- Texture atlas size and PBR workflow (Metallic/Roughness or Specular/Glossiness)
- Whether lightmap UV channel needed
- Style (realism, PBR, stylized, hand-painted)
- Whether modular requirements exist (alignment with existing asset set)