Geo Filter simple mode not working

[nowmat]

On 12/23/2023 at 7:07 PM, Netduma Fraser said:

Sent

Thanks, tested yesterday, works fine with geo latency enabled.
Question , what does this give me in terms of finding matches in MW3?

[Netduma Fraser]

24 minutes ago, nowmat said:

Thanks, tested yesterday, works fine with geo latency enabled.
Question , what does this give me in terms of finding matches in MW3?

Great to hear! Could you clarify the question please?

[Stobbee]

I never get this ping preview. It always says “couldn’t ping server”. Is it like this for everyone or it’s just me? 

[Crash0verride]

I had to let mine sit there for a minute before it pinged the server. 

Other than that, messing with the advanced settings for ping seems to break the geo filter radius a bit. I modified ping to 60MS and it started connecting to servers outside of my radius. I've only had it up and running for 48 hours so it's hard to say if there is a more optimal way to do this since some settings seem to prioritize over others. I haven't tried plotting anything yet.

In other news, I was playing MW3 last night and the connection got real choppy, like hits not registering and getting hit with packet bursts. Restarting the R3 seemed to have fixed it. I presume it was from me playing with geo filter settings but it's hard to say. 

[emma787]

Hello, I still have the problem with the r3 Geofilter not working as it is supposed to, it leaves the marked area and starts looking for servers that have a very high ping of 150 ms. I think they should implement the geo they used in rl r2. In r2 I was getting a ping of 30 to 40 always in the call of duty game before I could connect to the Miami servers now it doesn't work I hope they can solve the problem the r3 has the potential to be a perfect router

[nowmat]

On 12/24/2023 at 8:53 PM, Netduma Fraser said:

Great to hear! Could you clarify the question please?

When playing MW3 with geo latency turned off, I search for matches in about a minute Polish server in Warsaw, which is good... With geo latency turned on, I don't see any difference in searching for matches.
What exactly does this new feature (geo latency) do when playing CoD?

21 minutes ago, emma787 said:

Hello, I still have the problem with the r3 Geofilter not working as it is supposed to, it leaves the marked area and starts looking for servers that have a very high ping of 150 ms. I think they should implement the geo they used in rl r2. In r2 I was getting a ping of 30 to 40 always in the call of duty game before I could connect to the Miami servers now it doesn't work I hope they can solve the problem the r3 has the potential to be a perfect router

It seems to me that if you turn off geo latency and steady ping, the match search is like in R2.

[emma787]

2 minutes ago, nowmat said:

When playing MW3 with geo latency turned off, I search for matches in about a minute, which is good... With geo latency turned on, I don't see any difference in searching for matches.
What exactly does this new feature (geo latency) do when playing CoD?

It seems to me that if you turn off geo latency and steady ping, the match search is like in R2.

I have them disabled I still have the problem that it searches outside the geo

[Deasha]

7 hours ago, Stobbee said:

I never get this ping preview. It always says “couldn’t ping server”. Is it like this for everyone or it’s just me? 

I can’t see this either in my Xbox series X the couldn’t ping server message shows up every single game on call of duty. I do have the ability to ping the server in heat map though

[Stobbee]

1 minute ago, Deasha said:

I can’t see this either in my Xbox series X the couldn’t ping server message shows up every single game on call of duty. I do have the ability to ping the server in heat map though

Same for me! 

[Netduma Fraser]

If it says cannot ping this server that is usually legitimate. 

19 hours ago, Crash0verride said:

I had to let mine sit there for a minute before it pinged the server. 

Other than that, messing with the advanced settings for ping seems to break the geo filter radius a bit. I modified ping to 60MS and it started connecting to servers outside of my radius. I've only had it up and running for 48 hours so it's hard to say if there is a more optimal way to do this since some settings seem to prioritize over others. I haven't tried plotting anything yet.

In other news, I was playing MW3 last night and the connection got real choppy, like hits not registering and getting hit with packet bursts. Restarting the R3 seemed to have fixed it. I presume it was from me playing with geo filter settings but it's hard to say. 

What ping setting did you change exactly?

17 hours ago, emma787 said:

