Portfolio / Snuggles the Unicorn

Snuggles the Unicorn

Studio Left Turn Studios Role Technical Artist Dates 2022–2023 (canceled) Engine Unity
  • Unity Shader Graph
  • HLSL
  • Material Property Blocks
  • Rigging
  • C#
  • Editor Scripting
  • VFX
  • Animation Pipeline
Snuggles the Unicorn screenshot showing the game environment with character and enemy
FIG. 00: in-game environment with character and enemy Unity · URP

Snuggles the Unicorn was a Unity action game at Left Turn Studios, picked up from an externally developed prototype. My team inherited the project and built on it. The team was small: a concept artist, outsourced art from the Unity asset store, and me for tech art and implementation, with a second Technical Artist joining later for lighting and PCG level layout. The project was eventually shelved, but it produced significant work across rendering, shaders, rigging, animation, and tooling. The biggest piece was a full conversion to Unity's Universal Render Pipeline. Mobile was one of the target platforms from the start, so performance shaped the technical choices from day one: the render pipeline, the kinds of effects, and procedural or shader-driven solutions in place of heavy skeletal rigs.

Biped to Quadruped Mech

The player character is a unicorn: on foot in town, and riding a mech in battle. We inherited the project with an old store asset for that mech, and it was a biped. The design called for a quadruped instead, closer to a centaur, with four walking legs and a swiveling cockpit for the unicorn to sit in. Rather than get someone to model and animate a new mech, I built it from what we had:

  • Kitbashed the biped mech's parts into the quadruped shape to match Rowan Sherwin's concept art.
  • Re-rigged it to reuse the biped's animation on four legs: each biped leg drives two legs of the quadruped. The biped's right leg drives the left front and right back legs, and its left leg drives the other two, which reads as a gallop. The animation still plays only once, just on more targets, so it costs less than playing it twice.
  • Scripted the cockpit swivel to follow the aim direction from mouse movement or a controller joystick, tied into the existing control system.
  • Rigged each piece to be controllable in gameplay, with the cockpit staying level while the body bobs up and down. The cockpit base has no arms; weapons attach at spawn based on the player's loadout.
FIG. 01: quadruped mech galloping on the biped's reused animation, cockpit tracking aim Unity
FIG. 02: the cockpit holds its aim while the body moves Unity
the original biped mech, a store asset by VaxKun
FIG. 03: the original biped mech, a store asset by VaxKun Unity Asset Store
model sheet for the updated mech
FIG. 04: model sheet for the updated mech concept

It took an ill-fitting store asset to a customized, working feature, with no new modeling or animation from anyone else.

URP Conversion

The project came with Unity's standard renderer and needed a full conversion to the Universal Render Pipeline. This wasn't a settings change: it meant recreating every shader under the new rendering model, scripting a batch conversion of the materials, and rebuilding the lighting and post-processing. The outsourced store assets also needed cleanup and modification to work in the new pipeline and match the project's visual direction.

Puppet Rig Retargeting System

One of the project's major challenges was updating the player character to new concept art without remaking the animations that came with the original store asset. The rig's proportions changed, and the animations had position keyframes, so they couldn't simply be reused. I remodeled the character to match the concept, repainted the skin weights, and built a puppet rig system: the original rig and animations run without a skinned mesh and drive rotation constraints on the new rig and mesh. Since only one model's skinned vertices are driven, the performance cost was negligible, and not recreating the animations was a major budget saving. I also split the new mesh into parts so they could be swapped for character customization.

original model and rig next to the updated version
FIG. 05: original model and rig next to the updated version Unity
the original store model, by Suriyun
FIG. 06: the original store model, by Suriyun Unity Asset Store
concept for the updated version, by Rowan Sherwin
FIG. 07: concept for the updated version, by Rowan Sherwin concept
FIG. 08: the updated model in game Unity

The constraints had to be broken and reconnected several times as the model was updated, so I wrote an editor tool that walks the skeletal hierarchy and makes the connections automatically: faster, and without the user error of hundreds of manual clicks.

