Geofilter not working for Wash DC servers in MW3

[JR_]

Neither range from home nor manually drawing an area seems to work.

If I put the New York/Philly servers in range it will pick them every time, but I've only seen it connect to the DC servers once in a blue moon.

If I put only the DC servers in range, it will search up to <200ms ping, fail to find them, then pick some arbitrary server.

Any suggestions?

Oddly the DC servers don't show on the ping list, but they are visible in the geofilter list occasionally, and connected to very rarely - I have half the ping to them when connected as I do to NY/Philly.

[Netduma Fraser]

Try this:

• Disable GeoLatency
• Disable PingAssist (set it to 0,0)
• Enable Strict Mode
• Disable Fast Search

Then restart game or wait 10 minutes (in the lobby in the game). If that doesn't work, reboot PC/Console and try again.

[JR_]

No luck, it no longer connects to servers outside the highlighted area, but it's also not connecting to the DC servers for whatever reason

One oddity, unsure if it's meaningful to you, but set up that way, the first search is <~100ms ping ingame, rather than <20 like it usually is (moot since it didn't connect, just pointing it out)

edit: after expanding the region back to include NY, it did connecting to matchmaking servers and began searching at <33ms - I'm now wondering if the problem is that there's no matchmaking server in the DC area, and so if it's filtered to just there it won't connect at all?

[emma787]

I have the same problem, I did what he told me and it didn't work on the R2. And on the RX 500 it always had a ping of less than 40ms and now it usually looks for games of 150ms. I hope this is resolved. It is a good product and has good potential.

[Netduma Fraser]

25 minutes ago, JR_ said:

No luck, it no longer connects to servers outside the highlighted area, but it's also not connecting to the DC servers for whatever reason

One oddity, unsure if it's meaningful to you, but set up that way, the first search is <~100ms ping ingame, rather than <20 like it usually is (moot since it didn't connect, just pointing it out)

edit: after expanding the region back to include NY, it did connecting to matchmaking servers and began searching at <33ms - I'm now wondering if the problem is that there's no matchmaking server in the DC area, and so if it's filtered to just there it won't connect at all?

I've sent you a PM with firmware that has Geo-Filter improvements, let us know if that helps at all.

7 minutes ago, emma787 said:

I have the same problem, I did what he told me and it didn't work on the R2. And on the RX 500 it always had a ping of less than 40ms and now it usually looks for games of 150ms. I hope this is resolved. It is a good product and has good potential.

Are you having this issue on the R3?

[emma787]

yes i have r3

[JR_]

3 hours ago, Netduma Fraser said:

I've sent you a PM with firmware that has Geo-Filter improvements, let us know if that helps at all.

Gave this a try - initially it immediately connected me to a DC server, but after that first game, it remains sitting at searching for a match <25ms ping, with either radius or custom geofilter applied and the settings from above changed (geolatency off, ping assist off, fast search off) - I also tried Steady Ping off, though that didn't seem to help either.

This is different from before updating in two ways, the first being obviously that it connected to DC once, the second being that it's now failing with searching at <25ms, before it was starting at <100ms and counting up - vs perpetually stuck at <25 and never raising, nor according to the geofilter map, checking any servers.

I tried restarting the game and despite actively pinging the DC servers, it refuses to connect again - I also tried manually allowing them, same issue, despite being allowed the duma UI says they're blocked and MW3 won't connect.

If I expand the range to include NY it will connect again, still seemingly preferring the NY servers, despite them being farther away geographically and with a worse ping than the DC servers.

 

edit: Tried restarting the game again and trying again, it still would not connect to DC servers, failing to connect to NY repeatedly. When I clicked over to Custom filter with a preselected region around the DC servers it immediately connected to a DC server. I left and tried to connect again, and once again it was stuck searching, blocking NY servers and refusing to even ping a DC server.

The white dots are from the moment it connected to the DC server, but after leaving and trying to search again, it won't find them.

Out of curiosity I checked Zombies and it exhibits the same behavior as multiplayer - refuses to even ping DC servers, attempts and fails to connect to out of range NY servers:

I can't replicate the switching between Simple/Custom filter shape to connect to a DC server. Possible it might work after fully restarting the game, but not much of a solution if it only works once and inconsistently at that each startup. Backing out of search and changing modes then returning does not work either.

[Gus McNasty]

I am having the same issues, on both PlayStation and Xbox, MW3 only shows NY servers and when on Xbox, even with the filter set to 687 miles it puts my on the west coast of the US for Forza.  Those aren’t the only issues, I’ll have to search the threads for the rest.

[Netduma Fraser]

18 hours ago, JR_ said:

Gave this a try - initially it immediately connected me to a DC server, but after that first game, it remains sitting at searching for a match <25ms ping, with either radius or custom geofilter applied and the settings from above changed (geolatency off, ping assist off, fast search off) - I also tried Steady Ping off, though that didn't seem to help either.

This is different from before updating in two ways, the first being obviously that it connected to DC once, the second being that it's now failing with searching at <25ms, before it was starting at <100ms and counting up - vs perpetually stuck at <25 and never raising, nor according to the geofilter map, checking any servers.

I tried restarting the game and despite actively pinging the DC servers, it refuses to connect again - I also tried manually allowing them, same issue, despite being allowed the duma UI says they're blocked and MW3 won't connect.

If I expand the range to include NY it will connect again, still seemingly preferring the NY servers, despite them being farther away geographically and with a worse ping than the DC servers.

edit: Tried restarting the game again and trying again, it still would not connect to DC servers, failing to connect to NY repeatedly. When I clicked over to Custom filter with a preselected region around the DC servers it immediately connected to a DC server. I left and tried to connect again, and once again it was stuck searching, blocking NY servers and refusing to even ping a DC server.

The white dots are from the moment it connected to the DC server, but after leaving and trying to search again, it won't find them.

Out of curiosity I checked Zombies and it exhibits the same behavior as multiplayer - refuses to even ping DC servers, attempts and fails to connect to out of range NY servers:

I can't replicate the switching between Simple/Custom filter shape to connect to a DC server. Possible it might work after fully restarting the game, but not much of a solution if it only works once and inconsistently at that each startup. Backing out of search and changing modes then returning does not work either.

With some servers they are quite hard to force, if that is the case it's a good idea to try with filtering disabled but so you can still see servers on the map and play maybe around 10 times and see if you get connected to the server naturally. Also, may be worth doing a factory reset due to all the firmware upgrades would be good to start fresh and rule out any remnants from previous versions causing issues.

17 hours ago, Gus McNasty said:

I am having the same issues, on both PlayStation and Xbox, MW3 only shows NY servers and when on Xbox, even with the filter set to 687 miles it puts my on the west coast of the US for Forza.  Those aren’t the only issues, I’ll have to search the threads for the rest.

Same as the above but I have sent you the firmware just in case

[TheTerpinator710]

On 12/23/2023 at 2:05 PM, Netduma Fraser said:

I've sent you a PM with firmware that has Geo-Filter improvements, let us know if that helps at all.

Are you having this issue on the R3?

Can I get update firmware too please? Would love to test! 

[Netduma Fraser]

11 hours ago, TheTerpinator710 said:

Can I get update firmware too please? Would love to test! 

Sent, Happy Holidays!