Disable GeoLatency
Disable PingAssist (set it to 0,0)
Enable Strict Mode
Disable Fast Search
Use Simple instead of custom for the 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.
Hello - I saw a similar post on this forum, but I thought i'd create a new one based on my experience.
I have a net duma R3 router that's running on the latest firmware (see the first picture). The router is connected to my PS5 and a small PC, where I can visually see how Duma OS is handling the geo-filtering.
I only play COD MW3 on my PS5.
In the second picture, you'll notice that closest server to me is the one in Salt Lake City, and that's where I currently live. My latency to the MW3 Salt Lake City server is only (3 ms). The second-best servers to me are the ones in LA, yet they don't even show up when I run the ping heatmap.
The third picture shows the actual issue that I started this new topic for; it shows that my ps5 was connected to an LA server, and for some reason, Net Duma thinks that my latency to the LA server is (2 ms), and that's physically impossible. My in-game latency as shown on the picture and as measured by my PS5 is (15 ms), which is more realistic and accurate.
The fourth pictures is just another example.
This happens with all servers that I connect to (including Texas, Washington, Oklahoma, etc) where Net Duma thinks that my latency to these servers is (1 ms) or (2 ms).
This issue has been on going ever since I got my Net Duma R3.
Any ideas as to why that's happening, and how to fix it?
Please note that the geofilter connects me to the LA servers 9 times out of 10, and rarely connects me to the Salt Lake City Server. It (Net Duma Router) thinks that I am closer to LA than to Salt Lake City, yet the Ping Heatmap proves otherwise.
Can you please help fix this issue?
Thank you!
.png "Like")
SGS got a reaction from Zli in In Game Latency Does Not Match Net Duma's Latency