A game started directly ends its session at once when it relaunches itself through Steam #74
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#74
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?
Seen on 0.9.4 (Windows): Control: Resonant (Steam app 3669870), launch method "exe" with
CONTROLResonant.exeand process nameCONTROLResonant.exe. Right after Play, before the game finished starting, SavePoint showed "You played for 1 second" and asked to keep the session; the game then came up.Likely cause: a Steam game started directly often exits at once and has Steam start it again (Steamworks restart), so the program SavePoint started ends while the real game process, with the same name, appears a moment later. With a process name set, the session should keep waiting for that name (D13.10's grace, two minutes since D48.7) instead of ending when the first process exits. Confirm against the app's log for that launch before fixing.
Done when a game whose started program exits and comes back under the same name (or a named child) keeps its session until the named process ends, covered by tests with a stand-in program that relaunches itself, and checked with a real launch.