I'm not sure how GameLift works with Linux servers on EC2 instances, but I have noticed that if I don't connect to the server for a while, I get errors trying to start my game session. The project is a multi-user VR meeting room experience, and it is obvious when things have not appropriately connected because it launches the session incorrectly and the users can't move around. It seems the Player Session is not activated. This ONLY happens after a long period of inactivity and corrects itself a little while later.
The code in the project is probably not waiting for the server to spin up, but I do feel that this time period is way too long. Sometimes you'll need to wait for 20 minutes before it starts to work again.
Am I correct in assuming this is a 'cold start' issue with GameLift on-demand fleet instances?
The weird thing is that I wouldn't expect the Game Session to be created at all if the server wasn't running, but I can't think of another reason why this is happening. Maybe it is more to do with authentication and the GameLift SDK?
