salt/2077-gps-mod
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Document spatial cost inversion result

Browse Source
This commit is contained in:
Salt
2026-06-26 22:24:10 -05:00
parent dd1423b693
commit 690feb8684
5 changed files with 469 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/traffic-system-debrief.md
+17 -2
View File
@@ -861,20 +861,35 @@ Runtime logs also show that long visible routes are decomposed into many local
logs, so the first spatial test should patch edge cost across route-producer
calls instead of gating only on that caller.
The spatial edge-cost prototype is now also disproved as the decisive
world-map GPS weighting surface. In
`logs/EdgeWeightGPS_spatial_inversion_no_route_change_1845.log`, the plugin
first ran with highway-free weights (`H=0.05`, all other spatial classes
`19.0`), then hot-reloaded the exact inverse (`H=19.0`, all others `0.05`).
The four repeated world-map routes after the flip produced final
`GPSQueryResultFetch 0x7094b8` 0x28-byte route records that were exact matches
for the pre-flip routes: identical lane handles, identical packed metadata, and
identical record counts. Therefore `0x44f838` remains a real local graph edge
cost callback, but changing it does not change the final selected route records
for the tested full player GPS routes.
## Future Improvements
Better versions of this mod could:
- identify the broader async traffic route search/expansion loop around the
`0x8d25xx` to `0x8d49xx` cluster
- disassemble the full map-route submit/result chain around `0x8d20d4`,
`0x70a42c`, `0x70a570`, `0x7094b8`, and the `0x520783` result drain to find
the route selection or copy step before final records are emitted
- replace the crashing `0x8d46cc` detour with a narrower inline patch or a
safer caller-side hook
- decode enough of the `VAND` graph to join navigation points to traffic lane
polygons and highway flags
- extract the full Night City navigation streamingsector set into workspace
storage and summarize it with `tools/analyze_vand_navigation.py`
- tune the generated spatial grid resolution and multipliers after in-game A/B
tests
- keep the generated spatial grid as a local-search diagnostic, but do not
treat its multipliers as a proven world-map route weighting knob
- add route-mode gating if the spatial edge-cost hook affects pedestrians,
autodrive, or other local navigation too broadly
- inspect `GPSOnly` connector lanes if a later native trace proves they are