Rendering 100K units requires a lot of CPU cycles, so the second half of the video shows the setup running at (a bit unstable) > 60 FPS!

So I spent a few days tinkering with the containers the indoor pathing code relied on and boosted the numbers to 400-600 per frame (normal case: 2K to 3K), then distributed the load throughout multiple frames if needed.

Typically 2%-6% of the population (when awake) will change their activity per in game minute. Thus every ~2,000 population ate up a frame. In a real city, this number is probably closer to ~10,000 (i.e. 500 processed units per frame).

For this building (which is quite large), it came out to ~75 units per frame (@ 60FPS). <"worst case">

This became an issue when I began batch-processing units to update their activity each in game minute. Hard to say the max number of units it could handle since it depends on building size and the units schedule (e.g. at work they move around less)

There’s a guideline: 1% of purchase price per year for maintenance. Just realized that number is affected by inflation too 👀

I like all the feedback! Bluesky compresses all the pixels out of videos so it probably wasn't clear, but the default option is randomized widths. I assume you meant width where you said depth, since the depth is based on the selection box. (And the game will slightly randomize those too)