"I spent a year on geometry before I understood that the mesh was fine — I just had no idea how to light it."
Ondřej Vašíček
Environment artist, indie studio
You already know how to model.
At some point in most artists' work, the geometry is correct but the scene still looks flat. Not because something is wrong — but because lighting and surface response are skills you build separately, and most learning paths don't address them directly until much later.
The gap between a technically finished scene and one that reads as believable is almost always in how light interacts with surfaces — specular response, roughness, indirect bounce, and the way shadow edges communicate depth. These are learnable, but they take deliberate practice with feedback.
PBR texture workflows
Metalness, roughness, and normal maps — built around how real-time engines read surface data.
Real-time lighting
Dynamic vs. baked light, shadow resolution trade-offs, and performance-aware scene setups.
Material layering
Blending, masking, and procedural detail across surface types — rock, metal, fabric, wet ground.
Atmosphere and mood
Color temperature, fog density, and subtle ambient occlusion — the decisions that change a scene's feel.
what sets the approach apart
Built around how artists actually learn technical craft
Scene-first exercises
Every concept is demonstrated inside an actual game scene — not a blank sphere in a vacuum. You adjust light rigs, see the render update, and break down why it changed. Theory follows observation, not the other way.
Structured feedback cycles
Submissions are reviewed with annotated viewport screenshots — not written comments only. You see exactly where the surface read breaks down and what to change. Reviews happen within 48 hours of submission.
Adaptive path selection
Group sessions and individual lessons share the same material but different pacing. You choose based on how you work best — not based on budget alone. Both tracks finish at the same depth.
When you hit a wall, there is a way through it
Lighting problems in 3D tend to compound — one wrong decision creates three confusing symptoms downstream. Most artists either guess their way out or restart. Neither is efficient.
Each program module includes a diagnostic checkpoint. If your scene isn't reading correctly, you work through a structured checklist with your instructor — starting from light intensity, then surface values, then indirect contribution. The process itself teaches you how to think about the problem.
The typical student spends weeks 1–3 building foundational surface literacy, then moves into weeks 4–6 where lighting decisions become contextual rather than procedural. By week 8, most participants are producing scenes that hold up under critique — not perfect, but coherent.
Progress varies — this reflects a common pattern, not a fixed guarantee.
The people you are learning alongside matter
Participants come from game studios, indie teams, freelance contracts, and architecture visualisation — all working with 3D lighting in different contexts. That variety shows up in critique sessions.
Async critique board
Post a scene at any hour. Other participants and instructors leave annotated feedback before the next session.
Small cohort size
Group sessions cap at 12 participants. Enough to get varied perspectives, small enough for real instructor attention.
Cross-discipline input
When a lighting decision reads differently to a technical artist than to a concept artist, you hear both — and learn to evaluate them.
Studio workflow context
Exercises use production-realistic file structures and naming conventions, not simplified sandbox setups.
■ game studios
■ indie / freelance
■ archviz / other
The current cohort mix leans toward independent artists and small studio teams — people working without a senior lighting artist one desk over. That shared context tends to make critique sessions more direct and practical than programs oriented toward students with no production experience yet.
The part most people hesitate about
Do I need professional software already installed to start?
You can start with trial versions of standard tools. During the first two weeks the program covers setup and configuration, so you are not expected to have everything ready beforehand. If you are already working in Blender, Unreal, or Unity — all three are used in exercises.
Is there a difference between group and individual sessions?
Group sessions work through structured exercises with instructor feedback in a shared environment. Individual sessions adapt the pace and topic order to where you are right now — same material, different rhythm. Neither is a shortcut; both take roughly the same total hours.
What if I fall behind during the program?
Session recordings stay accessible, and each module has a short catch-up task rather than requiring a full redo. Instructors check in weekly — not only at assignment deadlines. Falling behind a week is recoverable; dropping three weeks without contact is harder to resolve.
Where this
actually
takes you
Eight weeks in, you are not a different artist — you are the same artist with a clearer understanding of why a scene works or doesn't. That clarity changes how you approach every project afterward, including the ones that have nothing to do with games.
The gap between where you are now and where this ends isn't mystical. It's a set of skills with a known learning curve. Some parts come quickly; others take several attempts. That's what the program is designed for.
see how the program is structured