4 Answers
- Newest
- Most votes
- Most comments
0
Update, i tried an eu region "eu-west-1" for everything "rule set, config and queue" along with the fleet and build but still the ticket stuck in placing, so currently only us-east-1 region is working for me.
answered 2 years ago
0
Hello James, Thanks for your reply.
- I have already dummy latencies for test purposes and its low "60 ms", which means it will have no issue to connect to any fleet. Still, if I removed all fleets and left the one I want, it won't work and no instances will be created at all.
- In my queue, I have the regions and fleet added in destinations "I tried removing all fleets except the one I want to", but if the us-east-1 fleet not there It won't, it won't create any instance and the tickets will get timed out.
- I tried that too, I wrote a lambda function that creates game sessions and worked fine and instances created.
answered 2 years ago
0
Hey Hassan,
Could you verify a few things for us?
- The best practice is that that you should be passing in player latencies for all the fleet locations. If not, then GameLift uses a very high value (1000) as the default latency for the location, and it may be filtered out if you have a player latency policy on your queue. If you have a player latency policy on the queue, try removing that first, or specify a dummy latency for all of your locations.
- Check your queue's filterConfiguration (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-gamelift-gamesessionqueue-filterconfiguration.html) to see if you allowed only placement on us-east-1? (If FilterConfiguration is not configured then by default it should allow all locations)
- Try manually calling CreateGameSession to see if you can create a game session in locations besides us-west-2? Part of what makes a Matchmaking ticket successful is that a game session is successfully created.
answered 2 years ago
0
For #2, could you check if your queue has a filter configuration? If not, then please give us the following information to help us verify if there is an issue in the backend:
- Queue name
- Region of the queue
- Approximate time when you last tried to place a game session on the queue and faced the timeout issue
answered 2 years ago
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 5 months ago