Patrick Mardy Portfolio

Blink Security

Hard-surface assets with editable finishes, three levels of detail and event-driven interaction.

Engine: Unreal Engine 5
Video output: 1920 × 1080, 30 fps
Films: Product film 33 s, Blueprint run 25 s
Blueprints: Device logic + presentation rigs

Frame 000 / 975 Product film · 33 s

Inside the build

Devices. The Video Doorbell in black and white finishes and the XT2 Outdoor Camera on its ball-joint mount. Each is modelled at its published size, with three LODs, one simple collision box and one UV channel.
System. The doorbell and camera are children of BP_BlinkDevice, which holds the device name, the Armed state and a Report command.
Training set. A small level with a porch, a path and a stand-in visitor. The visitor walks up, sets off the camera's motion zone and rings the doorbell.
No Event Tick in the system. Motion detection uses overlap events, the visitor walks with a latent Move Component To, and the LED pulses run in the material from a start time the Blueprint sets.

From mesh to interaction. The device models are supported by a shared Blueprint base, editable material parameters and commands for button presses and armed state.

Asset checks

Scale, triangles, LODs, UVs, collision, materials

Static mesh	Published size (mm)	Model bounds (mm)	Triangles LOD0 / 1 / 2	Material slots	Collision · UVs
`SM_Blink_Doorbell`	128.4 × 42.9 × 27.9	128.4 × 42.9 × 29.9*	4,324 / 2,161 / 865	6	1 box · UV0
`SM_Blink_XT2_Camera`	70.5 × 70.5 × 35.6	70.5 × 70.5 × 39.6*	4,616 / 2,308 / 924	7	1 box · UV0
`SM_Blink_XT2_Mount`	–	46.0 × 46.0 × 42.0	1,584 / 791 / 317	1	1 box · UV0

* Depth includes the raised lens bezel or sensor dome. LODs are reduced to 100, 50 and 20 % at screen sizes 1.0, 0.25 and 0.08. Nanite is off on these small props.

Wireframe of the Video Doorbell — Wireframe, Video Doorbell.

Wireframe of the XT2 Outdoor Camera and mount — Wireframe, XT2 Outdoor Camera and mount.

Doorbell wireframe at LOD0, LOD1 and LOD2 with triangle counts — Doorbell LOD0, LOD1 and LOD2, forced in the viewport.

UV channel 0 layout of the doorbell mesh — UV channel 0, doorbell.

UV channel 0 layout of the XT2 camera mesh — UV channel 0, XT2 camera.

UV channel 0 layout of the XT2 mount mesh — UV channel 0, XT2 mount.

Both doorbells with their simple collision boxes drawn — Simple collision: one box per mesh.

The doorbell in a white and a black finish — Material instances: one doorbell mesh in white and in black from the same parent. The LEDs use a second parent material with Color, Intensity, BaseGlow and pulse parameters.

Device behaviourExplore the Blueprints +

BP_BlinkDeviceBase class

Holds the device name and the Armed state. Report passes each event on. If the device isn't set up, it logs a warning instead of failing silently. SetArmed is a command with a Boolean input: it stores the state and reports it.

BP_BlinkDoorbellChild of BP_BlinkDevice

PressButton sets the LED ring's PulseStart parameter to the current time, so the material plays the pulse without Tick, then reports the press.

PressButton function graph — PressButton.

BP_BlinkCameraChild of BP_BlinkDevice

Begin Play makes a dynamic material instance for the red recording LED. When a person enters the MotionZone while the camera is Armed and not already recording, the LED turns on and the camera reports. After Clip Length, the LED turns off and it reports the clip as saved.

BP_BlinkCamera event graph with Begin Play and motion overlap sections — LED material and motion detection.

Showcase rig

BP_ShowcaseDirector · one pass, then loops

A separate presentation layer: one Director Actor drives a turntable and a camera rig per device and calls the same device commands the training set uses. This clip shows its doorbell and XT2 segments.

Frame 000 / 736 Blueprint run · 24.6 s loop

In this clip	Device	What the Director does
0.0 s	Video Doorbell	Cuts to the doorbell camera. The turntable makes one full turn (5 s at 72°/s), then the camera orbits for 6 s and pushes in over 4 s. The button is pressed 1.8 s into the orbit.
11.0 s	XT2 Outdoor Camera	One turntable turn, then a motion sequence: the head pans and tilts on its ball joint in four eased steps, turns on its red LED and reports the event "Re-aimed - recording clip".
24.6 s	Loop	Loop is on, so the Director starts again at the doorbell.

