When ModUpdateNotifier launches Satisfactory Mod Manager, Steam believes the game is still running #3
Description
Operating System
Windows 10/11
Environment
Single Player
Game Version
Stable
SML Version
3.11.3
Mod Version
2.4.4
Describe the bug
When ModUpdateNotifier launches Satisfactory Mod Manager, Steam believes the game is still running because the Mod Manager was launched as a subprocess of Satisfactory. The game cannot then be launched from the Mod Manager after updating mods, as Steam will say the game is already running. The Mod Manager must be closed, at which point Steam registers Satisfactory as no longer running; then Satisfactory can be launched either through Steam or by launching the Mod Manager again.
Expected Behavior
ModUpdateNotifier should launch the Satisfactory Mod Manager in such a way that Steam will not show Satisfactory as still running. There might be a Steamworks API call that can tell Steam the game is no longer running (does SteamAPI_Shutdown() get called when your mod launches the Mod Manager?) or changing the way the subprocess is created to decouple it from the parent process.
This might also just not be possible at all.
Attachments
No response