Repository navigation
v1.6.4 - consistent RP + reliability fixes
v1.6.4 — consistent RP + reliability fixes
Fixes the two things that made RP look/feel unreliable, plus two capture/log
issues found in the debug logs.
RP now reads correctly
starting_rpreflects the real baseline. When the tracker corrects a stale
snapshot (a squadmate's RP posts before the summary is read), it now writes the
corrected start value too — so a resolved game never shows the confusing
"start == end but +362 change" anymore. The change was always right; the start
column was stale. It's consistent now.
Faster, finer, quieter
- Poll interval auto-bumps 120s → 30s on older installs. Updates keep your
config.json, so setups from before v1.6 were still polling every 2 minutes —
too coarse, so back-to-back games' RP piled into one reading. 30s catches
results as they settle. (Only the old default is changed; a custom value is
kept. You can also set it in Settings → ALS poll interval.) - OBS Virtual Camera recovers ~5x faster from a stalled feed (~8–12s instead
of ~60s). A feed stall landing on a summary was dropping whole games; this
catches the summary while it's still on screen. - Stopped a debug-log quirk that wrote a bogus "session start" line every RP
sweep (made normal runs look like constant restarts).
No changes to detection, OCR, capture modes, or match logging.
Update
Click Update now in the app, or download ApexTracker_share.zip, unzip,
run Start Tracker.bat. Settings + history kept.