NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
GEO-FILTER NO LONGER SHOWING IN GAME PING
Hello, I have the XR-500 NIghthawks. I mainly play Call of Duty which is the main reason why I got this router. So that I can set a radius to somewhat control the distance of the host and so that...
Hey,
Where are you looking to find this ping?
If you have Auto-ping enabled in Geo-filter, it should show you on the Auto-ping panel beneath the map when you're in-game.
With regards to seeing who is the host, you won't be able to see this informaiton on Geo-filter as there are no peer-to-peer connections, you will just be seeing the server.
I have auto-ping enabled. I have not changed anything then what I had set before and I was able to see what the in game ping is. There is an "Auto Ping" panel and that is where the ping information used to show. I'm attaching a picture I took of the panel during the middle of a game and as shown in the picture ....no ping information is showing.
As far as hosts there are peer-peer hosts when a dedicated server is not available. I have "Filtering Mode", "Strict Mode" and "Auto Ping Host" selected. Again the picture attached is in the middle of a match in Call of Duty. Very rarely do I get ping info like I used to but now this is what I get 99% of the time. Wether the host is a peer-peer connection or a dedicated server most of the time it wont show ping info. It used to but not anymore.
- Could you disable Auto Ping please and click the host/server manually and see if the ping shows please? The issue with CoD is they now don't respond properly to pings so we may need to apply what we do on Ping Heatmap on to the Geo-Filter to compensate.
I disabled auto ping and clicked on the host and no information comes up. I tried it during 2 games. One on a peer host and the other on a dedicated server game match.
Thank you for this.
Just to clarify, which CoD are you playing? Modern Warfare, Cold War, Warzone?
This will assist us in recreating the issue and ultimately resolving it.
Could you also let me know which firmware version you're currently running?
