SavePoint does not notice a Steam game quit after starting it through Start Steam #255
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
ethan-hann/SavePoint#255
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Found testing 0.9.20 with Balatro (Steam library install, Run the .exe, process name Balatro.exe). With Steam closed, Play showed the "Steam needs to be running" card; Start Steam started Steam and then the game, which ran fine. When the game was quit, SavePoint did not notice, and the session only ended with "I'm done".
The log shows the session ending as ManuallyFinished with "started pid 13264, followed pids none" after 31 s. An earlier session the same minute (launch 0.2 s) also ended ManuallyFinished with no followed pids, so check whether exit detection works for this game on the plain path too.
Expected: when the game exits on its own, SavePoint detects it and shows the after-play choices, whichever way the launch started Steam (D67).
The fix shipped in 0.9.21 (https://git.tortal.tech/ethan-hann/SavePoint/releases/tag/v0.9.21): a clean quit (exit code 0) after at least 10 seconds of play now ends the session about 4 seconds later instead of after the 2-minute grace (D13.10). Keeping this open until Balatro is retested through Start Steam; #256 covers real store relaunches.