R3

[SableEU]

Great router! The UI is a lot faster and responsive  which is what DumaOS needed imo. The setup was nice and easy. The device itself looks incredible especially with the RGB.

Took some time to get the geo filter working how I wanted it, I was connecting to servers outside of my radius until I read another user comment on here about the geo latency option, not sure if that is working as intended. Steady Ping doesn’t always work (Usually the first game on a server) but when it does work you can feel the difference. The ping buffer definitely helps not to be on the bad end of lag compensation which I would of got on servers that I normally would, for example Germany server was horrible to play on before playing from UK it would give me a 20-25ms ping but with steady ping adjusted I not get 35-40ms. Still playing on UK servers ain’t great for Call of Duty MW3. 

Not sure how other people are getting on in Destiny 2 PS5 but I cover the whole of Europe and the game will search for member 12/12 try to load the game and then get kicked not sure why.

Im yet to try other games but for CoD it works wonders.

[Netduma Fraser]

Glad to hear you like it and are enjoying it overall! We're looking into the issues you mentioned currently. For Destiny 2 you'll have to use Geo-Latency to get filter it properly

[SableEU]

38 minutes ago, Netduma Fraser said:

Glad to hear you like it and are enjoying it overall! We're looking into the issues you mentioned currently. For Destiny 2 you'll have to use Geo-Latency to get filter it properly

Ok I’ll give it a try with destiny 2.

Congrats on the progress of DumaOS, come a long way since the R1 days.

[Netduma Fraser]

31 minutes ago, SableEU said:

Ok I’ll give it a try with destiny 2.

Congrats on the progress of DumaOS, come a long way since the R1 days.

Thanks a lot, we've definitely made some improvements!

[Stilts29]

On 12/19/2023 at 3:12 PM, Netduma Fraser said:

Glad to hear you like it and are enjoying it overall! We're looking into the issues you mentioned currently. For Destiny 2 you'll have to use Geo-Latency to get filter it properly

Hi @Netduma Fraser,

Just came across this comment a while back. Can you explain a few things please,

• What does Geo-latency do that's different from the usual filtering?
• If I set Geo-latency on for Destiny 2 should I also have the filtering option on also?
• Are their issues with Geo-latency working with Destiny 2 on .23 at the moment? Should it be on if so?

Cheers

[Netduma Fraser]

22 minutes ago, Stilts29 said:

Hi @Netduma Fraser,

Just came across this comment a while back. Can you explain a few things please,

• What does Geo-latency do that's different from the usual filtering?
• If I set Geo-latency on for Destiny 2 should I also have the filtering option on also?
• Are their issues with Geo-latency working with Destiny 2 on .23 at the moment? Should it be on if so?

Cheers

1. I don't think we've revealed fully how this works but I think we'll discuss it properly in a video
2. Yes filtering needs to be enabled
3. Not that I am aware of but give it a try and let us know how you get on

[Stilts29]

15 hours ago, Netduma Fraser said:

1. I don't think we've revealed fully how this works but I think we'll discuss it properly in a video
2. Yes filtering needs to be enabled
3. Not that I am aware of but give it a try and let us know how you get on

Thanks for clarifying some of the points. Just to let you know that when you select Destiny 2 when setting up Geofilter it recommends not to switch on filtering for this game.

But as per your comments, then Geo-Latency will not work and its designed to work with games like Destiny that have been difficult to get working with normal filtering.

[Netduma Fraser]

35 minutes ago, Stilts29 said:

Thanks for clarifying some of the points. Just to let you know that when you select Destiny 2 when setting up Geofilter it recommends not to switch on filtering for this game.

But as per your comments, then Geo-Latency will not work and its designed to work with games like Destiny that have been difficult to get working with normal filtering.

It's not working in what way exactly?

[Stilts29]

44 minutes ago, Netduma Fraser said:

It's not working in what way exactly?

