- Newest
- Most votes
- Most comments
Hey Andre,
[Is there] a way to get more detailed logs about what is happening or, at least, check if the server parameter values are being set correctly?
PS. I can't look for the GameSession logs since the fleet activation fails before the creation of any game session.
You can follow this link to Remotely access Amazon GameLift fleet instances to access all logs directly from the host.
Additionally, you can follow this blog post on Unreal Engine 5 dedicated server development with Amazon GameLift Anywhere for insight into using GameLift Anywhere to test your builds on your local machine and rapidly resolve issues before deploying to a Managed EC2 fleet.
Regards,
I tested my dedicated server on Anywhere fleet using my laptop. In the result, Server works fine without any errors. InitSDK and ProccessReady run almost fast. Why do EC2 fleet get failure while try to do initSDK ? so the fleet is going to be not activated.
Hey Monster,
Here’s a list of steps for migrating to SDK 5.0 to check against for your game server: https://docs.aws.amazon.com/gamelift/latest/developerguide/reference-serversdk.html#fleet-anywhere-sdk.
Since your game server is working with Anywhere but not Managed EC2, I recommend verifying that you provided a ServerSDKVersion greater than 5.0.0 when creating your Build resource. ServerSDKVersion defaults to 4.0.2 and won’t be able to go active with the newer SDK versions. https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-gamelift-build.html#cfn-gamelift-build-serversdkversion
In my case, I solved it as follows.
After the unreal server build, upload the build by including "libcrypto-3-x64.dll", "libssl-3-x64.dll" in the "GameLift_UE5\Binaries\Win64" folder to activate the fleet normally. The file exists in the folder that was installed when openssl was installed.
Relevant content
- asked 4 months ago
- asked 9 months ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 2 years ago
I have same problem. I use same thing for server parameters. The fleet always tell "SERVER_PROCESS_SDK_INITIALIZATION_TIMEOUT - The server process did not call InitSDK() within the time expected. Check your game session log to see why InitSDK() was not called in time". Then the fleet is not activated. I'm get some confused difference between what AWS SDK 5.x document says and actually SDK source for FProcessParameters. The api has new OnRefreshConnection callback rather than old 3.x . The document describe OnRefreshConnection with Required 'Yes' but I can't see that in the latest c++ SDK source. Is there no problem?