# Single-region Bayview drive capture (r354, 2026-10-16)

The retail loader trace in
[`city-region-overlap-audit-r203.md`](city-region-overlap-audit-r203.md)
formats the active track identifier into one `TRACKS/STREAM%s.BUN` path and
releases the previous stream list before initializing the next. It provides
no evidence that the retail game combines all eight overlapping STREAM
variants at once. The viewer's `?world=combined` option remains a diagnostic
union, not the source-backed default scene selection.

I loaded the packaged Route 736 drive using only `region=L4RA`, then repeated
the road-edge sequence: 3 seconds of W reached 7.49 m/s; 1.5 seconds of A
reached 11.32 m/s; steering back with D reached the road edge; and 1.5 seconds
of S moved the car about 5.6 m in reverse to `−7.12 m/s`. Chrome reported no
page or console errors. The screenshot shows the source L4RA road, its
texture-authored double-yellow marking, the selected 240SX, and one ambient
traffic car. It also still shows the flat gray paint fallback and incomplete
glass. This validates one regional route and its road support, not the whole
city or retail handling.

The visually inspected L4RA and eight-region captures at this Route 736
viewpoint are close; the union is not proven to be the cause of the broader
building-placement complaint. The region-only URL is recommended for
source-faithful scene selection while runtime free-roam track selection remains
unresolved.