Home / Work / Desert Drive
OWN PRODUCT · REAL-TIME 3D · MOBILE

Three real deserts,
at 60 fps on a phone.

Our own product, in development: a calm 4×4 dune-driving game set in three real UAE deserts. No race clock by default — just dunes, light and nine flags to find while the sun goes down. Built because real-time 3D and physics on hardware we don’t control is the same skill set as a digital twin or a training simulator.

Status
Own product, in development
Engine
Godot 4, .NET / C#
Code
~16,000 lines, custom shaders
Locations
Al Qudra · Big Red · Liwa
Android
60 fps on our test phone, 45 MB bundle
Desktop
Windows build runs
A white 4x4 driving along a red dune crest toward a low sun, from our game
3
Real UAE deserts, 9 km² each
60fps
On our Android test phone
0.6ms
Deformable-sand update
45MB
Android store bundle
In-engine capture — the tracks stay in the sand
A dark 4×4 climbing a rippled red dune, its tyre tracks left in the sand behind it and its shadow cast across the slope
/ 01
The Problem

We wanted a driving game that feels like a real afternoon in the UAE dunes, not a race across generic orange sand — and it had to run smoothly on an ordinary Android phone.

That is a harder brief than it sounds. Large open terrain, sand that changes under the wheels, light that moves, and vehicles that behave like their real counterparts all compete for the same few milliseconds per frame, on hardware we don’t choose.

It is also exactly the problem behind digital twins, site visualisation and training simulators. Building our own product is how we keep those skills sharp.

/ 02
The Approach

Three real deserts, each with its own character. Al Qudra is pale and gentle. Big Red, at Lahbab, is rust-red with a 58 m great dune. Liwa, on the edge of the Empty Quarter, has an 85 m great dune and salt flats.

Each location covers 9 km² and has its own dune height and spacing, sand colour and sun angle. Native plants — ghaf, markh and arta — are placed by habitat rather than scattered at random. Slopes are capped at sand’s angle of repose, about 33°, and the colours were matched to real dune photographs.

The default mode is Wander: no clock, nine flags to find while the sun sets over about twelve minutes, ending on a card of the route you drove. A contest mode puts you against four bot drivers.

/ 03
The Hard Parts
  1. Sand that keeps your tracks A 128 m patch of deformable sand at 0.25 m resolution keeps every track the tyres leave. The update costs 0.6 ms a frame, small enough to leave room for everything else.
  2. Light that moves As the sun sinks, dunes cast their shadows on one another, so the landscape changes over the twelve minutes of a drive. Custom shaders handle the dunes, the sand surface and the vehicle paint.
  3. Vehicles that behave like vehicles Five 4×4s, each with real horsepower, torque and gear ratios. Handling is tuned against dune-driving reports, with automatic low range and crawl. The engine sound is synthesised from cylinder firing pulses rather than looped from a recording.
  4. Sixty frames a second on hardware we don’t control Adaptive quality scales the work to the device. On our Android test phone it holds 60 fps from a 45 MB store bundle, and the same code runs as a Windows build.
/ 04
The Outcome

The game is still in development. Today it runs at 60 fps on our Android test phone and as a Windows build, from about 16,000 lines of code on Godot 4 and C#. There is also a downtown city mode, built from OpenStreetMap data.

For clients, the point is the capability: large real-world environments, physics and moving light rendered in real time on devices nobody can standardise. That is what a plant digital twin, a site walkthrough on a tablet or a training simulator needs.

Stack Godot 4 C# / .NET Custom shaders Deformable terrain Vehicle physics Procedural audio Adaptive quality Android Windows OpenStreetMap

Sixty frames a second,
on hardware we don’t control.

REAL-TIME 3D

A site, a plant or a procedure
you need to walk through on a tablet?

Contact Us →