Building comparison
head to head
DrivervsPure
Neither is meaningfully harder - they pose close to the same test. The widest gap is reads, and it is a single point.
Driver
Execution · Pure Mechanics
The 70s-cinema getaway driving game with famously demanding physics.
Pure
Execution · Practiced Mastery
Chaining aerial tricks with precise timing to fuel a boost economy.
Driver leans Execution (Pure Mechanics); Pure leans Execution (Practiced Mastery).
DriverPure
Axis by axis
Execution7 vs 7
Same score on execution - which means the number cannot separate them. The difference is in what each one asks of you.
Driver
Handbrake control and pursuit driving by feel
Pure
Trick timing and landing control feed the boost loop
Reads0 vs 1
Pure leans a little harder on reads, though the gap is small.
Driver
Police AI is mappable
Pure
Rival riders barely react to your lines
Variance1 vs 1
Same score on variance - which means the number cannot separate them. The difference is in what each one asks of you.
Driver
Traffic adds mild unpredictability
Pure
Tracks are fixed once learned
Optimization4 vs 5
Pure leans a little harder on optimization, though the gap is small.
Driver
City routes and mission tactics learnable
Pure
Bike tuning and trick-chain boost economy reward planning
A matching score does not mean a matching test. Two games can both sit at 10 on execution and demand completely different things of you - which is why the reasoning above matters more than the number beside it.