A single point of technical accountability
The client talks to one person who understands the project top to bottom, instead of splitting context across several specialists.
§ About OneBatch
A technical art practice built around a single problem.
OneBatch exists exclusively for location-based VR experiences (LBVR) — the format where performance, tracking and room physics matter as much as the art.
Founder
Pau Raurell
OneBatch is the name Pau Raurell works under — a technical artist who takes on LBVR projects end to end, from technical architecture to the last optimization pass.
No account layer, no hand-offs between specialists: whoever builds the project is who you talk to, from the first feasibility call to opening day.
«The name comes from one draw call batch: the smallest unit of work the GPU processes at once. Every project is treated as a whole system, not a list of separate tasks.»
Unlike an isolated art or programming role, OneBatch covers the project end to end: technical feasibility, scene creation, shaders, effects and the optimization work that decides whether an experience survives six hours of back-to-back sessions in a room full of people.
That means stepping into a project at any stage — from an unvalidated idea to a production that needs technical rescue — and speaking the same language as the client's art team, programming team and room operator.
§ 01 — Way of working
How OneBatch works alongside your team
Joins your pipeline directly
Works inside the client studio or agency's own tools and pipeline, as an embedded specialist rather than an outside vendor.
Performance isn't the last phase
Performance budgets are set before the first asset, not negotiated after the first crash on site.
§ 02 — Technical stack
Tools and technologies used daily
Engines
- Unity
- Custom render pipelines (URP/SRP)
Shaders & VFX
- HLSL
- Shader Graph
- VFX Graph
Code
- C++
LBVR & tracking
- OpenXR
- Multi-user area tracking
Pipeline & control
- Perforce / Git
- Asset CI
- Profiling on target hardware