# Combined Bayview scene candidate (r340)

## What was built

`tools/merge_nfsu2_world_glbs.py` combines the eight exported regional city GLBs
into one static scene. It deduplicates identical textures, materials, meshes,
and exact placed nodes. The candidate contains 181,792 placed nodes and 23,514
unique meshes; its GLB is about 163 MiB.

## Live Route 736 result

The candidate was loaded in the existing GPU Chrome session at the same
Route 736 start as the packaged L4RA scene. Chrome reached `City scene ready`
with 77,603 nearby triangles and 208 nearby textures. The candidate restores
some nearby regional context, including more of the overhead structure. In this
view I did not see a duplicated road surface or a building visibly crossing
the pavement. This is a single-view visual check, not proof that the region
union is free of overlap elsewhere.

The existing drive route, traffic routes, intersections, and lights are still
selected from L4RA. The combined scene does not yet provide a unified Bayview
traffic/navigation graph, so it is not a replacement for the normal viewer.
It remains a visual and road-support experiment.

## Route 736 spawn alignment

At the default spawn, the car is centered over the double-yellow marking even
though the road surface supports the route. Setting `startLateral=2.15` moves
the car into the visible right-hand lane while keeping it supported by the
exported road. The current automatic lane-offset preview reports zero here
because its source-texture paint detector does not detect the marking. The
manual result is visually better, but I have not generalized the offset from
this one route without checking the underlying route-selection semantics.

See `webgl-city/review/images/485-r340-combined-city-candidate.png` for the
default spawn and `webgl-city/review/images/486-r340-combined-city-lane-start.png`
for the validated manual offset.