-
-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
CSDM force-quits Steam when running games on another computer #996
Comments
Unfortunately, it looks like it's not possible to know if a Steam account is in-game before initializing a connection with the Steamworks API used to retrieve last matches. (tested with https://github.com/akiver/boiler-writter used by CS:DM) Notes:
If someone finds a way to do it, please bump this issue. Please understand that it's an edge case and the best thing ATM is to improve the error message which is done in 097fa6b |
I also added a doc about it https://cs-demo-manager.com/docs/guides/downloads#steam-is-closing-when-i-refresh-my-last-matches |
Describe the bug
When running a game via Steam on another computer (computer1), and trying to download Valve demos via CSDM on computer2, then Steam would force-quit on computer2 and no information/error message is given to the user. This happened to me when ArchiSteamFarm (ASF) was unknowingly running games in the background.
The behavior described above can be seen in the following video:
https://github.com/user-attachments/assets/5bdf204d-83d7-4d50-98bb-3f6ebb78b2e0
Demo links
No response
Steps to reproduce
Expected behavior
I would expect the demo download to be unsuccessful, but I don't want Steam to force-quit on computer2, and I'd also want CSDM to show an error message like:
A Steam game is currently running on another computer. Please exit the game on that computer before trying to download Valve demos.
In the current implementation Steam just force-quits, and no information/error message is given by the CSDM application.
How often does this bug happen?
Every time
Log file
Environment information
Additional context
No response
The text was updated successfully, but these errors were encountered: