3D Environment Art for Games

3D environment art is the production of the spaces a game takes place in — architecture, terrain, interiors, exteriors and the assets that fill them. It covers both making the pieces and, on many projects, assembling and dressing them into a finished, performant level.

Environment work usually splits into:

- Asset production — architecture, terrain, props, foliage, modular kit pieces
- Kit and material foundation — trim sheets, tileable materials, shared masters
- Level art — placement, composition and set dressing of the space itself
- Optimization — LODs, collision, draw calls and streaming structure

Both, and they are priced and scoped differently. Asset production delivers the pieces to your spec. Level art delivers the space: kit placement, composition, set dressing and a scene handed over ready for lighting. Which one you need is the first question we ask.

The two scopes:

- Assets only — you have level designers and artists; you need production capacity
- Assets plus assembly — you have design and a blockmesh; you need the space finished
- Assembly only — you have a kit and a library; you need it built with

On Starship Troopers: Extermination we produced environment assets and assisted in developing the game locations.

Unreal Engine and Unity. On UE5 we account for Nanite, Lumen, World Partition and virtual textures — but selectively. Each of those helps some projects and adds cost to others, and part of the job is telling you which ones your project actually benefits from.

What we handle per engine:

- UE5 — Nanite-appropriate geometry, Lumen-correct materials, World Partition streaming structure
- Legacy UE pipelines — baked lighting, lightmap UVs, traditional LOD chains
- Unity — prefabs, materials, LOD groups and scene structure to your project setup
- Either — collision, pivots, naming and streaming conventions matched to yours

Yes. Realistic environments are built from reference with PBR materials and architectural logic that holds up under inspection. Stylized environments follow a defined shape language with readability carried by silhouette and colour blocking. Most projects need us to match an existing world rather than define one.

The practical difference:

- Realistic — reference-driven, PBR, coherence carried by scale and material accuracy
- Stylized — simplified forms, deliberate colour blocking, readability at distance
- Either way — your existing levels are the style guide

Yes — it is the most common assignment. Send levels already in your build and we reverse-engineer the rules: scale relationships, material palette, texel density, kit grid, wear language. New spaces then belong to the same world instead of sitting next to it.

What we ask for:

- Two or three existing levels or kits, ideally source files
- Your art bible and technical spec
- Screenshots or footage in your actual in-game lighting
- The modular grid, naming and pivot conventions your project uses

A modular kit is a set of grid-aligned pieces designed to combine into spaces; a trim sheet is one texture shared across many surfaces. On environments they are usually not optional — they are what makes building a large world affordable, and they cut texture memory sharply.

Worth the setup when:

- The world is large, or more locations are planned after launch
- Level designers need to build without an artist in the loop
- Texture memory is constrained, especially on mobile
- Several artists will work on the same space in parallel

Less useful for a single small bespoke location.

FBX and OBJ as standard exchange formats, with source files on request. PBR texture sets plus shared trim sheets and tileable materials, full LOD chains sized to placement distance, collision, and lightmap UVs where the project uses baked lighting.

Standard delivery package:

- Meshes in FBX plus source files
- PBR texture sets and shared material library
- LOD meshes across the agreed chain
- Collision meshes and grid-aligned pivots
- Lightmap UVs where baked lighting is in use
- Assembled scene, where level art is in scope

Environments are where per-asset budgets stop being enough. We work to scene-level targets agreed at the brief: draw calls, frame budget, texture memory and streaming cell size. Material sharing, LOD thresholds and kit design are all chosen against those numbers rather than adjusted afterwards.

Levers we use:

- Material and atlas sharing across the kit to cut draw calls
- LOD chains tuned to actual placement distance, not to a default
- Trim sheets and tileable materials to reduce texture memory
- Collision complexity matched to gameplay use
- Asset and kit structure organised for streaming or World Partition

Environment cost is driven by scope definition more than by asset count. «One level» can mean a kit hand-off or a finished, dressed, optimized space — an order of magnitude apart. We quote per project once the scope and technical targets are clear.

What moves the number most:

- Assets only versus assets plus assembly and set dressing
- Whether we start at concept, at blockmesh or from an existing kit
- Whether a modular kit and material library already exist
- Realistic PBR versus stylized hand-painted
- Target platform, engine version and scene performance targets

Yes. We start by reading what exists — kit, material library, conventions and blockmesh — and tell you honestly whether continuing or rebuilding the foundation costs less. Then we deliver one section or location for calibration before scaling up.

How the handover works:

- We review the existing kit, spec and art bible
- You get a straight answer on continue versus rebuild
- One location or section is delivered and reviewed first
- Your grid, naming and folder structure are adopted, not replaced
- Throughput ramps only after that first section is approved