# Live player-car roster audit · r456

The packaged L4RA WebGL viewer was loaded in host Chrome on the Route 450 drive
start. I enumerated the actual `#car-select` options and switched each choice
in the same running city session. Every option completed its asynchronous model
load; the selector became enabled again, `#status` remained `City scene ready`,
and `#engine-state` reported that car's matching original AEMS/Ginsu recordings
were ready. Chrome reported no page exceptions, console errors, or failed
requests over the full selection sequence.

The 29 live selections were:

`240SX`, `3000GT`, `350Z`, `A3`, `CELICA`, `CIVIC`, `COROLLA`, `ECLIPSE`,
`ESCALADE`, `FOCUS`, `G35`, `GOLF`, `GTO`, `HUMMER`, `IMPREZAWRX`, `IS300`,
`LANCEREVO8`, `MIATA`, `MUSTANGGT`, `NAVIGATOR`, `PEUGOT`, `RSX`, `RX7`,
`RX8`, `SENTRA`, `SKYLINE`, `SUPRA`, `TIBURON`, and `TT`.

This confirms runtime selection and asset/audio-profile loading, not a separate
visual or driving evaluation of every car. The existing 350Z capture in the
review feed shows one selected vehicle driving in the city. Per-car paint and
handling fidelity remain incomplete.