Two tiers from one bake, and 60 frames a second
The format a cell takes on disk is written before the pipeline that fills it, and with two tiers from the start: a full tier for desktop and home consoles, and a compact tier for handheld-class hardware. Both are made from the same source by the same bake, as build variants. Neither is made from the other.
| Full tier | Compact tier | |
|---|---|---|
| A cell of suburb, measured | 128 KiB | 107 KiB as first drafted; 96 with tighter records |
| A cell of suburb, the limit | 250 KiB | 100 KiB |
| A cell of the centre | 2.5 MiB or less | 800 KiB or less |
| A cell of open country | 40 KiB or less | 20 KiB or less |
| Every cell of the map | about 32 GiB | about 15 GiB |
The compact limit for a cell of suburb started at 60 KiB. The measurement showed 60 can be reached only by building collision, fences and kerbs when a cell mounts, on the slowest CPU of any target, and that has not been timed there. So the limit is now 100, where nothing is built at mount and the saving comes from tighter records alone. The first compact draft saved only 21 KiB, because collision, coarse levels and instances, 81 of 105 KiB, were identical on both tiers.
Rules the format holds to:
- Mounting a cell costs the bytes read and little else.
- Ground, its collision and what the game asks about it come from one stored thing, not three that can disagree.
- A car drives the same on both tiers.
Frame rate
The target is 60 frames a second: no frame longer than 16.7 ms, on the hardware each tier is for. Systems are meant to degrade by construction rather than by retuning. For streaming, the stated bar is stricter than an average: nothing seen before it is loaded, nothing wanted missing, and no single frame over 16.7 ms. The flight over the centre does not meet that last part yet.
This is a draft and not yet approved. Sizes for the centre and for open country are still guesses. Nothing has been measured on the smaller tier's hardware.