Repository navigation
v1.6.7 - Fix phantom extra digit from card art
Fix: phantom extra digit from card art (e.g. 768 damage logged as 7,687)
Each player card's character art sits to the right of the stat column and can reach into the damage and Kills / Assists / Knocks boxes. When the art has a bright vertical edge there, OCR reads it as an extra trailing digit: 768 → 7687 damage, 1 → 11 knocks. The old white-pixel filter couldn't remove art that is itself bright, and the K/A/Kn line had no filter at all.
- Before reading damage and K/A/Kn, the tracker now cuts the box at the first wide empty gap after the number. Values are left-aligned with at most ~9px between characters at 1080p, and the art starts 44px or more past the text (measured on 7 real summary screens), so the cut sits at 20px (scaled to your resolution).
- If there's no such gap, the box is read exactly as before. Worst case is no change, never a clipped digit.
- Verified by painting an art-like vertical stroke ~50px past the text on a real summary: the old reader produced
2,616→26161and2/5/2→2/5/21, and the new one reads every value correctly. All reference screenshots still read 100%. - No frame of an actual bad read was available, so this fixes the mechanism the code already documented rather than replaying a captured failure.
- New
test_trim_trailing_art.py(source only).
Update
Use the in-app update, or download ApexTracker_share.zip, close the tracker, and replace the program files. Keep your existing config.json and .env.