The runtime streamer keeps a 3x3 ring of chunks resident (loadRadius=1). The "current map" screenshot shows that ring (chunk_02_02 .. chunk_04_04) already covers a large expanse — far more than the 5-10 city blocks we actually need near the viewer. Hypothesis: each chunk is too large, so even a minimal ring over-loads geometry/memory.
Explore: what is chunkSizeMeters today, how many blocks does one chunk span, what's the right chunk size (or loadRadius) for ~5-10 blocks resident, and the tradeoffs (more chunks = more streaming churn vs. less resident geometry).
Relates to #104 (streaming hitches); split off from #107 (enter/exit), which found chunk size was NOT the enter/exit cause.
The runtime streamer keeps a 3x3 ring of chunks resident (
loadRadius=1). The "current map" screenshot shows that ring (chunk_02_02 .. chunk_04_04) already covers a large expanse — far more than the 5-10 city blocks we actually need near the viewer. Hypothesis: each chunk is too large, so even a minimal ring over-loads geometry/memory.Explore: what is
chunkSizeMeterstoday, how many blocks does one chunk span, what's the right chunk size (orloadRadius) for ~5-10 blocks resident, and the tradeoffs (more chunks = more streaming churn vs. less resident geometry).Relates to #104 (streaming hitches); split off from #107 (enter/exit), which found chunk size was NOT the enter/exit cause.