# Current findings — 18 November 2026

This section supersedes the initial unvisited-candidate descriptions below.

| Marker | Current identification | Usage evidence |
| --- | --- | --- |
| A / B / C | Three driving-school-like maps, identified by the user after visiting | Visually supported; their exact school exercise/mission assignments are not traced |
| D | Damaged/explosion scene in the north | Mission 17 failure camera sequence statically linked; see below |
| E | Damaged/explosion scene; internal BOMB/BOMB2/BOMB3 geometry names | Actual mission use unresolved |
| F | Isolated floating ramp outside the road area | Observed in-game; purpose unresolved |

## D: mission 17, bomb-not-located failure sequence

SCRIPT/17.SCB contains the event **bombNOTLocated**. In that event the strings **Pos5** (file offset 0x758) and **Target5** (0x778) are followed by native camera-path selection calls 66 and 67. CAMPATH/M17.PXD defines those paths at D, far north of the road network:

- Pos5 runs from X=-364539, Y=-4159, Z=560174 to X=-384506, Y=-15839, Z=585487.
- Target5 points into the same area: X=-364600, Y=-3559, Z=574160 through X=-370603, Y=-5931, Z=582113.
- D's region centres are 68 (-374784, 601088), 69 (-376832, 561152) and 83 (-338944, 559104).

This is strong static evidence that **D is deliberately filmed during mission 17's bomb-not-located failure event**, rather than simply being an unused damaged location. We have not replayed that failure event to verify the rendered sequence frame by frame. It looks like a separately staged cutscene area; no evidence found that these three D regions are swapped into the normal city.

The exact countdown/proximity condition that dispatches bombNOTLocated has not been fully traced, so no precise timer threshold is asserted.

## Region swapping exists, but does not establish D/E swaps

The engine has a replacement table with **42 source-to-replacement region pairs**. Native script function 78 activates a lettered group through the routine at 0x80031504; the loader at 0x800315F8 then redirects source IDs to replacement IDs. The following numbered scripts call this during **Setup**:

| Mission script | Replacement group |
| --- | --- |
| 08.SCB | G |
| 10.SCB | A |
| 11.SCB | B |
| 14.SCB | E |
| 15.SCB | F |
| 18.SCB | C |
| 20.SCB | K |

**These engine group letters are unrelated to our audit markers A–F.** For example, engine group E does not mean our harbour candidate E.

None of the D region IDs (68,69,83) or E IDs (362,373,388) appears on either side of this table. Thus the particular swap mechanism identified here does not directly account for either candidate. This does not rule out another object replacement, relocation or cutscene mechanism.

## E: still unresolved

E's damaged appearance and BOMB names are suggestive, but they are not enough to assign it to a mission. The camera-path scan found no path centred at E comparable to D's exact mission-17 match. Mission 14 paths pass through the wider neighbourhood; that is insufficient to establish use of E. Mission 11 has an aBomb event and mission 17 has bomb events, but names alone do not link those events to E's geometry.

No claim is made that E is unused or that it is swapped into the main city. Further evidence would require tracing named scene objects/dynamic geometry or observing mission events in-game.

## Updated audit files

The annotated off-map-region-audit.png (also copied into work), map-region-audit.csv and map-region-audit.json now include our observed identifications and the D mission link. region-replacements.csv lists the complete engine replacement table. region-event-evidence.json preserves script offsets, camera samples and activation calls. Trace-Region-Events.py regenerates the static evidence without touching the emulator.

---

# Off-map and detached-region audit — 18 November 2026

## Result

The retail city contains 677 region records. Ten centres lie outside the 512 x 256 retail map image, all south of its bottom edge. All ten have the streaming selector skip bit clear and non-empty DAY.STR payloads containing named geometry records. This establishes real off-map city data, not a verified secret playable level.

Two separate five-region streaming-neighbour groups make up these ten records. A third five-region group sits immediately north, inside the map image but beyond the drawn road system. Their source names run through STR_L_405 to STR_L_420. Their placement in a repeated narrow strip makes alternate/staged assets a possibility, but their purpose has not been identified.

## Candidate groups

| Marker | Region IDs | Representative centre X, Z | Evidence |
| --- | --- | --- | --- |
| A | 530–532, 556–557 | 675840, -489472 (531) | Detached five-region group inside bottom edge; STR_L_405/406/408/409/420 |
| B | 533–535, 558–559 | 675840, -640000 (534) | Off-map group; STR_L_410/411/412/413/414 |
| C | 536–538, 560–561 | 675840, -790528 (537) | Farther off-map group; STR_L_415/416/417/418/419 |
| D | 68, 69, 83 | -374784, 601088 (68) | Detached northern group; STR_B_300/301/302 |
| E | 362, 373, 388 | 337920, 227328 (373) | Detached harbour group explicitly named STR_J_BOMB / BOMB2 / BOMB3 |
| F | 244 | 7168, 155648 | Lone harbour record STR_G214 |

