Building comparison
head to head
DrivervsNeed for Speed II
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.
Need for Speed II
Execution · Pure Mechanics
Arcade driving that tests cornering execution over a small set of memorisable tracks.
Driver leans Execution (Pure Mechanics); Need for Speed II leans Execution (Pure Mechanics).
DriverNeed for Speed II
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
Need for Speed II
Cornering and throttle control decide every race
Reads0 vs 1
Need for Speed II leans a little harder on reads, though the gap is small.
Driver
Police AI is mappable
Need for Speed II
AI racers follow rubber-banded scripts, not minds
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
Need for Speed II
Tracks are fixed; nothing meaningful is hidden
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
Need for Speed II
Learning six tracks' racing lines and car choice
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.