Detroit Lions Podcast

yes -everything used to work and was setup to spec. This is a new wrinkle.

I'm in Florida and Attempting to lock in Atlanta server. its really intermittent. Works for a bit, then doesn't. Been as far away as Chicago and LA for servers.

Same problem - the geofilter setup that worked for MW2, MW3, and up til now is no longer working. Settings haven't changed. It just stopped working and now I am placed all over the US - Jersey, Chicago, LA, Texas. Its bananas how they don't care an iota about your location when putting a lobby together. I need to get control over this back or its the end for me. I won't play a game that is so horribly manipulative - I can watch a movie if I don't want to affect the outcome of something on the screen by my actions.

Of course doing the easy/normal/sensible thing of using the App makes everything work wonderfully. Much appreciated, Fraser, thanks again for your help.

Appreciate the ongoing support, Fraser. You do a great job here with all the variables (both tech and people) that you have to deal with 🙂 Seems to work as it did with the custom radius, but it works. Connecting exclusively in Savannah but not Atlanta. During the search Atlanta servers light up, just always lands in Savannah. Could be that some servers are mislocated from Atlanta, or heck, maybe they picked up hosting in Savannah *shrug*. One last question: Do you know why - or more importantly how I can fix the issue - when I log in to the Duma (R3) from my iPad, every time I get into a lobby or out of a lobby or it seems when there is a server hand-off of some sort (speculation, but seems to track) I am prompted to log back in to the router? Its kind of driving me bananas because I have to put my controller down and re-login if I want to track server performance during a game. When I get sporadic lag spikes and I look over to the iPad I wind up seeing the login screen and not the network data. Of course by the time I log in the spike is gone and I have no information to work with. Its a frustrating QoL issue, but it also takes away some of the usability. Thanks again for your help.

After checking the only thing that I needed to change was the simple vs. custom radius, everything else was set as directed. Do you know why the radius setup would need to be different in BO6 rather than in MWIII? The reason I had custom radius was to keep the authentication server that I kept hitting (was listed as being in Oklahoma) included so I could get into games while blocking the Texas and Miami servers which picked up people with significant lag issues. I'll test in a bit and share results, but I'm skeptical about the smaller radius that I have selected. Do we know which US locations have authentication servers for BO6?

Further update: Expanded my geofilter to include Washington (DC) and then started playing on Washington's server every time, I still always get matchmaking from Tokyo. I experimented by closing Washington DC out of the geofilter and I suddenly started connecting in Savannah, GA exclusively for the entirety of the night (at least 4 hours). Seeing the servers in the pic on occasion, and very rarely I'll see other servers like Atlanta, Miami, and Illinois as I would expect from prior titles. Something is very weird with the servers in BO6 compared to previous titles.

Still happens today. I seem always to be in Tokyo, but if I turn off the Geofence I get East Coast servers. Do we know where the servers are in the US (which cities)? I am not getting any pings in Atlanta now and imagine that maybe there aren't servers inside my geofilter.

So interestingly, I was having Geofilter issues yesterday as well. Things seemed to be operating pretty well, but I can't monitor it as I used to because firmware v4.0.236 constantly logs my iPad out and I have to relogin almost every 2-3 minutes which is a pain. Now instead of monitoring while I play I typically check when there is an issue. Also, I get an error message every couple of days when I try to log in that it can't connect to DumaOS and I have to restart the router, which isn't just an added complaint but is also relevant to my experience in night 1 of the BO6 beta. I haven't played COD in a week or so, so I don't know if this is a brand new issue, but it was brand new to me. So starting around 2AM ET, I was curious about what was going on with connectivity during the beta and if I was still connecting solely to the Atlanta server so I tried to log in and of course got the stupid error that forced me to restart the router if I wanted to see what was happening. I told my friend/party mate that I was going to reboot and rebooted both my PS5 and my NetDuma. After reboot I logged in and partied back up with my friend. I logged in to the DumaOS and started the game, partied up with my friend and began my search for a game. First think I noticed is that I was being placed on a Ft. Worth, Texas server for search, which is strange because it is outside the geofilter range, and I used to connect to a server labeled "Oklahoma" for that. What happened next was nuts - we connected to a server in Tokyo. Now that's basically on the entirely opposite side of the world from me and is obviously outside of the geofilter area I have setup. The giveaway that it wasn't a mislabeled server was that the names were all in asian character sets or there were a number of clan tags like [Korea] etc. We definitely weren't in the US. Lag was reported at 150ms and it was hilarious watching the bullets start reporting hits all at once after half a mag was dumped into someone. We continued to connect to Tokyo exclusively for over an hour. I started to wonder if Activi$ion had determined a way to punish Duma users (since they aren't spending their time or resources fixing the prevalent in-game cheating issues). We moved the party lead over to my friend to see how things were working and the system looked massively confused and wouldn't find us a lobby. Once I turned off geofiltering we started connecting up and down the east coast again and getting the lag-based matchmaking experience Activi$ion wants to provide. Not sure if the matchmaking servers have changed up the algorithm, if Activi$ion has found a way to punish Duma users (like they do with shadowban lobbies), or they were doing some kind of funky testing since its the beta. Seeing others finding geofilter issues like I am starts to make me think one or more of those things are true. Hopefully this information will be helping in tracking down the issue, its one that we need fixed pretty quickly as their matchmaking experience makes the game feel like a frustrating pile of garbage. The Duma is the only thing that makes the game playable, please fix!