[Error] "Steaminternal_contextinit could not be located" when executing game.exe

[shinichishiruo]

After the last update, when I run the game.exe of a newly published project, I get an error stating that "steaminternal_contextinit could not be located in the dynamic link library"

I also got a similar error at first about missing "steam_api.dll" but that one was easy to fix.

Am I the only one with this problems?

I thought that, once published, games were not related to steam. The previous version of this same game still runs without problem.

Already uninstaled and reinstaled SRPG Studio two times and didn't fix it.

I know it's not a problem with the game files since I got the same error with a new project and with the sample game.

[SapphireSoft]

This error is a serious problem.
Please wait while we investigate.

[SapphireSoft]

What we have done with this update is use the latest SteamSDK. This is beneficial as it allows you to use new Steam features in your game engine.

However, after updating to the new SDK, two strange things seem to have occurred.

1:
It seems like steam_api.dll is always required when a game is released. This means that even if you don't intend to distribute your game to Steam, you must include steam_api.dll in your game folder. This is puzzling, but for now we have fixed it to always include steam_api.dll.

2:
We haven't encountered any steaminternal_contextinit errors so far. We were able to launch the game without issue if we placed steam_api.dll in the same directory as game.exe. However, when I placed the "old" steam_api.dll, an error "SteamInternal_SteamAPI_init" occurred. This error is an important hint to resolve "contextinit error".


Game.exe is now generated using the new SDK, so of course the Steam logic in game.exe expects the "new" steam_api.dll. In other words, the new dll thinks there is a function inside the dll called SteamInternal_SteamAPI_init. However, the old steam_api.dll does not have this function, so I think there is an error.

The lesson here is that the exe and steam_api.dl must always be compatible. We have just updated to the latest version. Try releasing the game again. The game folder includes steam_api.dll, which probably prevents the steaminternal_contextinit error from occurring.

[shinichishiruo]

Originally posted by SapphireSoft:

What we have done with this update is use the latest SteamSDK. This is beneficial as it allows you to use new Steam features in your game engine.

However, after updating to the new SDK, two strange things seem to have occurred.

1:
It seems like steam_api.dll is always required when a game is released. This means that even if you don't intend to distribute your game to Steam, you must include steam_api.dll in your game folder. This is puzzling, but for now we have fixed it to always include steam_api.dll.

2:
We haven't encountered any steaminternal_contextinit errors so far. We were able to launch the game without issue if we placed steam_api.dll in the same directory as game.exe. However, when I placed the "old" steam_api.dll, an error "SteamInternal_SteamAPI_init" occurred. This error is an important hint to resolve "contextinit error".


Game.exe is now generated using the new SDK, so of course the Steam logic in game.exe expects the "new" steam_api.dll. In other words, the new dll thinks there is a function inside the dll called SteamInternal_SteamAPI_init. However, the old steam_api.dll does not have this function, so I think there is an error.

The lesson here is that the exe and steam_api.dl must always be compatible. We have just updated to the latest version. Try releasing the game again. The game folder includes steam_api.dll, which probably prevents the steaminternal_contextinit error from occurring.

It is working fine again. Thanks for your help.