Jump to content

Geo-filter not consistently working


merthaw
 Share

Recommended Posts

I created a custom geo-filter for Black Ops 6 (Steam) that seems to stop working at different times of day. I might get a string of 5-10 games that are within my filter and another 5-10 games that are consistently outside the filter. Multiple times, I have tried:

  1. Quit the game back to console dashboard
  2. Remove device from the Geo-Filter
  3. Resync the cloud
  4. Re-add the device to the Geo-Filter
  5. Set up your settings
  6. Wait 2 minutes
  7. Boot up the game

No avail. It particularly likes to throw me in St. Louis servers (like 99% of the time) for some reason. Looks like it initially looks for West Coast servers and then gives up and connects me to St. Louis.

I'm on an MSI Stealth Studio.

Screenshot 2024-12-22 093333.png

Link to comment
Share on other sites

Merry meowmas!  I'm having similar geo experiences with black ops 6 on West coast servers, but I'm on the R1. Out of curiosity, when it initially tries to connect to West coast, does it look like the server is in LA? And if so, do you get a notification bell in the black ops menu that says unable to connect to host when it happens? That's what's going on for me anyway, it will connect to the san jose servers okay, but every time it tries the LA servers I get the unable to connect to host alert in the notifications in blackops 6. 

 

If I set it strict in my geo it will eventually grab a Seattle one, but this can take a very long time, it seems to want to try the la servers first for me almost every time. 

Link to comment
Share on other sites

Merry meowmas indeed. I'm not seeing any such notification. I don't even see it try to connect to a certain server.

My workaround has been just babysitting the queue and when I see it start searching 60 ping, I cancel the search. It can take 15-20 minutes before finding a local match. I've kept it in strict mode at all times.

Link to comment
Share on other sites

  • Administrators
  • Disable GeoLatency
  • Disable PingAssist (set it to 0,0)
  • Enable Strict Mode
  • Disable Fast Search
  • Use Simple instead of Custom radius

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

Link to comment
Share on other sites

That didn't quite work! I was doing all but using simple instead of custom radius. I think part of the problem is that I'm playing Ranked early-ish in the morning (instead of a more widely played mode) and it takes a long time to find a match. It seems like the program "gives up" searching for a match within my radius after a certain amount of time (~3 minutes), and it's basically always St. Louis servers. Is there a way these servers somehow bypass the filter?

Link to comment
Share on other sites

  • Administrators

If you've done all the above settings then it shouldn't be able to get past no, unless we've whitelisted a server incorrectly or they're relaying you through a server you can connect to which doesn't seem to be the case. Do you get the same issue still with the normal radius?

Link to comment
Share on other sites

On 12/27/2024 at 11:35 PM, Netduma Fraser said:
  • Disable GeoLatency
  • Disable PingAssist (set it to 0,0)
  • Enable Strict Mode
  • Disable Fast Search
  • Use Simple instead of Custom radius

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

I have setup all these setting but no result 

Link to comment
Share on other sites

I've been adding them to my deny list as I get connected to them. I think it's been about 11 so far. Hopefully I'll get them all soon

Maybe I got them all because now it's giving me Chicago. Just as bad ping-wise.

Also Texas. I think DumaOS is broken

Link to comment
Share on other sites

  • Administrators
7 hours ago, bochbou9 said:

I have setup all these setting but no result 

If you could make a new topic for your issue please

5 hours ago, merthaw said:

I've been adding them to my deny list as I get connected to them. I think it's been about 11 so far. Hopefully I'll get them all soon

Maybe I got them all because now it's giving me Chicago. Just as bad ping-wise.

Also Texas. I think DumaOS is broken

They will have a lot clustered in a single location.

It's not broken, it's likely an easily resolved cloud issue. If you could provide a video of exactly what you do/happens that would be really helpful. If you run through all the settings pages as well it will let me know if there are any settings impacting it.

Link to comment
Share on other sites

  • Administrators

I know you said you did these steps but you're not doing the PC/Console workaround so if you could just run through this so you have it setup that way and see if it's more consistent please:

  1. Quit the application/game/client completely
  2. Remove device from the Geo-Filter
  3. Give PC PlayStation Device Type in the Device Manager
  4. Resync from the Geo-Filter Map menu
  5. Re-add the device to the Geo-Filter with the manual option
  6. Set up the Geo-Filter how you like
  7. Wait 2 minutes
  8. Boot up application/game/client
Link to comment
Share on other sites

No, they were all outside my filter. Mostly St. Louis, Texas, Chicago, Atlanta, etc. I will say that the last few searches have resulted in the correct server. Fingers crossed this continues...

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...