View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0031167 | Runner | Steam | Public | 2019-07-11 15:45 | 2019-08-30 11:43 |
Reporter | Dan | Assigned To | Russell Kay | ||
Priority | Medium | Severity | C - General | Reproducibility | 100% |
Status | Closed | Resolution | Duplicate | ||
Platform | Windows VM | OS | Windows 10 | OS Version | Pro x64 |
Product Version | 2.2.2 | ||||
Target Version | 2.2.4 | Fixed in Version | 2.2.4 | ||
Summary | 0031167: Steam: Third-party "Steamworks_gml" extension no longer works for VM, only YYC | ||||
Description | We now have a couple of reports asking why a third-party "Steamworks_gml" extension no longer works for Windows VM, only YYC. This looks like a 1.4 extension which is still in popular use today. Currently, the belief is that the VM runner is linked using a different version of VC++ runtime to what the dll is expecting, whereas YYC will link it using whichever VC++ runtime is on the dev's machine during the build process. The source for this extension can also be found at https://github.com/Stormchaser2018/steamworks.gml | ||||
Steps To Reproduce | 1. Make sure you have the Steamworks SDK installed, etc. 2. Run the attached project for Windows VM 3. You will see in-game text that the extension failed to load and in your output window you will have the line "LoadLibraryA failed with error code 127". 4. Run it for YYC instead and observe all works. Repro: 100% | ||||
Tags | No tags attached. | ||||
1.4 Found In | |||||
2.x Runtime Found In | 2.2.2.326 | ||||
2.x Runtime Verified In | |||||
duplicate of | 0031203 | Closed | Russell Kay | Steam: We ship steam_api.dll v1.35 as part of the Windows runtime, incorrectly use this when building for VM |
|
Steam_extension.yyz (60,746 bytes) |
|
https://stackoverflow.com/questions/14361992/dll-load-library-error-code-126 is a good place to start it looks like it is looking for the steam_api.dll file and not finding it (looking at a Process Monitor trace of the failing VM version) it is also looking for an rpcss.dll which it is failing to find. YYC is also failing on my setup so I suspect an issue with the actual DLL |
|
I don't think this is our problem |
|
Closing as per the above comment. Note also that we *have* made a change for 2.2.4 which will ensure that the correct Steamworks dll is being used on VM, which may also fix this if it was on us. |
|
Indeed, that was due to https://bugs.yoyogames.com/view.php?id=31203 - while the original build of the extension used 1.35a (and continued to function as normal), issue author compiled it against 1.42 (as GMS2 doc suggested), which broke because VM would use 1.35a instead of the DLL from specified SDK. |