Portfolio | Chris Leu

👨‍💻

Game Programmer

Tool & Gameplay Systems

Serialization Save/Load

Voxel Manipulation

VR/XR Systems

Performance Optimization

GPGPU/Compute

🎨

Technical Artist

Asset Pipeline

ShaderLab

Niagara

Asset Performance

Shader Debugging

UI Panels

🖥️

Graphics Engineer

Raymarching

Render Pipelines

Post Effects

Outlines

HLSL Shaders

Supporting Scripts

Game Programming

C#, C++, Python, HLSL

Prototyping, Profiling, and Optimization

Texture Painting

Texture painting system, written in C# for Masterpiece Studio. Fully-featured painting suite with triplanar projection, blending modes, decal splatting, HSV manipulation and more.
After the development was finalized for desktop hardware, we shifted targets to mobile VR headsets, which demanded extensive optimization.
Within a few weeks, I had increased the framerate past management's expectations of averaging 30fps, and secured a steady 72fps on hardware, while also decreasing the memory requirements by almost 30%.

Isolated Intelligence

Various tasks on the Isolated Intelligence title, including performance optimization, authoring the entire rappelling system which defined gameplay, authoring AI state machines & pathfinding logic, player taunt system implementation, and dozens more small systems and tasks as part of game development.

RLE Voxel Compression

Lossless Compression of Voxel data is a complicated, difficult problem which has been thoroughly investigated by giants like Microsoft for Minecraft, and Square Enix for Dragon Quest Builders 2, and Roblox for Roblox.

For my implementation had the moderate complication that my voxel data only ever existed GPU-side, so I was able to capitalize on parallelism, but complications with GPGPU are often difficult to debug, so drawbacks were present as well.

In the end, the data pulled to cpu was >90% compressed in all but the most adversarial examples, as Run-line Encoding was very well-suited to our contagious data with very small areas of fluctuation.

Technical Artistry

ShaderLab, Blender, Niagara

3D Modelling, Visual Effects, and Asset Optimization

Steampunk Flintlock

I created this model entirely from scratch to demonstrate simple hard-surface modeling techniques, and as a gift to my close friend and collaborator, whom drafted the concept art and provided feedback on the art direction as needed.

High-resolution render version and real-time gameplay-ready versions available for download soon.

Technical Art with BMAD

At BMAD I currently work under an NDA, handling performance optimization, asset integration pipelines, shader development, graphical R&D, and more as the acting Lead Technical Artist.

Isolated Intelligence

With Soul Lantern I handled dozens of Technical Art tasks, such as handling asset import pipelines, handling all aspects of shader development, all VFX implementation, post-effects, and handling optimization of assets & systems that needed to be revised.

Having to handle all of the tasks that come together to make a tech artist, in addition to gameplay programming, gave me a much better understanding of both disciplines, which I now weaponize to maximize framerates and visual fidelity.

Graphics Engineering

HLSL, OpenGL and DirectX

Render effects, GPU trickery, and more!

Simple Raymarching

I drafted this example raymarching system in C# over the course of a weekend, referencing various online tutorials and example implementations. Future revisions could implement more advanced scenes, volumetrics, animated surfaces, or shadows.

It was a quick & dirty prototype with scene structuring, SDF sampling, and reflections. As an early exploration into how volumes and shapes can be defined mathematically, instead of by vertices, its far from optimized, but showcases the strengths of this structure.

Simple Realtime Outlines

This simple outline effect uses a brute-force method, since all of the assets in the title which used it were manifold, which is to say: they had no holes or discontinuities that would cause this naive effect to break.
More modern, optimized techniques are increasingly common, and I would love to revisit this subject to implement an optimized compute shader using the Jump-Flood algorithm.

Reference Shader Parameters in Build

In Unity, shader parameter information detailing the value and datatype of inputs are readily available in the editor, and very useful in build, when handling models imported from third-party libraries like Sketchfab or the Autodesk API.

This would be trivial if the shader was available in build, but it's not available in build. However, we can cache those values at build-time, making them available at runtime.

I authored two scripts to handle this issue, one to be present in build-time and capture the shaders in editor, and a serialized scriptable object to provide those parameters in build.