(Unity, Windows) NULL EOS Platform returned by native code: issue probably occurred in GFX Plugin!

We’ve recently upgraded our Unity EOS SDK from v3.3.3 to v4.0.0, and getting the above exception on launch on our Windows builds. From what I can tell, `GfxPluginNativeRender-x64.dll` is failing to load, but I’m not sure why. The C# code related to loading the dll seems to be the same across versions, and the import settings for the three dlls (`DynamicLibraryLoaderHelper-x64.dll`, `GfxPluginNativeRender-x64.dll` and `EOSSDK-Win64-Shipping.dll`) are the same in Unity across versions.

Taking a closer look look at `DynamicLibraryLoaderHelper-x64.dll`, `GfxPluginNativeRender-x64.dll` using `objdump`, it looks like the versions from the v3.3.3 Release are compiled to dynamically link with MSVCP140.dll, which makes sense because as far as I’m aware, games on epic require clients to have installed the latest MSVC runtime libraries. The newer versions of these dlls do not depend on MSVCP140.dll, however, which is making me suspicious and could perhaps point to the problem? I’ve attached the objdump reports for GfxPluginNativeRender-x64.dll.

Has anyone run into this issue? Maybe I’m barking up the wrong tree and the solution is simpler, but the error does just indicate that the function `EOS_GetPlatformInterface()` exported by `GfxPluginNativeRender-x64.dll` returns a null pointer, so I’m not sure where else to look.

Thanks,

Joe

068QP00000d7NuJYAU.txt (9.83 KB)
068QP00000d7hubYAA.txt (5.94 KB)

Found the issue here. It turned out that having an empty Encryption Key in our Windows Config was the problem. We had:

"EncryptionKey": ""

Where the examples in the SDK had:

"EncryptionKey": "1111111111111111111111111111111111111111111111111111111111111111"

Even though that’s still an invalid key, the SDK is a lot happier with that.

I couldn’t actually see what the encryption key is for, or that it’s being used at all - is it a hang-up from an older version of the SDK?

Hi Joe,

Thanks for reporting this issue and I’m glad you found a fix. We will investigate this encryptionkey value and work on making improvements in the future.

-Jeff