Hi. thanks for finding this workaround. Looks like it solved it for me too.
I’m developing a multiplayer game for HTC Vive. My colleagues and I often face one very annoying issue: in development build Steam can stop initializing correctly after few launches.
LogOnline:Display: STEAM: Loading Steam SDK 1.32 LogOnline:Warning: STEAM: Failed to initialize Steam, this could be due to a Steam server and client running on the same machine. Try running with -NOSTEAM on the cmdline to disable. LogOnline:Display: STEAM: OnlineSubsystemSteam::Shutdown() LogOnline:Warning: STEAM: Steam API failed to initialize! LogOnline:Display: STEAM: OnlineSubsystemSteam::Shutdown()
Players with “broken” steam can’t find hosted games and their sessions are invisible to other players. To fix the error I need to reboot steam and sometimes reboot VR headset via Steam VR menu. If it doesn’t help and Steam still has init errors, only PC reboot helps.
It’s strange, but this bug reproduces after a few launches only if I run built game in VR mode (Vive connected to PC). If I disconnect Vive and run game in PC mode, everything is fine, Steam inits correcly after 10 and more launches.
Network part of my DefaultEngine.ini :
[/Script/Engine.NetworkSettings] n.VerifyPeer=False [OnlineSubsystem] DefaultPlatformService=Steam PollingIntervalInMs=20 bHasVoiceEnabled=true [OnlineSubsystemSteam] bEnabled=true SteamDevAppId=480 SteamAppId=480 GameServerQueryPort=27015 bRelaunchInSteam=false GameVersion=126.96.36.199 bVACEnabled=1 bAllowP2PPacketRelay=true P2PConnectionTimeout=90 [/Script/OnlineSubsystemUtils.IpNetDriver] InitialConnectTimeout=60.0 ConnectionTimeout=60.0 [/Script/OnlineSubsystemSteam.SteamNetDriver] NetConnectionClassName="OnlineSubsystemSteam.SteamNetConnection" ; Network limitation MaxClientRate=100000 MaxInternetClientRate=100000
Fixed by turning off Steam VR Home Beta in Steam VR settings
Hi guys. This is a workaround that is OK only during development. But you can’t possibly ask your users to turn of Steam VR Home before starting your game.
This issue is still happening in 4.16. Here is another discussion about this issue on Steam forums:
I’m going to open another thread to get a bug entered in the bug database.