These X/Z values are quantised streaming centres, not validated spawn points. Height has not been established for a safe visit. The southern payload roots have Y=-4000; this is an asset transform, not a recommended camera/car height.

## Off-image payload inventory

| Region | X | Z | DAY.STR offset | Payload bytes |
| --- | --- | --- | --- | --- |
| 533 | 675840 | -603136 | 0x0271B000 | 12288 |
| 534 | 675840 | -640000 | 0x02729000 | 32768 |
| 535 | 675840 | -676864 | 0x0273E800 | 24576 |
| 536 | 675840 | -754688 | 0x02751000 | 12288 |
| 537 | 675840 | -790528 | 0x0275F000 | 30720 |
| 538 | 675840 | -827392 | 0x02773800 | 24576 |
| 558 | 712704 | -640000 | 0x028EE800 | 28672 |
| 559 | 711680 | -674816 | 0x02902800 | 24576 |
| 560 | 712704 | -790528 | 0x02914000 | 28672 |
| 561 | 711680 | -825344 | 0x02928800 | 20480 |

## Method and confidence

CITY.HDR was extracted directly from MERGED/DAY_STD.MRG. Header count is 677; its region table pointer is a relative offset with a -4 base adjustment. Each record is 12 bytes. X is the signed 12-bit field at bits 9–20 scaled by 1024; Z is the signed 11-bit field at bits 21–31 scaled by 1024. Low three bits give streaming-neighbour count; bit 3 is skipped by the nearest-region selection loop at 0x8002F280. The payload word uses low 27 bits for DAY.STR byte offset and upper five bits for size in 2048-byte sectors (0x8002F588 onward).

Map coordinates follow the retail renderer at 0x80035AE0–0x80035B68: u=(X+710400)*127/469600; v=(648400-Z)*63/298400. These expressions omit only integer subpixel rounding. The overlay closely follows the retail roads across the city. “Outside” is tested against the complete 512 x 256 texture image, not merely the road outlines.

Small groups were found by treating the streaming-neighbour references as an undirected graph, excluding skipped records. These are not navigation links. A disconnected streaming group can be a mission variant, an asset parked off-map, ordinary scenery or a reachable area. No collision/reachability test or in-emulator visual inspection of these targets has yet been performed. No live game state or scripts were changed by this audit.

## Files

- off-map-region-audit.png: annotated map; also copied into work.
- map-region-audit.csv / .json: all 677 records, neighbours, payload offsets, names and map coordinates.
- Audit-Map-Regions.py: reproducible audit, requiring Python and Pillow.

Next: inspect group A first, then B and C with controlled streaming and a recoverable checkpoint; capture what each actually looks like before assigning names or making accessibility claims.

## Candidate A visited, 18 November 2026

Moved the camera/player to X=695000, Z=-510000 and refreshed the streaming selection after their positions settled. The game selected region 557 in group A. Visible geometry includes a paved course, cones/markers and surrounding buildings. This confirms group A can load in the running game using the exploration tools; it does not yet establish whether normal missions use it. The pre-visit recovery is before-visit-A.state; the loaded-area checkpoint is at-A.state. Screenshot: candidate-A-first-visit.png.

Candidate B visited on 18 November 2026: camera target X=695000, Z=-660400; selected region 559. Visible layout resembles A's paved course and surrounding buildings, with different foreground course markings. Exact differences and mission usage remain unverified. Checkpoint: at-B.state.

Candidate E visited on 18 November 2026: target X=337920, Z=205000; stationary streaming rescan selected region 373 (STR_J_BOMB group). Building/street geometry became visible. Some previous course geometry remained visible during the transition, so the scene needs further inspection before attributing every object to E. Checkpoint: at-E.state.

Candidate F visited on 18 November 2026: target X=7168, Z=140000; streaming selected region 244 (STR_G214). Visible scene includes a tall stair/ramp structure between buildings. Checkpoint: at-F.state. The purpose and normal accessibility remain unverified.

Candidate D visited on 18 November 2026: target X=-356000, Z=540000; streaming selected region 83. Road/bridge-like geometry is visible; some prior geometry can persist during cross-group transitions, so individual objects are not yet conclusively attributed. Checkpoint: at-D.state.

Candidate C visited on 18 November 2026: target X=695000, Z=-810800; streaming selected region 561. Paved course-like geometry with curved white markings, vegetation and structures became visible. Checkpoint: at-C.state. Normal mission usage remains unverified.
