§ Projects

LBVR project case studies

Four common types of engagement, with the technical challenge, what was built and the result. Projects marked Placeholder are waiting on real client content — the structure is already in place to replace them.

Placeholder

[Project name]

[Client / LBVR venue] · 20XX · Multiplayer experience

UnityHLSLPhoton

The challenge

The real technical or creative challenge of the brief — for example, syncing N players on area tracking with zero perceptible latency.

What was built

Scene, systems and shaders developed to solve the challenge, plus the pipeline tools used to deliver on time.

Result

Measurable or qualitative outcome: sustained framerate, session length, on-site feedback.

Placeholder

[Project name]

[Client / attraction operator] · 20XX · Single-player installation

Unreal EngineNiagaraOpenXR

The challenge

A concrete physical or technical constraint of the project: available space, target hardware or performance budget.

What was built

Shader, VFX and optimization systems developed specifically for this brief.

Result

Production impact: reduced draw calls, higher framerate, shorter load time.

Placeholder

[Project name]

[Confidential client] · 20XX · Prototype / R&D

UnityCustom render pipeline

The challenge

The technical question the prototype needed to answer before committing to full production.

What was built

What was built to validate the hypothesis, and in how much time it was delivered.

Result

The decision it enabled: green light, change of direction, or estimated savings.

Placeholder

[Project name]

[Studio / partner agency] · 20XX · Technical support to production

Unreal EngineC++Perforce

The challenge

A technical bottleneck blocking the internal team before onboarding.

What was built

Tools, pipeline or shader refactor delivered to unblock production.

Result

Production time recovered, or delivery milestone reached.

Does your project look like one of these?

Let's talk