World.syncToModel runs after every frame of a run and resolved each
object of the scene anew to compare it with its entity. With 222
entities that was most of the Editor line in the performance panel,
also for entities that are never drawn.
- The world keeps per entity what the model said when it last read
the object (syncFromModel, spawn) or wrote it. A frame compares the
entity with that and resolves nothing while both agree.
- A place that differs is written as three numbers.
- A value that differs is written as an override, and that one object
is resolved again. An override can bring rows of its own, such as a
sprite's shader.
- The objects of entities that left the run are dropped only in a
frame in which one left. World.remove notes that.
- Editing during a run works as before: the editor has the model read
again on every project event, which renews what the world keeps.
One difference: a write to the model that goes past the editor and
does not have it read again now stays. The next frame used to
overwrite it with the entity's state. No code does that, during a run
only the world writes.
Measured on stein2 with a copy of the reference project of #284, ms
per frame: syncToModel alone 0.92 to 0.12 (Node, 600 frames), the
Editor line in the browser 1.14 / 1.20 / 1.29 to 0.25 / 0.25 / 0.27.
Physics and Drawing are unchanged.
Tests:
- Gate: 198 files, 2891 tests (2887 + 4), exit 0
- e2e, full run: 1613 checks passed, exit 0. That measures the total
that was only computed since #273.
- Smokes: 24 / 19 / 21, exit 0
- Four new unit tests, no new e2e check: 60 unchanged frames resolve
nothing, an edit during the run arrives and stays, an override with
rows of its own is seen with them, container content in an editor
run is written into the instance edits once
- Seven counter-probes fail, 1 to 4 tests each
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
adminandClaude Opus 5.5
26cc6324af