Summary of "Exploring the Art of “Indiana Jones and the Great Circle” with MachineGames"
Exploring the Art of Indiana Jones and the Great Circle (Machine Games)
Overview
A studio presentation (hosted by Kir Terv) where Machine Games artists explain technical workflows, pipeline decisions and practical techniques used to build Indiana Jones and the Great Circle. The session covers environment modularity, photogrammetry-driven sculpting, vehicle texturing workflows, weapon scanning/modeling, and engine/tooling constraints and trade-offs.
Studio & tech context
- Machine Games (Sweden) moved from idTech-based tooling to a newer in‑house engine (referred to as “Mon”/Motor).
- Engine features added for this project: ray tracing, a new terrain system, vegetation, open‑world capabilities and real‑time GI.
- The renderer can handle very high polygon counts; texture memory remained the main optimization constraint for large assets.
Presentations / technical highlights
1) Modular environment building — Vtoas / Pontus Katras
Goal: build large, richly detailed open-world scenes from small modular pieces.
Key ideas:
- Decompose architecture into repeating elements (trims, roof tiles, beams, add‑ons). Prioritize the most interesting/repeating pieces for trim sheets.
- Create small modular meshes (Modo or similar) and assemble them in the editor as prefabs. No large precomputed buildings — everything is built from many small modules.
- Use baked “add‑ons” and trim sheets for transitions; decals and vertex painting blend seams and damage variations.
- Work iteratively and early on architectural passes: start small (a corner or module), then scale up by combining modules.
Practical tips:
- Split textures and trims for baking convenience.
- Plan gradual transitions in both geometry and texture values.
- Ensure modular parts share compatible albedo/values so blending (vertex paint/decals) is easier.
Work iteratively: start with a single module, refine blending and trims, then scale up by composing modules into larger structures.
2) Photogrammetry + boolean-driven sculpting — George McClelay
Workflow summary:
- Create boolean “cutters” from scanned meshes or displacement/height maps.
- In ZBrush, use Live Boolean (folder-based workflow) to non‑destructively cut damage and edge detail into high‑poly modules.
- Important steps: mask/extract sections, close holes, flip normals for cutters, set cutters to subtract, use Dynamesh (Colorize off) to preserve polygroups, convert polygroups to vertex color/ID masks for export.
- Export baked ID masks (vertex color / polygroup-based) and use them to drive layered materials in Substance Painter and in-engine.
Benefits:
- Fast production of complex edge damage and silhouette detail.
- Automatic masks for material blending.
- Dramatically speeds high‑poly creation (large high‑poly modules reported in under a day).
Tools & tips:
- ZBrush Live Booleans, Dynamesh, polygroup → polypaint → ID masks.
- Follow-up resource: a referenced “hidden gem” tutorial video (older but influential, updated workflow referenced in the stream).
3) Vehicle texturing & material blending — Andre Malo
Constraints:
- High texel density targets mean large vehicles often require multiple large textures; texture memory management is critical.
Techniques:
- Combine trim sheets, tiled textures, decals and baked parts. Trim sheets are efficient for blocky elements; tile-based materials + texture‑mask blending are flexible for complex curved surfaces.
- Avoid baking unique normals for every tiled layer when possible: use beveled geometry and adjusted vertex normals (weighted normals or rebuild from faces) so shading looks good without baked normals.
- Texture mask / image‑mask blending workflow:
- Create RGBA (or grayscale) masks in Substance Painter (export RGBA channels as a mask).
- Engine shader blends up to four tile materials across the mesh driven by that RGBA mask; each layer can have independent tiling, normal/spec adjustments and blend softness.
- Decals, vertex painting, and small baked parts are used alongside mask blending for fine detail.
- World editor features: material remap capability so level artists can swap materials globally or per-instance.
Practical limits:
- Generally keep tiles ≤ 2K when possible; masks often 1–2×2K.
- Larger vehicles may still require multiple 4K textures.
4) Weapon scanning, boolean modeling & high‑poly workflow — Denil / Daniel
Scanning hardware/process:
- Handheld laser scanner: HandyScan Black.
- Use anti‑reflective spray on shiny parts and tracking dots.
- Scan precision: 0.1–0.2 mm depending on viewport/weight tradeoffs.
- Scan modes: grid (main) and line (for tight edges).
- Clean scans by deleting background/noise, close holes, stitch multiple scans via best‑fit/manual alignment.
Post‑scan pipeline:
- Produce proxy/rough meshes for scale and animation tests, then model final meshes in Maya with booleans separated into named layers (base / boolean / boolean_add) for easier ZBrush import.
- In ZBrush: run boolean operations, Dynamesh, polish with layered bevel/morph target technique to preserve multiple bevel sizes (gives control over edge shapes for first‑person fidelity).
- Export high poly (decimated if needed) and bake textures (spec‑gloss workflow).
Texturing & lighting check:
- Used Substance (PBR/spec‑gloss), studio sky and Marmoset (or other viewers) to inspect extreme lighting.
Typical weapon polygon targets (studio averages):
- Pistols ≈ 15k tris
- Rifles/SMGs ≈ 40–50k tris
- Improvised melee ≈ ~5k tris
Q&A / pipeline & production notes
- Preproduction involved significant R&D and pipeline development; many engine features were added during production and the pipeline evolved alongside.
- References & authenticity: a mix of scanning, on‑site photography, film stills and Lucasfilm archives when available; some props recreated from movie reference rather than scans.
- Optimization: Motor is comfortable with high polygon counts; main constraints were texture memory and real‑time GI/ray tracing performance on consoles. Artists optimized by mixing tiled materials, trims, decals and selective baking.
- Best practices: identify repeating elements early, plan trim sheets, iterate architecture early, and balance hand sculpting with procedural/live boolean techniques to provide visual variety while giving areas for the eye to rest.
Tutorials / guides mentioned
- ZBrush live boolean step‑by‑step demo (presented live by George): making cutters, flipping normals, live boolean folder workflow, Dynamesh with Colorize off, extracting polygroups → ID masks, baking to Painter.
- “Hidden gem” boolean tutorial (older video) that influenced their workflow — referenced but not reproduced in the transcript.
- Vehicle texturing guide: texture‑mask blending (RGBA masks) + trim/tile/decals workflow demonstrated by Andre (Substance Painter → engine material editor).
- Weapon scanning demo: HandyScan usage, scan cleanup, mesh stitching, Maya prep, ZBrush boolean & bevel/morph workflow, Substance/Marmoset checks (presented by Denil).
Practical numbers & tips (quick reference)
- Weapon triangle counts: pistols ~15k, rifles/SMGs ~40–50k, improvised melee ~5k (approx).
- Tile & mask sizes: tiles generally ≤ 2K; masks often 1–2×2K; large vehicles may need multiple 4K textures.
- Scanning precision: 0.1–0.2 mm (0.1 mm increases mesh detail but can reduce viewport fps).
- ZBrush tip: use Dynamesh with Colorize OFF to preserve polygroups / vertex color ID masks.
Main speakers / sources
- Host: Kir Terv (communications & industry relations, Nommon)
- Machine Games presenters:
- Vtoas / Pontus Katras — senior environment artist (modularity & world building)
- George McClelay — senior environment artist (photogrammetry + ZBrush boolean sculpting)
- Andre Malo — senior 3D artist (vehicle pipeline, texture masking & material blending)
- Denil / Daniel — weapon artist (scanning pipeline, modeling, boolean workflow and texturing)
- Studio: Machine Games (developers of Wolfenstein reboots and Indiana Jones and the Great Circle)
Tools & tech referenced
- ZBrush (Live Booleans, Dynamesh, polygroups)
- Substance Painter
- Marmoset
- Maya
- Blender (for reference/UVs)
- HandyScan (laser scanner)
- Modo (asset creation)
- Motor engine (in‑house, idTech heritage)
- Engine material editor, asset browser/prefab workflow
Available follow‑up materials (as presented)
- Short step‑by‑step ZBrush boolean checklist distilled from the demo.
- Quick template for creating RGBA blend masks in Substance Painter (export preset & engine usage).
- Compact modular‑environment checklist (trim sheets, prefabs, vertex paint/decals).
Category
Technology
Share this summary
Is the summary off?
If you think the summary is inaccurate, you can reprocess it with the latest model.
Preparing reprocess...