Add live GPS momentum weights
This commit is contained in:
@@ -2,6 +2,32 @@
|
||||
|
||||
Current date/time context: 2026-06-27, local timezone America/Chicago.
|
||||
|
||||
## 2026-06-27 Live Momentum Knob Installed
|
||||
|
||||
- Installed a new telemetry/control DLL at about `03:21` local while the game was
|
||||
cold. Installed size: `16899519` bytes.
|
||||
- Active installed config:
|
||||
`solver_weights.bin = 1.0` and `momentum_weights.bin = 8.0`.
|
||||
- The plugin log beside the DLL was truncated to zero after install:
|
||||
`red4ext/plugins/EdgeWeightGPS/EdgeWeightGPS.log`.
|
||||
- `momentum_weights.bin` is one little-endian `float32`, hot-polled every
|
||||
500 ms. `0.0` disables the fixed ordinary-edge penalty; `8.0` is the current
|
||||
prototype; larger values are stress tests. Presets are in
|
||||
`presets/momentum/` and can be written live with
|
||||
`python3 tools/write_momentum_weights.py <preset>`.
|
||||
- New presets:
|
||||
`vanilla=0.0`, `mild=4.0`, `default=8.0`, `strong=16.0`,
|
||||
`silly=80.0`, `pathological=250.0`.
|
||||
- The `gps-momentum-summary` line now waits for a nonzero result route-record
|
||||
count before marking a query as summarized. It should report
|
||||
`gpsResultRouteCount` directly instead of showing `0` from the staging fetch.
|
||||
- Build verification passed:
|
||||
`toolbox run -c 2077 ./tools/build_red4ext_shim.sh`.
|
||||
- Next test should start with current `momentum=8.0`, then while the game is
|
||||
open switch to `vanilla` and `silly` on one or two fixed routes to confirm
|
||||
live A/B behavior. Good candidates from the last run: The Damned/Dogtown
|
||||
pathological route and the SW Badlands fuel station route.
|
||||
|
||||
## 2026-06-27 Momentum Telemetry Test Installed
|
||||
|
||||
- Installed telemetry DLL at about `03:04` local while the game was cold.
|
||||
|
||||
Reference in New Issue
Block a user