Sarah Clarity Studios

Chapter 3: Lighting Renders for Paintover

Created by Sarah Choi (prompt writer using ChatGPT)

Lighting Renders for Paintover

Unit 25 — 2D / 3D Hybrid Methods for Vehicles

Lighting renders for paintover are the bridge between blockout truth and final illustration. A good render is not a beauty shot; it is a neutral, information‑rich plate that preserves stance, surface intent, and contact logic so a 2D pass can move fast without inventing physics. This article lays out how concept‑side and production‑side vehicle artists can craft lighting setups that are reliable, repeatable, and ethically sound when mixed with kitbashing and photobash.

1) What a paintover render must do (and must not do)

A paintover render must tell the viewer where the light comes from, how mass meets ground, and how the big forms crown and turn. It should be simple enough to repaint but specific enough to avoid guesswork on perspective and shadow. It must not hide proportion problems with theatrical rim lights, over‑fogged atmospherics, or glossy shaders that falsify material reads. Think of it as a measured sketch: deliberate, legible, and shy of spectacle.

2) Start with stance truth: scene scale, camera, and ground

Lock units and scene scale so one software unit equals one centimeter or meter across the project. Drop a ground plane of realistic size with a subtle micro‑roughness; this creates believable bounce and contact shadows. Establish camera presets that match gameplay lenses and review norms: a crouch‑height 24–35 mm for presence, a beauty 50–85 mm for portfolio, and an orthographic/plan for packaging. Save height, tilt, and focal length in the preset names so renders remain comparable across passes.

3) The speed‑cage carries the light

Run lighting tests on a speed‑cage blockout, not on polished surfaces. Hard planes and minimal bevels keep the light honest and expose proportion issues instantly. Assign four neutral materials—matte body, semi‑gloss glass proxy, dark rubber, satin metal—so value separation is readable in grayscale. If it sings as a clay under a single key, it will survive detail. If it doesn’t, fix stance before touching shaders.

4) A dependable baseline rig

Use a single directional key to represent sun or key stage lighting, paired with a broad fill (HDRI or area fill) and optional low‑intensity ground bounce. Set sun elevation and azimuth to match the context you expect most (e.g., 35° elevation for mid‑day patrols). Keep color temperatures near neutral early; reserve stylization for paint. Verify reads in both color and grayscale. A baseline that exposes the silhouette and the crown transitions will be more valuable than a moody setup that hides flaws.

5) Clay, AO, and shadow‑only: the holy trinity of plates

Export three core passes for every angle you intend to paint: a clay (lit diffuse without albedo), an ambient occlusion (separate pass, not multiplied into the clay), and a shadow‑only (matte/shadow catching just cast shadows and contact). These let you rebuild lighting logic in 2D and adjust levels non‑destructively. Keep AO radius within plausible bounds; giant AO makes vehicles look toy‑scale and lazily fakes creases you haven’t designed yet. If your renderer supports it, also export reflection‑only and specular‑only passes for highlight control.

6) Linear workflow and color management

Work in linear or ACEScg for rendering and convert to sRGB for delivery. Bake nothing into the clay: no color textures, no baked AO, no LUTs. Tone mapping should be conservative (Reinhard or Filmic with gentle shoulder). When in doubt, export 16‑bit PNG or EXR and do shaping in 2D. Consistent color management ensures that a black value in one project equals a black in another, which in turn stabilizes your paintover process across months of production.

7) HDRI ethics and usage

HDRI maps are excellent for believable reflections and global fill. Choose sources with clear licensing, keep a sources note, and avoid branded skylines if the reflection would create IP conflicts. Rotate the HDRI around a stationary vehicle rather than spinning the vehicle inside a fixed HDRI—this keeps camera continuity for reviews. Avoid high‑contrast HDRIs that create zebra striping on curves; your goal is information, not drama. When using photography plates under the vehicle, match exposure and color temperature to the render or the image will dictate false lighting cues that you’ll be forced to chase in paint.

8) Managing kitbash in renders

Kitbashed parts should inherit your four neutral materials during lighting tests. Busy kit geometry must be decimated or boxified so it reads as planes under light; otherwise it will spawn micro‑highlights that disguise proportion problems. Reserve production‑grade kit shaders for reference renders later. If a kit part’s reflections dominate the composition, its material is too hot for a paintover plate—pull it back.

9) Shadow craft: the language of weight