I think we have crossed wires maybe, I'm not saying it doesnt work, just that you mentioned that the Geofilter needs to be on for Geo-Latency to work. If someone sets up Geofilter for Destiny it advises the user to turn off filtering. If a user did that then Geo-latency would not work. Just pointing that out because its not clear that they both need to be on for games like Destiny when you setup specifically for that game. 

I'm testing now with Geofilter and Geo-Latency and will let you know how I get on. I am still having probs with port forwarding to get open nat which is on another post.

[Stilts29]

29 minutes ago, Stilts29 said:

I think we have crossed wires maybe, I'm not saying it doesnt work, just that you mentioned that the Geofilter needs to be on for Geo-Latency to work. If someone sets up Geofilter for Destiny it advises the user to turn off filtering. If a user did that then Geo-latency would not work. Just pointing that out because its not clear that they both need to be on for games like Destiny when you setup specifically for that game. 

I'm testing now with Geofilter and Geo-Latency and will let you know how I get on. I am still having probs with port forwarding to get open nat which is on another post.

Port forwarding working now. Had some time to check and filtering is working fine. Steady ping never kicks in usually, but have seen the odd occasion when it does. 

After a lot of experimentation though the game setup itself is mainly to blame for bad connections. If you take Destiny for example it still matches you with people all over the world fairly often, due to steam match making and VPN's I assume. Just had a game when one of the players was in Russia and had the host connection so was one sided from the start and most people on my team left the game. I had a good ping connection to London server.

MW3 has aggressive SBMM so again you can have good ping but bad games due to VPN's or steam matchmaking policies.

[Netduma Fraser]

3 hours ago, Stilts29 said:

I think we have crossed wires maybe, I'm not saying it doesnt work, just that you mentioned that the Geofilter needs to be on for Geo-Latency to work. If someone sets up Geofilter for Destiny it advises the user to turn off filtering. If a user did that then Geo-latency would not work. Just pointing that out because its not clear that they both need to be on for games like Destiny when you setup specifically for that game. 

I'm testing now with Geofilter and Geo-Latency and will let you know how I get on. I am still having probs with port forwarding to get open nat which is on another post.

2 hours ago, Stilts29 said:

Port forwarding working now. Had some time to check and filtering is working fine. Steady ping never kicks in usually, but have seen the odd occasion when it does. 

After a lot of experimentation though the game setup itself is mainly to blame for bad connections. If you take Destiny for example it still matches you with people all over the world fairly often, due to steam match making and VPN's I assume. Just had a game when one of the players was in Russia and had the host connection so was one sided from the start and most people on my team left the game. I had a good ping connection to London server.

MW3 has aggressive SBMM so again you can have good ping but bad games due to VPN's or steam matchmaking policies.

Oh I gotcha, thanks for clarifying. I believe it's been brought over from how it was before with the standard Geo-Filter in which case it was advised. I'll get the team to amend the message to something along the lines of we recommend disabling if you won't be using Geo-Latency or something to that affect. Responded to your other topic about NAT. There will be times when you still get bad connections, you can limit that by adding that server to your deny list, overall with the router you should have a more consistently better experience.

[Stilts29]

On 1/20/2024 at 6:41 PM, Netduma Fraser said:

Oh I gotcha, thanks for clarifying. I believe it's been brought over from how it was before with the standard Geo-Filter in which case it was advised. I'll get the team to amend the message to something along the lines of we recommend disabling if you won't be using Geo-Latency or something to that affect. Responded to your other topic about NAT. There will be times when you still get bad connections, you can limit that by adding that server to your deny list, overall with the router you should have a more consistently better experience.

Unfortunately that is not applicable for Destiny, I always connect to London or Amsterdam server with a good ping but its peer to peer after that and other players will be connecting to those servers from as far away as India, Russia and USA. The geofilter map lets me know where the players are located. They must be using a VPN or something or Steam is still matchmaking me with players far away. 

[Netduma Fraser]

You can't affect who connects to your servers unfortunately but if you're close to the server then you should have an advantage.