Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CallbackType not in sdk #507

Open
dustingraham opened this issue Dec 6, 2020 · 6 comments
Open

CallbackType not in sdk #507

dustingraham opened this issue Dec 6, 2020 · 6 comments
Assignees

Comments

@dustingraham
Copy link

Describe the bug
Integrating with unity, using Dispatch.OnDebugCallback receiving "not in sdk" messages.

To Reproduce
Steps to reproduce the behavior:

  1. Dispatch.OnDebugCallback = (type, str, server) =>Debug.Log(str);
  2. SteamClient.Init(gameId);
  3. Observe callback messages.
[715 not in sdk]
[711 not in sdk]

Expected behavior
Expected a known CallbackType like: [Callback UserStatsReceived client]

Desktop (please complete the following information):

  • OS: Windows 10 64-b0t
  • Unity: [e.g Unity 2020.1.16f1]
@uladzislaubasin
Copy link

@dustingraham have you found the solution?

@dustingraham
Copy link
Author

@uladzislaubasin this is simply a report of some values that don't have a definition in facepunch yet. I think you can find what those values are in steam's API. I just ignored them.

@sarahnorthway
Copy link

I'm getting [1040015 not in sdk] when my game gains or loses focus, and [1040011 not in sdk] regularly for unknown reasons. I couldn't find anything like a code lookup in Steam's API and these seem way out of range of the other IDs.

It would be good to know what these messages were trying to say for debugging purposes, but they do seem unimportant.

@marcospgp
Copy link

marcospgp commented Oct 19, 2023

I'm getting [1040015 not in sdk] when my game gains or loses focus, and [1040011 not in sdk] regularly for unknown reasons. I couldn't find anything like a code lookup in Steam's API and these seem way out of range of the other IDs.

It would be good to know what these messages were trying to say for debugging purposes, but they do seem unimportant.

Can't believe I found this, I'm getting these weird callback IDs too on my custom Steamworks wrapper and thought I must have done something wrong. Some other callbacks are as expected, so the code wasn't entirely broken somehow.

Did you find out anything about these mysterious callback IDs in the meantime? I see quite a few, such as

'1040044'
'1280006'
'1040015'

Edit: I also get unexpected SteamAPICallCompleted_t callbacks even when no async API call had been made. The callback ID I'm seeing for that API call's m_iCallback is "1296", which also does not appear to be part of the callback enum.

Edit: Not ignoring these API calls with unrecognized m_iCallback IDs (proceeding with SteamAPI_ManualDispatch_GetAPICallResult) was causing crashes with seemingly random stack traces in the Unity editor log

@NBG-Zorian
Copy link

@marcospgp
Edit: Not ignoring these API calls with unrecognized m_iCallback IDs (proceeding with SteamAPI_ManualDispatch_GetAPICallResult) was causing crashes with seemingly random stack traces in the Unity editor log

What do you mean not ignoring? Do you need to somehow unregister from these callbacks? How can I ignore them without just checking for "not in sdk" substring?

@marcospgp
Copy link

@NBG-Zorian According to what I wrote there, not ignoring = proceeding with SteamAPI_ManualDispatch_GetAPICallResult. So if you don't call that you are effectively ignoring the API call, you don't have to actively ignore it by doing something no. Cheers!

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

No branches or pull requests

6 participants