Contact shadows communicate mass. Use a shadow catcher on the ground and ensure your sun penumbra matches plausible softness for the scale (large penumbra for far sun, crisper for spots or stage lights). Check that wheels and skids actually touch; a 5‑mm float will poison every paintover. For aircraft or hovercraft, include faint projected shadows and soft bounce under the fuselage; this prevents the “sticker on a background” look when compositing onto photos.

10) Highlight discipline and crown management

Highlights describe curvature and panel logic. For paintovers, avoid anisotropic or flake shaders until surfacing is locked; prefer broad, calm highlights that signal form without noise. Sweep a rim pass only to separate foreground from background; keep it subtle. When a highlight fights the silhouette or chops across a hero line, change the surface or light, not the exposure. Crown management—where a form transitions from lit to unlit—should be legible at game camera distance; if it isn’t, the form is under‑designed.

11) Atmospheric control

Use atmosphere sparingly: a touch of volumetric haze can separate layers, but it also flattens contrast and fakes scale. If your project uses heavy fog or dust, create a separate atmosphere pass so paint can dial it. Never hide unresolved geometry under god rays; that’s debt disguised as mood. For aerial or orbital vehicles, add a faint ground‑reflected fill from below to simulate sky/earth bounce; it stabilizes the read without washing out silhouettes.

12) Output discipline: what to export every time

From each camera, export: clay, AO, shadow‑only, reflection‑only (optional), specular‑only (optional), object/material ID masks, normal (world or view), Z‑depth/position for depth‑of‑field and aerial perspective, and a silhouette mask. Keep naming consistent and embed camera/lens info in the filename. Provide a small layout JPG that thumbnails the passes and notes exposure so a teammate can paint without ever opening the 3D file.

13) Photobash ethics for lighting plates

When you place a photograph beneath or behind a render, document the source and license. Transform materially—perspective correction, lighting match, color temperature—before paint. Avoid using photo reflections on vehicle bodywork unless you own or can clear the image. If a plate introduces a light direction that contradicts your key, re‑light the render or choose a different plate; do not force the 2D artist to argue with physics. A finished concept that relies on uncredited backgrounds or distinctive manufacturer details is both unethical and risky for production.

14) Review ritual: grayscale first, then color

Conduct reviews in grayscale for the first pass to force attention onto stance, silhouette, and crown transitions. Then flip to color to check temperature balance and material cues. If a plate needs a LUT to look good, the lighting is performing theatrics instead of delivering information. Treat “looks cool” as a red flag during paintover prep; cool can come later.

15) Common failure modes and their fixes

Over‑contrasted HDRIs create zebra bands—swap to a softer map or reduce intensity. AO cranked too high makes everything look like a 1/24 scale model—halve the radius and intensity. Specular overdrive makes matte armor read as plastic—lower spec intensity or roughen the shader. Excessive rim hides silhouette problems—turn it off and fix stance. Shadows too soft for scale—tighten sun angle. Photobash plate fights render lighting—color‑match or pick a different plate.

16) Mini case study: urban interceptor paintover plate

The brief calls for a compact urban interceptor. A speed‑cage is lit with a 35° sun and a neutral HDRI; ground plane has mild roughness. From crouch‑height at 28 mm, the silhouette feels top‑heavy, so the track widens by 60 mm and the cabin drops 40 mm before any shader tweaks. Clay, AO, shadow‑only, and ID masks are exported at 4K. In 2D, the artist dials AO to 35%, paints a crisp beltline highlight to reinforce the shoulder, and adds a faint blue fill to lift the underside. A gridded rooftop photo is placed as background with documented license and temperature matched; the render’s shadow‑only plate grounds the tires on the roof gravel. Final paint introduces livery and light scratches while preserving the render’s shadow logic. The modeling team later swaps the cage for a minimal quad surface, and the lighting rig remains unchanged—proof the plate was honest.

17) Production‑side notes: keeping rigs reusable

Package the light rig as a locked file with named lights, camera presets, and exposure notes. Include a “calibration scene” with a gray ball, chrome ball, and color checker so renders can be matched month to month. Document renderer version, tonemapper, and exposure settings; small changes here can break consistency across teams. Provide a quick start paragraph: where to place the vehicle, which render layers to enable, and how to export the standard pass set. This turns your personal lighting habits into a studio tool.

18) Closing thoughts

Lighting renders for paintover are instruments, not performances. When they are linear, neutral, and repeatable, they accelerate every downstream step—2D paint, modeling, rigging, and lookdev—because everyone is reading from the same physical script. Tie them to speed‑cage blockouts, keep kitbash materials honest, treat photos ethically, and your vehicles will carry the same stance and light from first sketch to shipped asset.