Hello, I still have the problem with the r3 Geofilter not working as it is supposed to, it leaves the marked area and starts looking for servers that have a very high ping of 150 ms. I think they should implement the geo they used in rl r2. In r2 I was getting a ping of 30 to 40 always in the call of duty game before I could connect to the Miami servers now it doesn't work I hope they can solve the problem the r3 has the potential to be a perfect router

Disable Geo-Latency, do you get the same issue?

17 hours ago, nowmat said:

When playing MW3 with geo latency turned off, I search for matches in about a minute Polish server in Warsaw, which is good... With geo latency turned on, I don't see any difference in searching for matches.
What exactly does this new feature (geo latency) do when playing CoD?

It seems to me that if you turn off geo latency and steady ping, the match search is like in R2.

 It still may appear to search in the same way if it gets games within your radius.

--
I've sent you all the firmware with Geo-Filter improvements in a PM, some of you may have it already

[Crash0verride]

5 hours ago, Netduma Fraser said:

If it says cannot ping this server that is usually legitimate. 

What ping setting did you change exactly?

Disable Geo-Latency, do you get the same issue?

 It still may appear to search in the same way if it gets games within your radius.

--
I've sent you all the firmware with Geo-Filter improvements in a PM, some of you may have it already

I will try and update the firmware later.

I had everything by default to start with the filter size. It was selecting servers within the filter circle. I went and changed the ping assist setting to 60MS to see what kind of connections I would get and it started selecting servers outside of the filter radius that were within the ping margins. I tried closing in the filter size radius but didn't solve the issue. I then put ping assist back to default hoping the filter radius would kick back in but it didn't. It was connecting to 3 servers outside of my preferred range but within the ping assist margins. 

After a reboot, it looked like it was only connecting to 1 of the unpreferred servers,  a bit north of my filter circle (Chicago). I tried blocking it but it didn't take. I just started backing out of the lobby if it connected to that server. Not a huge deal, but my connection to that server just seems to be really bad for some reason.  I'll do some more testing as I play this week/weekend.

Atlanta seems to be my preferred server. I haven't seen a connection to Miami or Washington DC yet, but I'm on Xbox so i'm not sure if maybe not all servers are crossplay enabled or something else is happening? I know someone locally using the R2 so I will probably do some troubleshooting and compare/contrast results. I may end up resetting everything and going back to a basic geo-filter circle.

[Netduma Fraser]

2 hours ago, Crash0verride said:

I will try and update the firmware later.

I had everything by default to start with the filter size. It was selecting servers within the filter circle. I went and changed the ping assist setting to 60MS to see what kind of connections I would get and it started selecting servers outside of the filter radius that were within the ping margins. I tried closing in the filter size radius but didn't solve the issue. I then put ping assist back to default hoping the filter radius would kick back in but it didn't. It was connecting to 3 servers outside of my preferred range but within the ping assist margins. 

After a reboot, it looked like it was only connecting to 1 of the unpreferred servers,  a bit north of my filter circle (Chicago). I tried blocking it but it didn't take. I just started backing out of the lobby if it connected to that server. Not a huge deal, but my connection to that server just seems to be really bad for some reason.  I'll do some more testing as I play this week/weekend.

Atlanta seems to be my preferred server. I haven't seen a connection to Miami or Washington DC yet, but I'm on Xbox so i'm not sure if maybe not all servers are crossplay enabled or something else is happening? I know someone locally using the R2 so I will probably do some troubleshooting and compare/contrast results. I may end up resetting everything and going back to a basic geo-filter circle.

That's how Ping Assist works, you've told it to connect you with games under 60ms so it's done that - games under 60ms may be outside your radius and therefore you can then connect to them. If you want to exclusively use the radius Ping Assist should be set to 0.

When you deny a server fully the connection has to be completely severed before it can be blocked, if you research immediately the connection can be kept alive and therefore it does not become blocked. The next time you go to play after a break it'll be blocked, if you restart the game/console it will sever the connection and be blocked. Keep in mind there are usually lots of servers clusters in the same location.

You may not connect to all the servers within the radius, you can try to force those specifically by just covering them but some servers are notoriously hard to force.