# Browser drive input capture (r333)

This is a check of the currently served WebGL viewer, not a comparison with
retail gameplay. It used the existing headless Chrome session at route 736,
with the page debug flag enabled, and injected W/A key events through Chrome's
debug protocol. The scene reported `City scene ready`; the page error field
was empty.

## Observed low-speed response

In one straight-to-turn sample, the initial player state was `(x,y)=(-1005.94,
-220.93)`, heading `1.6481`, speed `0`. After one second of W, position was
`(-1006.04,-219.64)` and speed `2.44 m/s`. After one additional second of W+A,
position was `(-1006.52,-216.59)`, heading `1.8061`, speed `4.62 m/s`,
`steerInput=1`, and wheel steer angle `0.1184 rad`.

A second W+A sample started from rest at heading `1.8570`. After 1.5 seconds,
the viewer reported position `(-1011.21,-200.70)`, heading `1.9271`, speed
`2.52 m/s`, `steerInput=1`, and wheel steer angle `0.1559 rad`. The associated
frame is [476](../webgl-city/review/images/476-r333-steering-at-low-speed.png).
The state read and screenshot were adjacent but not frame-synchronized: the
screenshot HUD read 8 mph in first gear at 2,555 RPM.

The W-only packaged view is [475](../webgl-city/review/images/475-r333-live-drive-after-2s.png).
The vehicle moves forward, updates its speed/gear/RPM display, and turns in
response to A. These captures establish basic input wiring and movement only;
they do not calibrate the driving model against XP.

## Visible remaining issue

The Route 736 capture still shows an opaque blue wedge at the Mega Low shop.
The source geometry is an authored `SHOPBEAM` object, but the texture and draw
state are missing. Its exact appearance cannot be corrected from the current
static asset set; see [the material audit](shopbeam-megalow-material-audit-r328.md).
This capture also does not resolve the 240SX's missing main glass pane texture.