Skip to content

Conversation

@kasimir-spellgarden
Copy link

The new InitEx method is awesome and provides much more data if something breaks. I've changed the method slightly to expose the underlying error that the Steam SDK produces instead of the generic Steamworks.NET error message.

initResult = ESteamAPIInitResult.k_ESteamAPIInitResult_FailedGeneric;
OutSteamErrMsg = "[Steamworks.NET] Failed to initialize CSteamAPIContext";
if(!string.IsNullOrEmpty(OutSteamErrMsg))
OutSteamErrMsg = $"[Steamworks.NET] Failed to initialize CSteamAPIContext: {OutSteamErrMsg}";
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can this ever get hit? If OutSteamErrMsg is not empty, does that not also mean we'll never get into the branch at L256?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants