Are people still using Steamv132 or have people moved to current Steamv137?

Development Programming & Scripting Blueprint
1

I got Steamv137 working in the editor when launching a stand alone game using this guide: http://allarsblog.com/2016/02/29/UpdatingSteamSDK/#steamcontrollercpp . However the development package doesn’t contain the steam overlay. Per the normal response to this problem, I have moved the steam_appid.txt file and steam_api64.dll to both the packaged project root folder and project/binaries/64 folder but the steam overlay is still absent.

I am now wondering if I should have just left the older Steamv132 folder alone (that comes with the UE4 GitHub build), by the sound of it most people are still using that with success. Can anyone confirm that the 132 version works or confirm that the 137 version also works and I am making some other error?

Thanks

2

132 worked just fine for me. Didn’t even have to mess with the folders. If you are messing with blueprints though no matter what version you use very little of the steam api is exposed to blueprints. Just creating, finding and joining sessions. Everything else has to be done in C++ and some folks have mentioned issues there as well.

I have a post in the feature request section about getting more of the steam api exposed to blueprints if you want to add your voice to that conversation. More Of Steam's API Exposed To Blueprints - Feedback & Requests - Epic Developer Community Forums

3

I just this weekend released Steam keys to beta testers that were built using Steamworks v138 and Unreal 4.13.1. All confirmed working, including the steam overlay, achievements, cloud saves, etc.

4

Steam version used is hardcoded in the Engine.