[4.8.3] Shipping build with steam
We have a problem when packaging a project with the Project Launcher and doing a shipping build, the steam api doesn't seem to fire.
Took a look at a past issue and attempted to make the changes outlined in there with the steam_appid.txt in the root folder, but that did not help either.
When running the game in stand-alone, steam overlay shows up and the API fires properly. Shipping on the other hand does not.
Tried to reproduce this in a blank project, sure enough it also doesn't work.
Blank Project has everything setup to work with steam, along with the steam_appid.txt in the staged folder.
Can you let us know why this blank project also does not trigger the steam overlay?
(Process used to create the shipping build)
It appears this is simply a bug. We're aware of this behavior on the Mac, but I did not know it also happened on the PC. I've created a bug report for the issue (UE-23238), and I'll post here if I see any update on it.
For now, with the project you gave me to look over, as well as projects I created here, as long as you open the .exe through the Steam client, the overlay should appear as expected.
I'm not certain why you needed to add SteamAppId to the DefaultEngine.ini to get it working. Neither should make any difference in a shipping build, and I was able to get this working through the Steam client without that, and without the steam_appid.txt file. Incidentally, the steam_appid.txt is a development only thing. Once you are properly uploaded and instrumenting your builds with Valve and launch from the Steam client, you won't need that text file unless you're distributing dedicated server executables: https://partner.steamgames.com/documentation/dedicated_servers
answered Nov 11 '15 at 09:16 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here