# Regional union overlap audit, r393 The Windows XP guest is useful for static file extraction and executable analysis, but it cannot render the retail game in this VM because its virtual GPU lacks the required graphics support. Visual checks for the WebGL reconstruction use the host's headless Chrome with ANGLE/Vulkan on the Quadro P2000. ## Combined-scene finding A fresh packaged Chrome load of `?world=combined®ion=L4RA&debug&debugRoadObjectPrefix=XO_SPOTSTADIUM` reached “City scene ready.” The road-intersection diagnostic found 8 placed `XO_SPOTSTADIUM_1A_FUN` groups in the 360-unit radius around the L4RA start, and all 8 had at least one object triangle intersecting an exported road triangle. The captured driving view also shows a large dark structure across the skyline. The first sampled intersections are at road heights around Z 11–24, so this is not just a distant-sky draw artifact. This explains one visible failure of the eight-region experiment. It does not establish whether those stadium placements are wrong in every retail mode, or what the correct visibility condition is. The retail stream-loader audit at `city-region-overlap-audit-r203.md` shows one selected `STREAM.BUN` path per world-entry invocation and no positive evidence for loading these regional bundles together. Therefore the combined scene remains an invalid diagnostic experiment, not a full Bayview reconstruction. The viewer now labels the link and mode as experimental and warns that the region union overlaps. ## Capture The capture at `webgl-city/review/images/511-r393-combined-stadium-road-overlap.png` came from the already-running host Chrome session configured for ANGLE/Vulkan on the Quadro P2000. The packaged page reached “City scene ready” with 55,164 nearby triangles and 183 nearby textures; it reported no browser or console errors. The diagnostic collection did not move the player or alter the scene.