Jump to content


  • Content Count

  • Joined

  • Last visited

  1. I am from the US. No matter where I set the geo-filter, I get matches with SOLO people from all over the world. They are not being brought in by a fireteam leader connecting to them, they seem to being brought in because you dont allow me to black list servers that people in denmark and Japan are connecting to. This router simply doesnt work at all with Destiny2 since you whitelisted all the servers. Since this is the game I play, it is dishartening that the router doesnt work at all with D2. Especially when it USED to work when I could deny servers from out of the country. Also, you guys should get your suggestions in order, since the last time I created a topic to discuss this, it was suggested to use strict mode (and that it would lead to more disconnected games, but better connections). Now you are claiming to NEVER use strict mode. Regardless, strict mode or not, the geofilter simply doesnt work at all for Destiny anymore. Can you please either admit that it doesnt work at all, or give some advice on how to set it up so it works. Right now at least 50% of players I match against are from other continents, when my geo filter is set to 500km in my area. To test if it made any difference at all, I moved it to Europe, where I got the same random matchmaking, as evidence that the geofilter doesnt do anything at all with D2. I see you play on PS4, maybe you can fireteam with me and explain how my setup is not right.
  2. I posted a couple comments on another thread, but this needs to be addressed. Since the destiny servers were all white listed, geofiltering doesnt work at all. Not in strict mode, regardless of the range, etc. It is CONSTANT connections to INDIVIDUAL players from way outside the range of the geo filter. What is the solution for this, or does geofiltering just flat out not work for D2? I should note that moving the center of my geofilter (and rebooting) in D2 does not actually change what servers or what players I connect to. If you cant deny servers, you cant geofilter. Forcing all destiny servers to be white listed seems to make the geofilter not work.
  3. So.... how does geo filtering work then? because it absolutely does not right now. Or to put it another way: does Geofiltering just not work on D2? It used to when it would deny the servers, but now I get wide ranges of players, even in lobbies full of solo players. What settings should I be using?
  4. The next game (with only 2 of 12 grouped) looked like this Honestly, I even tried forcing a public IP change by changing what MAC was used. That is how desperate I am to get this sorted. It didnt work. It is still worse than normal matchmaking. By a HUGE amount.
  5. I have the same problem, and I didnt used to have it. I am CONSTANTLY connecting to dedicated servers in destiny that I have set as "denied" and through them, connecting to people WAY WAY outside my accepted range (or any acceptable range for gaming). I find when this happens that the only solution is to disable geofiltering. I have been told that you cannot deny servers (destiny "requires" them to work, AND that denying individuals doesnt do anything in the geofilter. I am just curious how it is SUPPOSED to work now, because it seems to just absolute garbage right now. This is what my settings are while matchmaking These two servers are denied (but still used for matchmaking) This is the game I got (with only two people grouped together) This is the denied servers It didnt used to be like this. Now it seems like nothing is working correctly. I have tried this with a radius that covers the entire US and parts of Canada. I have tried with just the west coast. Just CA/NV. Just Or/Wa (Bungie HQ). None of it makes a difference. CONSTANTLY matchmade with people from anywhere at random, through servers around the world.
  6. They are all "allowed" and little people (rather than triangles). Even if its just people inside my geo region selected (ie 1000km) it gives me nat errors.
  7. Yeah. Party chat works fine if I spectate and rejoin the party. It also stays working fine if I switch from spectate to filtering while in a party. (edit: Without rebooting my PS4, but that requires constantly changing settings from spectating to filtering, backing in and out of the game, and quitting parties etc. I havent found that to be worth my time.) Also, I set up the router using portforward.com, so I am not sure what I would have to change.
  8. I saw in a previous thread from Feb2018 that someone got DM's a hotfix to possibly resolve this issue. Not sure why it wasnt just posted, but either way, same problem: I cant talk to anyone if I am filtering. Whitelisted friends, people inside my geo selection. No one. It just says NAT not compatible. For me, that means that geo filtering is a single player only use. Any tips?
  9. My ISP (Comcast) says they can't renew my IP unless I pay for business service for an insane upcharge. Maybe the 24 hour thing will work. I tried about 8 hours, overnight, and that didn't. My only other ISP option is 3mbps AT&T. Unbelievable. I theoretically should be able to get around this with the VPN update, right? But I am unclear on the steps I need to take to do that. If that would help my situation, is it possible to discuss how to configure it?
  10. My question is super basic and not really related to DumaOS (other than that is what I use): How to I get a public IP that makes sense? DumaOS has not worked very well for me for a while... After a lot of digging, Turns out my IP address is geo-located by at least one service I can find (IP2Location) on the opposite side of the country. Others show me correctly basically right in my house. (ipinfo.io EurekAIP, DB-IP)... This causes me to matchmake almost exclusively on the wrong side of the country, or EXTREMELY poor quality of games even with filtering.
  11. >>Hi everyone. We have just made a large Cloud update. This will improve IP location of all devices and all games. These changes will automatically install on your router within the next 24 hours, but if you would like to force your Cloud to update, please do the following: Go to your Geo-Filter Open the Geo-Filter Map Options (click the three horizontal lines in the top left of the panel) Click 'Flush Cloud' Wait about 30 seconds - 45 second for the Flush to complete. Don't worry if you see a message that says '"Error: The operation is taking longer than expected. Please briefly wait before using this R-App" - this is just a default popup that appears when something is taking a while to complete on DumaOS. Just clear the message and wait another 30 seconds for the new Cloud to complete its installation in the background Once complete, make sure you're happy with your other Geo-Filter settings e.g. home location, radius, Ping Assist on the R1 etc. Now restart your game Don't worry if a server sometimes shows as a 'Peer' - there are still servers that we have not yet been categorised as servers. This will be something we tackle in the future but it is a purely visual benefit so don't sweat too hard if they're showing as peers. We will announce this more publicly once we have feedback from you that things are looking good. Thanks. i'll try this
  12. Thanks. Playing a match just now with spectating De-selecting auto ping and selecting what looks to be the host FWIW, Auto-ping host never works now. For all intents and purposes, it seems like there just are no players at all in the area between the Pacific and the Rockies. Like it is a black hole of non-gamers.
  • Create New...