I design game systems, then build them.

What I did

• Speed-gated destructionVideo

  Walls only break if you hit them fast enough. I built it in C++ on Chaos Geometry Collections: two trigger volumes measure your speed on the way in, and the impact spawns a physics field with strain plus directional and radial velocity. We use it to hide secrets and to reward players who keep their speed up.

• Destructibles editor toolVideo

  A panel under the Window menu that lists every destructible in the level, shows its tuning, and fires a test projectile with an in-place reset. Designers can tune breakage without entering Play mode.

• Respawn systemVideo

  I built Everent's respawn system. The clip shows it running in the editor.

• Corrupt surfaces

  You can ride on any surface in Everent, so puzzles needed a hard limit. I wrote a C++ physical material that pushes the board away with world-space gravity, scales the push by approach angle, and turns off boost.

• Leading the design teamVideo

  I led 7 designers from concept through production. I wrote the GDD and the one-page specs for movement, puzzles, and progression, ran sprint planning in Jira, and tuned the DualSense adaptive triggers for each surface type.

• Sky creatures

  I prototyped a compute-shader flocking plugin for the koi, manta rays, and jellyfish that fill the sky. Niagara integration didn't work out, so I switched to instanced meshes driven by CPU readback.

• Lighting decisions

  I led the call on Lumen versus baked GI, the cost of Virtual Shadow Maps, and our HLOD plan, then wrote the team's graphics settings spec on UGameUserSettings with runtime scalability groups.

• Streaming-safe destruction

  World Partition streaming broke destructibles in a few ways. I fixed a delegate that was binding twice, resolved overlaps at BeginPlay, and guarded destroy calls against actors that had unloaded.

• Playtest analytics

  I built a local pipeline (FFmpeg, faster-whisper, DeepFace, Llama 3.1) that turns playtest recordings into transcripts, emotion timelines, and coded feedback in the spreadsheet format our studio already used.

UE5.7, C++, Blueprint, Chaos, World Partition, Perforce, Jira

How I build it: I own the architecture and direction, and AI writes much of the code. I set the goals and the tests, read the GPU timings, and make the final call in the headset. It's about 145k lines of Rust across 13 crates, with 600+ commits.

What I did

• Path-traced lightingVideo

  ReSTIR direct lighting, one-bounce diffuse GI, SVGF denoising, a physically based sky and volumetric atmosphere, and DLSS Ray Reconstruction. Curved primitives use analytic intersection shaders.

• Connected spacesVideo

  Portals join rooms with different curvature. Rays continue through a portal into the next space, so lighting and shadows stay consistent across the seam.

• Fixing VR frame timeVideo

  Streaming in distant terrain pushed VR frame time up. The run data pointed at the radiance cache, so I had the distance cascade extended and checked it pass by pass in Nsight. Cache resolve dropped from 2.8–5.8 ms to about 0.35 ms (median).

• A physical body in VRVideo

  In VR you have a physics-driven body that can grab, climb, and pick things up. I also built benchmark tooling that pins GPU clocks and logs power draw.

• A shader regression

  GPU timestamps showed a cylinder intersection shader taking far too long. I replaced its 64-step sphere tracer with an analytic quadratic solve.

• Running inside Godot

  The renderer sits behind a C ABI inside a Godot fork, so Godot handles the editor, scripting, and asset pipeline.

Rust, Vulkan ray tracing, HLSL, OpenXR, Godot, Nsight Graphics

What I did

• DoorwaysVideo

  Each doorway uses stencil masking to show a room larger than the outside of the building. A player state machine, per-object portal membership, and gravity overrides let the player and physics objects cross cleanly.

• Objects crossingVideo

  Physics objects move between rooms and switch to the new room's gravity as they cross.

• Rope through doorwaysVideo

  A Verlet rope and grapple that keeps working through doorways, with a renderer that draws the rope across the portal.

• Room builder

  A one-click procedural room builder with a custom inspector to build, rebuild, eject a room's contents, and preview its gravity.

• A hyperbolic room

  One room holds a raymarched hyperbolic Mandelbox with Möbius-transform camera movement. I also documented where stencil nesting fails: at depth 3 the render queue falls apart.

Unity URP, C#, stencil rendering, editor tooling