# Track Resources — Technical Art --- ## What the role is Technical artists are **hybrid creative and technical operators who liaise between the artist and the programmer teams.** In practice: you build the tools, shaders, and procedural systems that let artists work faster, and you are the person who figures out why the frame rate dropped. Epic's own description of the responsibilities: ensuring performance, consistency, and workflow optimization; prototyping new graphics and content creation methods; reducing scene complexity and analyzing profiling data; developing content guidelines; and negotiating compromises between artistic and technical demands. It is one of the most reliably employable disciplines in this field, and it is under-supplied because it requires genuine competence on both sides. **Salary reference:** junior ≈ $58,000, senior ≈ $117,000 (CGSpectrum). Unreal-specialized technical artist postings have listed substantially higher. --- ## What the job asks for **Foundations** - **Solid understanding of trigonometry and vector math** — Epic names this explicitly - Comprehensive understanding of the hardware-to-software rendering pipeline - Real artistic competence: proportion, color, composition. You are not a programmer who works near art. **Scripting and languages** Python (pipeline, DCC tooling) · C++ (Unreal, engine work) · HLSL/GLSL (shaders) · C# (Unity) · Blueprint · MEL, MaxScript, Lua in specific contexts **Specialization areas** - **Shading and materials** — authoring shaders, material systems, lookdev support - **VFX** — Niagara, particle systems, simulation - **Procedural content** — Houdini digital assets, PCG frameworks - **Pipeline and tools** — DCC integration, automation, asset validation - **Optimization and profiling** — the least glamorous and most consistently valued - **Lighting and rendering** — Lumen, path tracing, light budgets **Software** Maya, 3ds Max, Houdini, Substance Designer, Unreal Engine, Unity, Substance Painter, Nuke or After Effects for post. --- ## The Unreal-specific technical bar Current hiring guidance for UE5 roles asks for demonstrated evidence of: - **World Partition** — how it changed your level workflow, plus HLOD layers, always-loaded actors, and data layer management - **Nanite** — including its constraints with skeletal meshes, translucent materials, and deferred effects - **Lumen** — real-time GI tradeoffs, particularly console performance - **Gameplay Ability System** — production-level implementation, not theory - **Blueprint/C++ boundary** — the screening question that separates depth from familiarity is whether you can expose a C++ class to Blueprints so a designer can set properties without touching code Knowing the *constraints* of these systems, not just that they exist, is what a portfolio needs to show. --- ## Portfolio standard Tech art portfolios are judged on **evidence of solving a real problem**, not on beauty renders. Epic's framing: successful candidates have "something tangible and 'techy' to show." **For each piece, show** 1. **The problem** — stated in one sentence. What was slow, broken, or impossible? 2. **The solution** — the shader graph, node network, code, or tool UI, visible and legible 3. **The result** — before and after, with numbers where numbers exist 4. **Profiling data** — frame time before and after, draw calls, memory. Numbers are the discipline's native language and almost no student portfolio has them. 5. **A debug or breakdown view** — the effect deconstructed into its passes **Include** - A shader you wrote, with the graph shown and the math explained - A tool with a working UI that another person could use, on GitHub with a README - A procedural system (Houdini HDA or Unreal PCG) with the parameters demonstrated live - An optimization case study with real profiler screenshots - A Niagara or VFX system with the emitters broken out **Post your code.** GitHub presence is a meaningful signal for this discipline in a way it is not for pure art roles. --- ## Learning resources **Shaders and rendering** - **The Book of Shaders** (thebookofshaders.com) — free, the standard introduction to fragment shaders - **Shadertoy** (shadertoy.com) — read other people's code; write your own - **Catlike Coding** (catlikecoding.com) — free Unity shader and rendering tutorials of exceptional depth - **Alan Zucconi's shader tutorials** — free, well explained - **Ben Cloward** (YouTube) — free shader instruction for Unreal and Unity, professional grade - **Real-Time Rendering** (Akenine-Möller et al.) — the reference text; realtimerendering.com has a free resource list - **Íñigo Quílez** (iquilezles.org) — signed distance fields, procedural techniques, math articles **Houdini** - **SideFX Learn** (sidefx.com/learn) — free official tutorials; **Houdini Apprentice is free** for non-commercial use - **Entagma** (entagma.com) — procedural and mathematical Houdini, free and outstanding - **Rohan Dalvi** — free and paid Houdini tutorials, beginner-friendly - **Houdini Engine for Unreal** — HDA integration, a strong job skill - **CGWiki / Tokeru** (tokeru.com/cgwiki) — Matt Estela's Houdini wiki, the community reference **Unreal** - **Epic Developer Community** (dev.epicgames.com/community) — free official learning paths for materials, Niagara, PCG, optimization - **Unreal Engine documentation** — the profiling and optimization sections specifically - **Niagara documentation** and Epic's VFX learning paths - **PCG framework** documentation — procedural content generation in-engine **Python and tooling** - **Chad Vernon's Python for Maya** — free and complete - **Tech-Artists.org** — forums and Slack; the discipline's central community - **Qt for Python (PySide)** documentation — you will build tool UIs - **Autodesk Maya API documentation** **Substance** - **Adobe Substance 3D** learning content — free official tutorials - **Substance Designer** node reference; procedural material authoring **OpenUSD** - **OpenUSD.org** — official documentation and tutorials - **Alliance for OpenUSD** (aousd.org) — the Core Specification 1.0 and roadmap - **NVIDIA OpenUSD learning resources** — free courses - **Autodesk OpenUSD** solutions documentation **Math** - **3Blue1Brown, Essence of Linear Algebra** (YouTube) — free, the clearest available introduction - **Freya Holmér's math for game developers** (YouTube) — free, directly applicable - **Immersive Math** (immersivemath.com) — free interactive linear algebra --- ## Project ideas that map to hiring **Project 1 — Deconstruction** Recreate faithfully, or in your own style. See the Project 1 page for this track's curated source list: Pick a specific shader, VFX, or procedural system from a shipped game and rebuild it from observation. Document your hypothesis about the implementation, then test it. The write-up of where you were wrong is the valuable part. **Project 2 — Technique Tutorial** Candidate techniques to encounter in Project 1 and then teach. Pick one you genuinely did not have going in: HLSL shader authoring from scratch · Houdini HDA authoring with Houdini Engine integration · Niagara systems · Substance Designer procedural materials · a Python pipeline tool with a Qt UI · profiling and optimizing an existing scene with documented numbers · OpenUSD scene assembly · Gaussian splatting capture and integration. **Project 3 — Original Work** Built to fill the gap you named in your Week 3 portfolio review, or to demonstrate a requirement from a real posting your portfolio does not yet show: A tool, system, or shader that solves a real problem, delivered as a usable artifact: documented, published, with a README, and demonstrated with profiling evidence. If it is something another student in this program could actually use, that is a strong sign you chose well. --- ## Communities - **Tech-Artists.org** — forums and Slack. The single most valuable community for this track. - **Real Time VFX** (realtimevfx.com) — the VFX and tech art community - **Houdini / SideFX forums and Discord** - **Unreal Slackers** Discord — large, active, tech art channels - **Graphics Programming Discord** - **SIGGRAPH** — papers, courses, and the student volunteer program. The talks are directly applicable and many are free online. - **GDC Vault** — many talks free; the tech art and rendering tracks are excellent --- ## The advantage of this track Technical art rewards the exact loop this course is built on: encountering something unfamiliar, working out how it functions, and explaining it clearly enough that someone else can use it. A published Project 2 tutorial in this track is essentially a job application. Career paths into tech art typically run through texture artist, rigger, animator, or environment artist roles with coding added. If you are coming from an art background, the scripting is the gap. Close it this semester.