If you look closely at the the above path, it says Steamv137 instead of Steamv132. Is this going to be a problem? Or should I definitely be using the v132 DLLs instead?
I made a project on my end using 4.13 and all I had to do to use the Steam SDK was go to the plugins window in the editor and turn it on with the check box and add the following the project DefaultEngine.ini:
Are the lines added to my source code needed anymore for steam when activating the plugin?
I have bUsesSteam = true; in my *.target.cs files
and
DynamicallyLoadedModuleNames.Add(“OnlineSubsystemSteam”); in my *.build.cs file
Add the following to DefaultEngine.ini
`[/Script/Engine.GameEngine]
+NetDriverDefinitions=(DefName=“GameNetDriver”,DriverClassName=“OnlineSubsystemSteam.SteamNetDriver”,DriverClassNameFallback=“OnlineSubsystemUtils.IpNetDriver”)
I have just enabled STEAMWORKS in 4.13 by downloading latest sdk 137
//STEP 1
, created folders in root of you project folder — > Engine/Binaries/ThirdParty/SteamWorks/Steamv137/Win32
Engine/Binaries/ThirdParty/SteamWorks/Steamv137/Win64
then go to programFiles(x86) and copy steamclient.dll, tier0_s.dll ,vstdlib_s.dll to Win32 Folder and steam_api64.dll, steamclient64.dll, tier0_s64.dll to Win64 Folder ,
than go to your downloaded SDK and find steam_api.dll and steam_api64.dll and copy to folders WIN32 & WIN64 too
//STEP2
///////////////////////////////////////////////////////
in Defaultengine.ini copy →