Presentation rigExplore the Blueprints +

BP_ShowcaseDirectorDirector

Runs the showcase from Begin Play. The graph has one commented section per device and a Loop section. Each device section repeats the same steps.

Set View Target with Blend (device camera) → Reset Camera → Start Spin → Delay (Turntable Time) → Stop Spin → StartOrbit → device commands

Settings
Turntable Time	5.0 s
Orbit Time	6.0 s
Loop	On

Doorbell section of the Director graph — Doorbell section.

BP_TurntableReusable rig

A Pedestal, a Spinner the device attaches to, and a RotatingMovement component. StartSpin and StopSpin are functions any Blueprint can call. StopSpin snaps the Spinner back to the front, so every shot starts from the same angle.

Settings
Degrees Per Second	72.0 (one turn in 5 s)
Spin on Begin Play	Off

BP_ShowcaseCameraReusable rig

A camera on a Boom, turned by an Orbit movement component. The Construction Script places the camera from Distance and Height and aims it at Focus Height, so the framing updates in the editor as the values change. StartOrbit turns the Boom and pushes the camera in with a latent Move Component To. ResetCamera puts everything back.

Settings
Distance	62.0
Height	14.0
Focus Height	6.0
Orbit Degrees Per Second	28.0
Push Distance	34.0
Push Height	5.0
Push Time	4.0 s

Distances in Unreal units (1 unit = 1 cm).

Construction Script graph of BP_ShowcaseCamera — Construction Script framing.

StartOrbit graph with Move Component To — StartOrbit push-in.

Liquid Death

A study in cylindrical form, metal finishes and fluid motion.

Engine: Unreal Engine 5
Video output: 1920 × 1080, 30 fps
Loop: 6 s, 180 frames, seamless
Blueprints: 2 Actor Blueprints

Frame 000 / 179 Orbit loop · 6 s

Inside the build

Can. A lathe profile (a shape spun around its centre) built to real size. It is split into CanBody, CanLid, CanTab, CanAluminium and CanDrops under one CanSpin pivot.
Materials. M_Metal is a parent material with parameters. MI_Gold and MI_Aluminium are instances of it, so a finish changes without touching the graph.
Water. A particle fluid simulation baked to 180 meshes, SM_Water_000 to SM_Water_179. The Blueprint shows one mesh per frame on a single Water component. The simulation used the same spin as the can, so the water drags with it.
Camera. A CineCamera on a yaw pivot, set to a 16:9 digital film back, 50 mm and f/8. Orbit, push-in and height are exposed as settings.

Motion & Blueprint breakdownExplore the build +

BP_LiquidDeathSplash2Can and water

Spins the can and plays the simulation frames. The graph has three commented sections: Loop Clock, Can and Simulated Water.

Event Tick → Time → LoopT = Time ÷ LoopDuration → Phase = LoopT × 360 → Make Rotator → Set Relative Rotation (CanSpin)

Fraction(LoopT) × frame count → Truncate → Get (Water Frames) → Set Static Mesh (Water)

Settings
Loop Duration	6.0 s
Water Frames	Array of simulation meshes

Event graph of BP_LiquidDeathSplash2 with three comment boxes — Full graph: Loop Clock, Can and Simulated Water.

Loop Clock and Can sections of the graph — Loop Clock and Can.

Truncate, Get and Set Static Mesh nodes — Simulated Water: frame lookup.

BP_CanOrbitCameraCamera rig

Orbits the camera around the can, pushes in and rises on a cycle, then aims at the can every frame. Each motion runs off the same loop clock as the can and the water, so the three stay in step.

Phase → CameraYaw turns OrbitDegrees · distance eases in by PushIn, PushCycles times per loop · height rises and dips by HeightSwing once per loop · Find Look at Rotation → Set World Rotation (CineCamera)

Variables

LoopDuration
OrbitDegrees
Distance
PushIn
PushCycles
Height
HeightSwing
FocusHeight

Event graph of BP_CanOrbitCamera with four comment boxes — Full graph: Loop Clock, Orbit, Dolly and Height, Apply.

Orbit, Dolly and Height, and Apply sections of the camera graph — Orbit, dolly, height and aim.

Review log

Problems I caught

Problem	Change
The label read mirrored	UVs corrected so the artwork reads the right way round.
The water didn't act like liquid	The first version's procedural swirls and droplets were replaced with a particle fluid simulation, baked to 180 frames.
The lighting was blown out	Lighting reworked in its own review round.

Soundcore Sport X20

A component-based earbud assembly with coordinated motion.

