Chapter 4: When Games Got Real
ā Previous: Chapter 3 | [Series: Chapter 4 of 12] | Next: Chapter 5 ā]
When Games Got Real
Somewhere in the middle of all the fantasy, comedy, combat, and narrative experimentation, computer games discovered they could model reality without becoming dull.
That was not obvious at the time. Plenty of publishers still wanted clean genres, clear victory states, and products that behaved like products. The idea that players might happily spend hours managing a city they could not technically win, or learning an aircraft they might never physically fly, sounded suspiciously like somebody had mistaken work for entertainment.
Will Wright understood something those publishers did not. Systems are compelling when you can touch them.
SimCity emerged from that intuition. Wright had already discovered, while building Raid on Bungeling Bay, that making the world interested him more than destroying it. That reversal matters. Instead of treating simulation as a side effect of action, he treated action as secondary to the pleasure of construction, balance, failure, and adjustment. A city did not need a villain or a princess or a final boss. It only needed enough moving parts that the player started to care what happened when roads, zoning, transit, power, and growth collided.
That was a radical proposition because it trusted curiosity more than conquest.
Publishers famously did not know what to do with it. A game you could not quite win looked commercially suspicious. But the suspicion missed the point. SimCity was not trying to produce the old arcade rhythm of challenge and reward. It was trying to give players a living model and let their intelligence attach to it. The satisfaction came from seeing consequences ripple outward. Build here, break there. Tax too hard, watch the city complain. Ignore transit, feel the sprawl harden. The game turned systems thinking into a form of play.
That is why SimCity mattered so much. It expanded what a computer game could reasonably ask the player to enjoy.
The deeper lineage matters too. Wright was not improvising from nowhere. Urban theory, planning logic, pattern language, simulation models; all of that sat somewhere underneath the toy box. But the brilliance of SimCity is that it did not present itself as a lecture. It hid intellectual seriousness inside approachable control. You did not need to read Jane Jacobs to feel the consequences of bad planning. The system taught by letting you touch it.
That same convergence of simulation and fascination appears in Flight Simulator, though in a different register. Where SimCity turned planning into play, Flight Simulator turned technical realism into desire.
Bruce Artwick's work began long before Microsoft stamped its name on the box. From the beginning, the project lived in the strange borderland between hobby, engineering challenge, and actual aviation practice. The important thing about Flight Simulator was never just that it looked impressive for its time. It was that it behaved seriously enough to stop feeling metaphorical. Pilots used it. Enthusiasts learned from it. Hardware compatibility got judged by whether the software could run properly. A game had become a test of the machine and a rehearsal space for reality at the same time.