alt Hacker NewsHow to run a city builder on 16 MHz
Comments
> The original SimCity for example lists Intel’s 386SX as the CPU in it’s system requirements.
Not sure where that comes from. The original release box art [1] says it will work on any PC with 512KB of ram. So that's an 8088 running at just 4.77 MHz.
But that's far from the lowest spec port of the game. The Commodore 64 version might have been missing quite a few features (like stadiums, police/fire stations and railways), but the main city simulation loop was there in just 64KB of ram and a 1MHz 6502.
And the BBC Micro/Acorn Election port was even more impressive. Had basically all the features of the full Amiga/PC/Mac version, only missing Music/Sound/Animation. With a 2Mhz 6502 (or 1Mhz on the Election) and just 32KB of ram.
[1] https://images.launchbox-app.com/79861ce4-75ea-46dd-b46e-521...
This reminds me of microcity which is a Simcity Clone for the Game Boy Colour.
The author has some great in-depth docs about the design, and how they managed to make a fairly lively-seeming simulation fit into a machine with an 8 MHz 8-bit processor.
https://github.com/AntonioND/ucity/blob/master/docs/index.rs...
The implementation: https://github.com/SimHacker/micropolis/blob/master/micropol...
O huh. I just learned that SHADOWFIRE on the C64 is able to simulate 50 different characters, by only updating one of them per frame. So the limit is 50 to fit the refresh rate of a PAL TV.
This is a good revelation but is a technique that is old as the hills. My first post university programming job was working for CAE Electronics, a Flight Simulator company. The simulations ran on a variety minicomputers of the era, primarily DEC Vax 780 and successors or Gould SEL during my time there.
If memory serves me correctly the simulation ran like a super loop on a microcontroller every 50ms or 33ms. On each loop the dispatcher would run a selection of the core simulation functions some every loop, some at every 2nd, 4th or more loops. The system was called banding. The dispatch table was redone to optimize the needs of that particular simulator.
There were various optimization outside of the main cpu as the peripheral devices did computation as well. Also as the systems got faster there was time left over for the normal OS to run low priority function with non real-time requirements.
The technique was not new in my time and had been used on the previous generation of Xerox systems about a decade earlier.