- Newest
- Most votes
- Most comments
Hi IngDanko,
Sorry for the late reply, this seems to be a very specific use case since we have other users being able to bundle dlls in their build and access them successfully. Could you please reach out to AWS support so they can help facilitate more personalized support?
You also have sudo access to the gamelift instance, could you possibly debug your game server directly on the instance? (e.g. try changing file/directory permissions, try relocating the file, etc.)
Thanks,
James
I have a completely identical problem. How can I solve this problem?
Hi,
As I mentioned in the comment on the previous answer, my team didn't really fix it but we found a workaround - host the server on Linux EC2 instances instead of Windows.
The issue only seems to happen on windows VMs running GameLift. Linux VMs work fine, and our Unity-based server worked with a Linux build without any adjustments. So my suggestion is: make a Linux build of your server and see if that works.
Relevant content
- asked 5 years ago
- Accepted Answerasked 2 days ago
- Accepted Answerasked 10 months ago
- AWS OFFICIALUpdated 2 months ago
Hi James. We switched to Linux servers and the build works fine there. It also works on an unmanaged Windows EC2 instance with the same OS and instance type.
The problem only occurs on a GameLift-managed Windows instance, and only for .dlls that need to be loaded in runtime.
We have moved to using Linux instances for our use case (since that approach has no real downsides for us) but maybe this info is useful for your team to track down the issue.
Best regards, Danko