The investigations

Outside the city.
Inside the files.

Our out-of-bounds visits and HUD texture experiment: what we found, how we tested it, and what remains unresolved.

We decoded 677 retail region records and visited six unusual locations using the exploration tools.

Region audit showing our investigation markers A–F
Region audit showing our investigation markers A–F · Select image for full resolution.

The locations we visited

MarkerWhat we sawWhat the evidence establishes
A / B / CThree driving-school-like courses with paving, markings and surrounding structures.Visited in-game. Exact exercise and mission assignments remain untraced.
DA damaged / explosion-like set north of the road network.Mission 17’s bombNOTLocated event selects camera paths positioned at D. Strong static evidence of a failure-cutscene set.
EA damaged scene with internal BOMB / BOMB2 / BOMB3 geometry names.Visited; actual mission use unresolved. Names alone are not sufficient.
FAn isolated floating ramp / stair-like structure.Observed in-game. Purpose and normal accessibility remain unresolved.
First successful visit to A: paved course geometry and surrounding buildings
First successful visit to A: paved course geometry and surrounding buildings · Select image for full resolution.

D is more than an unused-looking scene

In SCRIPT/17.SCB, the bombNOTLocated event selects the Pos5 and Target5 camera paths. CAMPATH/M17.PXD places both paths in D’s region group. That connects the location to a specific mission failure sequence.

This is a code-and-coordinate match. We have not replayed the failure sequence frame by frame, and its precise dispatch threshold has not been fully traced.

Does the game swap these scenes into the city?

The engine does have a table of 42 region replacement pairs. Scripts for missions 8, 10, 11, 14, 15, 18 and 20 activate groups from it. None of D’s or E’s region IDs appears on either side of that table. The mechanism we identified therefore does not directly account for either scene.

The engine’s replacement-group letters are unrelated to our A–F investigation markers.

Coordinates for future work

These are quantised streaming centres in engine units, not safe vehicle spawn points. Camera height must be established separately.

MarkerRepresentative XRepresentative ZRegion
A675840-489472531
B675840-640000534
C675840-790528537
D-37478460108868
E337920227328373
F7168155648244

HUD texture experiment

Old artwork. Final game code.

We also tried the surviving NOTINUSE HUD textures in the running game. This is a compatibility experiment, with final code still controlling the layout.

Experimental texture substitution running in Free Patrol
Experimental texture substitution running in Free Patrol · Select image for full resolution.

Two approaches, different results

First we loaded the complete _NOTINUSE_HUD/MISC.DOB bank. It reached RAM, but area loading halted. The compatible version retains retail resource definitions and page headers, substitutes five packed pixel pages, and copies palette entries within the retail allocation.

That version reached Free Patrol and continued running at 25 guest FPS. Informative rows from all five pages were matched in live VRAM.

This is not a restored old HUD.

The red health bar and changed map colours may result from palette or UV mismatches. Final code still controls the layout. Several sprite names differ between banks, so the intended historical appearance has not been reconstructed.

Keeping the experiment reproducible

The test uses a separate disc copy, with sector EDC/ECC recomputed after substitution. The original image was hash-verified unchanged. The research archive retains both builders, manifests, recovery notes and the successful screenshot.

A useful retail cross-check

Not every unusual asset is hidden content. Code tracing linked the skeleton pedestrian to the retail Halloween theme, GFX_SHOOTER and GFX_PERP to vehicle gunners, and GFS_BACKDROP to sky and horizon scenery. The catalogue labels the historical versions as legacy variants of used roles.

Read the supporting code trace