Engine: Unreal Engine 5
Video output: 1920 × 1080, 30 fps
Loop: 16 s, 480 frames, four 4 s cycles
Blueprints: 2 Actor Blueprints

Frame 000 / 479 Crossing loop · 16 s

Inside the build

Earbuds. Modelled from photos, with collision. Each bud is split into nine named parts (Collar, CollarTrim, Eartip, Faceplate, Grille, Hook, Logo, Nozzle and Shell), so every part keeps its own material slot and pivot.
Rig. A CrossPivot carries Arm_L and Arm_R, and each arm carries one bud. A single eased value, Alpha, drives both the swing and the spin, so the parts can't drift out of step.
Timing. Alpha runs 0 → 1 → 0 every 2 × Cross Duration. At the default of 2.0 s that is a 4-second cycle, four cycles in the 16-second render.
Dynamic version. BP_X20_CrossingGate2 adds a float, a camera orbit, a dolly zoom and a height swing. Every motion is a whole number of cycles per loop, so the loop is seamless.

Motion starts with the assembly. Separate components and a shared motion value keep the two earbuds coordinated while exposing timing and rotation as editable settings.

Motion & Blueprint breakdownExplore the build +

BP_X20_CrossingGateCrossing motion

The buds swing across each other around CrossPivot while spinning, then swing back.

Event Tick → Time ÷ CrossDuration × 180 → cos → Alpha = 0.5 − 0.5 × cos · Swing = Alpha × CrossDegrees · Spin = Alpha × SpinDegrees, with negated copies for the counter motions → Set Relative Rotation on CrossPivot, Arm_L, Arm_R, Bud_L and Bud_R

Settings
Cross Duration	2.0 s
Cross Degrees	180.0°
Spin Degrees	360.0°

Start of the crossing-gate graph: time, cosine easing and degree multipliers — Alpha easing, swing and spin.

Chain of five Set Relative Rotation nodes — Rotation applied to pivot, arms and buds.

BP_X20_CrossingGate2Dynamic loop

The crossing motion plus a float, a camera orbit, a dolly zoom and a height swing, all tied to one loop clock. At the defaults that is three crossings in a 12-second loop, the same 4-second rhythm as the first version.

Settings
Loop Duration	12.0 s
Crossings Per Loop	3.0
Cross Degrees	180.0°
Spin Degrees	360.0°
Float Height	4.0
Orbit Degrees	360.0°
Camera Distance	560.0
Zoom In	0.45
Zoom Cycles Per Loop	2.0
Camera Height	20.0
Camera Height Swing	45.0
Focus Height	14.0

Earbud Crossing, Float, Camera Orbit and Camera Zoom sections of the graph — Crossing, float, orbit, zoom and height.

Apply Earbud Motion section of the graph — Apply earbud motion.

Apply Camera section of the graph — Apply camera and aim.

The details behind the result

Real references, real size

The Blink breakdown compares reference dimensions with model bounds. Raised lenses and sensor domes are called out separately so depth differences stay visible.

See the mesh table

LODs, UVs and collision

Every Blink mesh has three LODs, one UV channel and one simple collision box, checked in wireframe, UV and collision views. Pivots sit where the object moves, like the XT2 head on its ball joint.

See asset checks

Editable materials

A parent material exposes parameters and each finish is an instance: MI_Gold and MI_Aluminium, the doorbell in black and white. LEDs are driven at runtime through material parameters.

See material instances

Event-driven Blueprints

The Blink devices expose PressButton and SetArmed commands. Motion detection responds to overlap events; shared device logic lives in a base class.

See system Blueprints

Readable graphs

Blueprint screenshots show the logic in labelled sections, with exposed settings and motion formulas alongside the graphs.

See the graphs

Asset organisation

Meshes, materials, instances, Blueprints and textures use distinct SM_, M_, MI_, BP_ and T_ prefixes. Named components make assemblies easier to inspect.

Troubleshooting

Reproduce the problem, then narrow it down: empty material slots, the Reference Viewer for missing textures or parents, breakpoints on the node that misbehaves. Black renders on one project came down to an unsaved level.

3D asset portfolio

Selected work

Blink Security ↗

Liquid Death ↗

Soundcore Sport X20 ↗

Blink Security

Inside the build

Asset checks

Showcase rig

Liquid Death

Inside the build

Review log

Soundcore Sport X20

Inside the build

The details behind the result

Real references, real size

LODs, UVs and collision

Editable materials

Event-driven Blueprints

Readable graphs

Asset organisation

Troubleshooting