Netduma Fraser

I'll respond to your email with a confirmation

To comment on your points: The team will be working to improve WiFi Could you provide the ID for that server please so we can correct the location? Good catch, I'll pass it on. Do you mean Ping Assist? It's on the Geo-Filter page > Settings Import/export has been requested for potential future inclusion I'm not sure if the customizable dashboard will be coming back now The table view? While you can see that specifically you can see the list of devices next to the tree view

Do you have speed test bypass enabled? Where are you testing the speeds? Is this over WiFi or ethernet?

Thanks for that, so could you ensure the console is completely shut down, make your Geo-Filter changes, then when you're ready turn on the console/boot up the game and see if that works better please?

With the general Steady Ping not working all the time for CoD yes the team will need to look into it, once we can ensure stability on that then we'll know if it's not always working for other games that that is legitimate. Try just clicking the 'X' top right of the Steady Ping panel and see if it applies then

That's odd, could you get the ID and I'll look into it

Device Prioritization is still there with SmartBOOST. Where are you testing the speeds exactly? What is your exact physical setup? Are ALL devices connected to the R3?

Do you have it connected to a power extender or direct to an outlet? If an extender please try direct to an outlet. Otherwise do you have another power adapter you could try with?

I think it will be mostly bug fixes and no major features being added so unlikely for SmartQoS

Sent to you both

Replied to your topic I've given you access

I appreciate you're frustrated but this kind of post doesn't help, the devs won't suddenly see it and be able to fix it faster than they already are. As soon as it is ready it'll be put out there

You shouldn't do a 30/30/30 reset, it's primarily for older routers. Are you trying to factory reset to prevent the reboot with VPN enabled issue or just get access again after having the VPN issue? A normal factory reset, holding for 30 seconds, releasing then waiting 4 minutes should work or doing a reset from the interface.

As was mentioned by the PingPlotter guide, that first hop is fine. It's the bottom graph you want to pay attention to, that doesn't have any packet loss and seems relatively stable as I do think it's likely the game server and you should try to connect to another.

That's great to hear, thanks for the update!

Sent via PM

Reboot from 192.168.1.1/adv_index.htm and wait 4 minutes again before accessing

We are aware it needs some tweaking so we'll be doing that, if you haven't already a reset after the upgrade is advised

Rebooting the game should be enough in most cases but yes the game caches pings and the servers you can connect to so if you start changing it you need to restart

You shouldn't need to do that but most likely it restarted some backend systems which made it work. You can find a free WiFi analyzer on the Microsoft Store for Windows called WiFi Analyzer. It won't tell you what channel to use but you can see which channels are being used around you and then pick one that isn't being used that isn't close to others or the one that is being used the least. You do have high speeds so CC is needed less so could be a legit suggestion but you can always try adjusting manually to see what gives you the best results.

Without the Geo-Filter enabled at all are you still experiencing disconnects?

I'll pass this topic over to him to see if we can get you further along the path to a resolution

Make sure the PC hasn't connected to a different WiFi but yes you can refresh the page

Sent

Based on the ping, that server in South America for example, very unlikely you'd have 40ms to it so yes it does appear to be favoring ping over location when it shouldn't. I will have to pass that onto the team. The game/console can cache pings/servers which is a potential reason so if you make a change, reboot the router then the console then check again, it shouldn't get outside the radius again unless its a backend bug.