Character Status FX Shader

Enemies needed visual feedback for gameplay states like burning, impact flash, and frozen. I built a single custom overlay shader for all of them: gameplay script sets a bool on the character, and a helper script turns it into a shader parameter that enables or disables the effect. More than one effect can be active at a time.

Shader-Driven Enemy Wings

The character designs gave every enemy wings, but the enemies were pre-made store assets, and adding wings to their rigs would have meant reworking rigs and animations across the board. I tested the obvious route first: rigged wings parent-constrained to a shoulder bone, using a $5 store asset to check feasibility. It looked great, but a heavy skeletal rig on every enemy wouldn't hold up with a screen full of them, let alone on mobile hardware. So I pivoted to a vertex shader before the rig went any further, taking a cue from the schools of fish in Abzu.

FIG. 09: an earlier version of the wing shader, with the arc still running the wrong way Unity · Shader Graph

The wings are a simple placeholder mesh (easy to swap for a polished model) with a custom shader that drives the flap, including controls for flap speed. They're made as separate left and right pieces so they can be scaled and positioned for each enemy. A script sets the flap per enemy through Material Property Blocks, driven by gameplay: the enemy's velocity, whether it's alive, and more.

Because the motion was based on time, every enemy at first flapped in perfect unison, which looked unnatural. I added a reusable Material Index property that gives each instance a random number and passes it to the shader, again through a Material Property Block, to offset its timing. The result had the look, believability, and performance we needed, and scaled to every enemy that needed wings.

wing flap vertex shader node network
FIG. 10: wing flap vertex shader node network Shader Graph
the Material Index component
FIG. 11: the Material Index component Unity · C#

One open issue remained when the project ended: the wings conflicted with the character outline effect that shows enemies behind obstacles, and I was working on a fix.

Other VFX

A library of VFX built for this project and carried into later ones as prototype building blocks, including a fuel refill timer driven by gameplay script through shader parameters, collectibles, and celebration effects.

FIG. 12: a sampling of the VFX library Unity Particle System
FIG. 13: fuel spawner collectible VFX Unity Particle System
FIG. 14: enemy spawn VFX Unity Particle System
FIG. 15: confetti celebration VFX Unity Particle System

Model Updates

Store assets were modified to fit the game's art direction rather than replaced. The fire pig got changed proportions, a new shape, and larger tusks. The phoenix got new coloring and a mouth mesh, borrowed from another enemy asset we didn't use and skinned on top of the original.

fire pig, original store model by Suriyun
FIG. 16: fire pig, original store model by Suriyun Unity Asset Store
FIG. 17: fire pig, updated model update
phoenix, original store model by Suriyun
FIG. 18: phoenix, original store model by Suriyun Unity Asset Store
FIG. 19: phoenix, updated with new coloring and a mouth model update
fuel can model
FIG. 20: fuel can model 3D model
skull mesh from the portal cutscene, wireframe
FIG. 21: skull mesh from the portal cutscene, wireframe Maya

Portal Cutscene

The project's hell portal opening cutscene was inherited and built on. My additions: the bunny's rising and exploding animation (animated in Maya), sound effects, the skull mesh (shaded with vertex colors so a triplanar splatter texture could be applied at runtime), blood splatter VFX and decals, and the unicorn's animation trigger. I also built the portal opening VFX from parts of an asset used elsewhere in the project.

FIG. 22: hell portal opening cutscene Vimeo

Tools

A Tree Sizer/Rotator/Tinter script randomizes each tree's size, rotation, and position within set ranges. Together with a color tint randomizer, it turns a row of identical trees into a forest without a lot of hand placement.

Besides that and the puppet rig tool, a Scene Composer component: placed in a master scene, it loads additional scene and level assets automatically in the level editor. It sped up iteration while keeping assets separate in source control, which cut down on people overwriting each other's work and on misalignment errors.