Expertise 04 / Rendering & Performance

Performance as a whole-product discipline

I connect profiling, runtime architecture, rendering, shaders, content construction, and technical-art workflows so performance improvements survive everyday production.

01 / Approach

Profile the system
Then change the right layer

Hardware-aware

Account for the different constraints of Apple mobile GPUs, Android devices, and PC hardware, including memory bandwidth, overdraw, batch cost, and CPU/GPU balance.

Architecture-aware

Restructure data and work when necessary so algorithms can batch, move to Jobs and Burst, or transfer appropriate work from CPU to GPU.

Production-aware

Adjust shaders, materials, lightmaps, UI assets, scene structure, and art workflows so the improvement is repeatable by the team rather than a one-off code trick.

02 / Evidence

Rendering systems
built under real constraints

Combat Master / Mobile Battle Royale

Keep the entire detailed map visible

  • Built a runtime, depth-aware, semi-automatic impostor system for aerial drops.
  • The entire map remained visible, rather than falling back to a bare terrain representation.
  • Visual differences were difficult to notice without close inspection.
  • The benefit increased as source rendering became more detailed and expensive.

Combat Master / Map rendering

Batching and mobile bandwidth

  • Reduced mobile GPU memory-bandwidth pressure through texture and rendering-layout decisions.
  • Used texture arrays with a single material per map as part of the batching strategy.
  • Kept standard maps near 52 rendering batches and the large Battle Royale map below 100.

D.A.W.Studio / Four projects

Layered rendering with one camera

  • Consolidated layered rendering into a single-camera URP pipeline.
  • Replaced auxiliary effect cameras with Render Features.
  • Kept complete game scenes within roughly 50–100 batches.
  • Applied the approach across two sniper games, a runner, and a roguelike shooter.

D.A.W.Studio / Art pipeline

Quality without unnecessary runtime cost

  • Optimized island water while preserving its visual quality.
  • Improved lightmap quality without increasing resolution, removing visible stepping.
  • Adjusted UI art production to obtain hardware-assisted antialiasing at negligible runtime cost.
  • Worked with technical artists and modelers so content was built for the target performance envelope.

Tellurion / RealmCraft

Voxel lighting, culling, fog, and VR

  • Moved voxel-lighting work from CPU to GPU.
  • Optimized shaders and distance-based fog to improve frame rate and battery behavior.
  • Contributed to delta-based lighting updates and light/chunk culling, reducing unnecessary recalculation and invisible work.
  • Optimized rendering for internal Gear VR and HTC Vive builds.

Wargaming / REVOLT

Low-end headroom and a distinct style

  • Optimized rendering so the game ran reliably on iPad 2 with substantial performance headroom.
  • Developed a custom shader with a triple-shadow treatment for the hand-drawn visual style.
  • Established a technical-art workflow and mentored the technical artist in rendering and production practices.

West-Games / Seaker

Approximately seven batches

Designed a unified shader and material approach that reduced the complete casual game's rendering to roughly seven batches.

The result came from organizing the rendering system and content around the constraint, not from optimizing isolated draw calls after production.

Cubic Games / Pixel Gun 2

CPU and memory optimization

  • Improved algorithms in gameplay and voxel hot paths.
  • Moved suitable workloads to Unity Jobs and Burst.
  • Restructured logic toward DOD to expose further optimization opportunities on low-end mobile devices.
  • Optimized hanging-voxel logic and destruction-driven NavMesh rebuilding.

03 / Areas

The layers I work across

GPU and shaders

Manual shader optimization, stylized rendering, CPU-to-GPU transfer, texture access, bandwidth, water, fog, lighting, and platform-specific trade-offs.

Scene and content

Material architecture, texture arrays, batching, impostors, culling, lightmaps, UI asset production, and collaboration with modelers and technical artists.

Runtime and data

Profiling, algorithms, memory behavior, DOD, Unity Jobs, Burst, ECS-oriented structure, voxel processing, pathfinding, and update frequency.

04 / Outcomes

Concrete performance markers

~7

Rendering batches for the complete casual game Seaker.

~52

Rendering batches for standard Combat Master maps.

<100

Rendering batches for the large Battle Royale map.

iPad 2

REVOLT ran reliably with substantial performance headroom.

05 / Relevant stack

Rendering and optimization tools