Steamwork.net builds packages that will call the Steam client and then flash back

[zzr767299]

I'm having a weird problem with Steamwork.net. After Steamwork.net runs a package built in Unity, it will call the Steam client. When Steamwork.net starts, my game will flash back. The steam. App TXT is correctly set to the Steam application ID, but no matter what method I use, I will always flash back after running the Steam client. I hope you can help me when you see it, thank you very much!

[rlabrecque]

Hey @zzr767299, can you clarify what you mean by "flash back"? If you run your game with your AppId set in RestartAppIfNecessary, it will enqueue your game to be launched directly from the Steam Client. That may not be the same executable you are launching though.

[zzr767299]

Thank you very much for your reply. Flash back means Game Forced to terminate. My Game has not been released yet. When I load Steamworks.Net and package it, what I want is to launch the project file directly, then launch the Steam client, and then launch the local project file again. Instead of starting the Steam project, because I haven't released it yet and it hasn't been approved yet. I don't know if it was my mistake. Looking forward to your reply