1 Answers
0
Hello there -
GameLift expects whichever process has been integrated with the GameLift Server SDK to be the same process that calls InitSDK() and ProcessReady(). In other words, whichever process you specify in your Fleet's Runtime Configuration (eg. C:\game\server.exe), that executable needs to be the one that is integrated with the GameLift Server SDK and communicates back to GameLift via the InitSDK() method, otherwise registration of your game server process will timeout and the error message you describe above will be shown.
Does this help?
answered 5 years ago
Relevant questions
Is there a way to modify the existing server executable files in a running fleet?
Accepted Answerasked 2 years agoServer process run through command do not persist in my Amazon Lightsail Instance
asked 5 months agoHow can I increase the number of devices that you can include in a test run in DeviceFarm?
Accepted Answerasked 3 months agoTime frame for fleet instance to be freed after termination
asked a year agoCan I extract the code from the aws to save it in Github?
asked a month agoI am not able to stop or terminate the server
asked 2 months agoElastic Beanstalk doesn't run commands in the background
asked 3 years agoIs it possible to schedule the number of instances in a fleet?
asked a year agoServer process started correctly but did not call InitSDK() or ProcessReady() within 5 minutes.
asked 2 months agoCan not you call SDKInit () in a background process?
asked 5 years ago