GitHub/Facepunch.Steamworks
2
0
Fork 0
mirror of https://github.com/Facepunch/Facepunch.Steamworks.git synced 2024-12-27 23:25:55 +03:00
Code Issues Projects Releases Wiki Activity

Use CreateInterface instead of FindOrCreateUserInterface

Browse Source
This commit is contained in:
Garry Newman 2019-05-14 10:23:43 +01:00
parent d671c1ddc8
commit a2942bd098
1 changed files with 17 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
Facepunch.Steamworks/Utility/SteamInterface.cs
View File

@ -35,8 +35,23 @@ public void Init()
public void InitClient() public void InitClient()
{ {
var user = SteamAPI.GetHSteamUser();
Self = SteamInternal.FindOrCreateUserInterface( user, InterfaceName ); //
// There's an issue for us using FindOrCreateUserInterface on Rust.
// We have a different appid for our staging branch, but we use Rust's
// appid so we can still test with the live data/setup. The issue is
// if we run the staging branch and get interfaces using FindOrCreate
// then some callbacks don't work. I assume this is because these interfaces
// have already been initialized using the old appid pipe, but since I
// can't see inside Steam this is just a gut feeling. Either way using
// CreateInterface doesn't seem to have caused any fires, so we'll just use that.
//
// var user = SteamAPI.GetHSteamUser();
// var pipe = SteamAPI.GetHSteamPipe();
// Self = SteamInternal.FindOrCreateUserInterface( user, InterfaceName );
Self = SteamInternal.CreateInterface( InterfaceName );
if ( Self == IntPtr.Zero ) if ( Self == IntPtr.Zero )
throw new System.Exception( $"Couldn't find interface {InterfaceName}" ); throw new System.Exception( $"Couldn't find interface {InterfaceName}" );