Building comparison
head to head
DrivervsRaid over Moscow
Neither is harder. They score identically on all four axes, so the difference between them is in kind, not degree.
Driver
Execution · Pure Mechanics
The 70s-cinema getaway driving game with famously demanding physics.
Raid over Moscow
Execution · Pure Mechanics
A multi-stage 8-bit action gauntlet testing joystick precision over memorised sequences.
Driver leans Execution (Pure Mechanics); Raid over Moscow leans Execution (Pure Mechanics).
DriverRaid over Moscow
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
Raid over Moscow
Joystick precision across flying, shooting and dodging sequences
Reads0 vs 0
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Driver
Police AI is mappable
Raid over Moscow
Defences follow fixed attack scripts
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
Raid over Moscow
Minor timing randomness in enemy fire
Optimization4 vs 4
Same score on optimization - which means the number cannot separate them. The difference is in what each one asks of you.
Driver
City routes and mission tactics learnable
Raid over Moscow
Each stage has a learnable optimal approach
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.