|
|
| Reporter | Dan | Assigned To | Russell Kay | |
|---|
| Priority | Medium | Severity | C - General | Reproducibility | 100% |
|---|
| Status | Resolved | Resolution | No Change Required | |
|---|
| Platform | Windows VM | OS | Windows 10 | OS Version | Pro x64 |
|---|
| Product Version | 2.2.2 | |
|---|
| Target Version | | Fixed in Version | | |
|---|
|
|
| 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 | |
|---|
|
|