NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Multiple games matchmaking "messes up"?
I have noticed this issue in two separate games that I've played and while it could be just the games themselves the fact that both games have effectively the same problem happens makes me question if something is wrong that maybe I'm not aware of.
In Street Fighter 6 and Guilty Gear Strive that are technically P2P fighting games I run into this issue where I will play against multiple people just fine and then after maybe 4-5 people BOTH GAMES will suddenly go into what I would describe as "matchmaking loops".
Both games will basically show that I am "Connecting" or "Checking Opponents Connection" indefinitely as if it can no longer match with another person. Either I have to outright restart the games or it would take an excessive amount of time to find another match.
Both these games are relatively popular for what they are so it shouldn't be a lack of opponents to play against. Secondly if I monitor to my personal connection, like say pinging google DNS I can see that it is stable and never going above like 45ms, so there isn't any fluctuations on my "raw connection". My speeds are 500/100 so I don't think it is a bandwidth issue either.
I have UPnP ON on the router so there shouldn't be any problems connecting to other people if I understand how that is SUPPOSED to work. But I did try to setup port forwarding as stated within whatever game support or Playstation said to do anyway. So I also have a static IP for my PS5 setup to do that.
So my question is what could be causing this type of problem and is there a solution? Cause it is one thing if it was happening just in a specific game but the fact that same pattern happens in both is a little suspicious.
System: PS5
Connection: Wired
Router: XR1000v2 (xr1000v2 1.1.0.22_2.1.34)
Modem: CM2000
7 Replies
Presumably you're using the Geo-Filter is that correct? If so it's likely your radius size is too strict, we suggest at least 1000km but you may need to widen it to allow more games. Let us know if that is the cause.
I do not currently have the Geo-Filter enabled but from previous usage attempts I had it set to 1110 miles/1786km.
Because these games are P2P the geo filter is basically non-functional from a practical standpoint because the games themselves would not be able to recognize that the connections "aren't allowed" because of the geo filter in my experience. What typically happens when it is setup is that the game would try to match with someone outside the filter -> the filter functions correctly and disallows it -> the game does a matchmaking connection error since it couldn't connect to that person. So the matchmaking itself becomes inherently worse since it thinks it is erroring out whenever it runs into these types of connections.
This is why I haven't been using the geo filter anymore anyway.I get you, the way the matchmaking works makes Geo-Filtering more of a slog. If you don't have the Geo-Filter enabled then there isn't really anything blocking you from making further connections, do you get the same issue if you connect your PS5 directly to the modem?
Something to check with the game Mfr and game console Mfr first about. Can be anything on the hosting side.
Does this happen with gaming directly with the ISP modem/ONT with out the router in the mix?
Is the game console ethernet connected or wireless connected to the router? Ethernet is preferred.
Tried a factory reset and setup from scratch on the router?
I can't easily test the situation without the router given other people needing to use the internet for more important stuff inbetween everything but that is something I will have to try on the off chance there's a good time I'm able to do that.
I do always use a wired connection so no wireless while I am gaming.
I have factory reset this router a few times because of other issues in the past, and just from ongoing problem situations I can say I don't think that has solved this particular problem since it has continued to happen over the last two years or so in the meantime unrelated to the other problems I experienced before those factory resets.
