Jackal235

The game is really bad for me too. Instant deaths, sometimes I don't even see my enemies (except kill cams). The only way to be positive is use geo filter to find 50-80ms games. Unfortunately in my location they are not easy to find. Looks like devs did something to make it more suitable for Xmas players. Anything they're doing is to boost sales not to improve gaming experience.

If HDR is enabled on the console these settings will be locked in the game. Any HDR adjustments can be done on PS5 screen & video menu. Only If you disable HDR on PS5 then you can change brightness in the game.

My traffic prio is on, for game console only. The rest is disabled. Benchmark test: all 3 show A+ congestion control set to always

I think that there is a problem with this website and its test. About 2 weeks ago I had good results and suddenly my upload is also above 100ms even though my settings have not changed. Now I went as low as 30%, still bad upload active.

Is there a beta firmware available for XR1000?

Might be one of your apple devices randomly changing MAC address (new security feature) Use private Wi-Fi addresses on iPhone, iPad, iPod touch, and Apple Watch - Apple Support (CA)

Hi, It looks that, my best games are on 60-70ms servers, which are not that easy to find. Anything close to me is under 30ms, when looking for farther is around 100ms or more. Is there a way to set the geo-filter to allow 60-70ms games (not below, not above)?

It's been one year since netduma luke stated about brand new firmwares for nighthawks as below. So my congrats on the anniversary. Hi everyone, This is an update for you guys on where we are with DumaOS and specifically, the XR/NPG routers which is why we have posted it in this subforum. First of all, here’s the current status for each XR router, including links to where you can get the latest firmware for those of you who don’t already have it installed: XR300 – V1.0.3.68 (DumaOS 2.0) XR450/XR500 – V2.3.2.130 (DumaOS 3.0) XR700 – V1.0.1.46 (DumaOS 3.0 Beta) XR1000 – V1.0.0.58 (DumaOS 3.0) Now to address the problem: the speed at which XR users have been getting new firmwares. We realise it has been far too slow. Here’s how the firmware building process typically works: Every few months a new DumaOS firmware is completed This first must pass our internal testing Then it moves over to NETGEAR where it must pass their testing, including all the non-DumaOS side of the firmware Then it goes into closed beta testing Eventually, if all has gone well, it will be released The big problem we have is that if there is an issue at any point, the entire process needs to start again. Considering all the different XR routers DumaOS is on combined with the fact all of them have very large user bases (meaning disaster if a serious bug gets through) and you begin to see the problem. So, what can we do about this? We asked ourselves the same question at the beginning of the year and we have been working on a solution ever since. We’ll be putting a blog and video together to explain in more detail what we have done, but here is a summary. We have created a brand new ‘build system’ which will drastically speed up how quickly we can build and test firmware. One part of this system involved writing hundreds and hundreds of automatic tests which allow a bunch of computers to test DumaOS without any human involvement. Another part is to allow us to trigger new internal firmware builds every night. The purpose of this is to gather all the latest changes our developers have made during the day, build a new firmware and then kick off the automated tests. This means we can catch bugs before human testers ever get their hands on the firmware. The end result of all of this is we can make stable and well tested DumaOS much, much faster than ever before. We’ve been working on this build system for some time and last week, we released a new R2 firmware. It was our very first full firmware built using the new build system, so it’s a bit of a landmark moment for us. Our plan is to now use this new system for all future DumaOS 3.0 firmwares, including XR routers, Telstra Game Optimiser, the R1 etc. It’ll take us a bit of time to tweak it to work with each router, but once done it will become very easy for us to prepare rock-solid firmwares to send to NETGEAR for their testing before then releasing them to you guys. There’s still one sticking point left: the XR300 community. We really do know how far behind you are, and it sucks. All I can say is we’ll do everything in our power to try and bring you up to the latest version using this new build system - I can’t promise it will work, but we’ll do our very best. The last thing to say is we realise we’ve been pretty quiet over the past few months in terms of communication. Behind the scenes, we’ve never been busier. We’ve got some massive features coming out in 2022. Honestly, it’s going to be the biggest leap forward we’ve ever made in our technology and is the culmination of several years of R&D. We’ve also doubled the size of our team over the past 18 months. We know it’s been a long wait, but the payoff will be worth it. Thank you for all the patience on this. We know we’ve got a brilliant user community, we feel very blessed and fortunate to have you. We think you’ll love what’s coming out next and we’ll begin to share more details with you on what we have been up to, so stay tuned. The Netduma Team

SBMM is another factor screwing this game. Now the server matching priority isn't the ping but rather skills. Leaving low latency players on mercy of the lag comp. Also, if you play with cross play enabled cheaters are roaming with no shame in almost every single game. Disabling the cross-platform games means longer waits and more mixed pings.

I remember the PS3 MW days. Planty of hackers but lag was minimal. Today they want to sell this game to everybody, either it's 5ms guy on fiber or 100ms 10 years old on his mommy's wifi. I also remember (long time ago) conversation in Activision COD forums with one of their employees. He said that "you no longer will have the advantage because of your internet". When I asked why, he closed the entire thread.

I've just changed my ISP from cable (75/10mbps) to fiber (1.5/1.5Gbps). Now tests on speedtest.net show 3ms ping. My in-game ping also improved by about 15ms. Should it improve my gaming experience? I hoped so. Unfortunately, not...in fact it got much worse. One on one is an instant death. I don't even see them shooting. I die by what I call look of death. I struggled like this for a week trying different settings on xr1000, PS5 without results. Today, I decided to force my games by geofencing to Europe. Playing 100ms + games made the difference. Now I can see the enemy and have time to react. This is just another example of lag compensation screwing this game. It works by intentionally delaying information about positions of the high ping players in the lobby to low ping players.

Refresh rate is one thing and latency the other. if you enable 120hz refresh rate on your PS5 and your TV/monitor as well as the game support it... then you should play it in 120 hz regardless the ping. you can check it: when in game press PS button, then home, settings, screen and video, then video output information.

I never had problem running the game at 120hz. Actually, I've been playing it with all bells and whistles PS5 can provide: 4k, 120hz, VRR, ALLM and HDR all together When it comes to latency... before season one: in game ping was about 20ms higher than netduma's in geo-filter. Today, it was showing 20ms in game and 15ms in the router, so only 5ms difference, which is the same to what I had in vanguard.

I changed my MTU to 750 on XR1000. To my surprise it run very well. Playing MW2 on PS5 (did not touch PS5 settings). I lowered it before (not as much though), I can definitely say it helps in my case.

Let me to chip into this with some of my own findings. I had the same problems, tried different combinations, with a little success. I checked my MTU settings number of times, always coming up to 1500. Then...I decided not to add 28 bytes after highest number without fragmentation, which is 1472. To my surprise the game run much better, it seemed, like now, I have more time to react then before. I know, there is no much proof, that lowering MTU would improve gaming experience, however it does in my case both in Vanguard and MW2.

I did... back in November last year: XR1000 1.0.0.58, 1.0.0.52 - DumaOS on NETGEAR Nighthawk Support - Netduma Forum

I'm a XR1000 owner and the firmware support at this time is NOT EXISTING. The last time they released the update was in July 2021, it was full of bugs from day one. There is an obvious problem with software support. Everybody should stay away from this model for now.

Yes, I have a Hitron cable modem (no router) connected to XR1000. All my devices are hooked up to the router as follow: XR1000 gets the external WAN IP from ISP as below:

Ok, No Armor always wired (already mentioned, wifi not even set for Ps5) MS edge to access the router no making rules when in game also my ps5 is in static ip

I bought this router to enjoy gaming, not to troubleshoot the problems in a baby steps details. Before you were suggesting, that the TCP prio problem was because wifi and wrong traffic type selection, now it's upnp conflicting with forwarded ports. I never enable both, it's common knowledge on every router. I apricate your help but you can see there are some issues with the firmware. For now I'm playing without forwarded ports, upnp on, traffic prio: basic PS5, game console. It's more simple setup but it has to do for now.

please stop assuming - you wrong again

Ok, once more:) I forwarded number of ports to get open NAT in COD for PS5 (TCP 1935, 3478-3480, UDP 3074-3079, 3478-3479). It played fine for days, then I noticed NAT is moderate again. I went to forwarded ports page, where all the settings were gone. I tried to reenter them, just to get ports conflicting with another service error. Only solution was to revert to factory settings. It happened probably 5 times within the last 3 months on both firmwares. After all router setting were done (wireless, QOS, port forwarding, device manager), I obviously wanted to save it. In Backup page, I would save a copy of current settings in NETGEAR_XR1000.cfg file. Next time, I did the factory reset, when initial setup begins, there is an option to restore the settings from backup. Pointing to my saved cfg file, would start the restoration. Unfortunately, after few minutes nothing gets restored. Traffic prioritization for TCP ports not working because the you assumed I'm on wireless My PS5 is hard wired with 1G cat6 cable, that's why you see "normal default wan" selection. Strange enough UDP ports are being prioritized with no problem. Guys, If you have access to XR1000, maybe you could do some testing, instead shooting possibilities from the hip. If Netgear is responsible - shame on them for this support.

LMAO, Instead of asking these questions and playing detective, why don't you take XR1000 and simulate the problems I described.

No ISP router, just the modem. Trying not to complicate things. Following QOS rules prioritize TCP ports 1935 and 3478-3480 for any outgoing and incoming traffic to and from my console. Unfortunately no single TCP packet shows up:

1.0.0.58 was released in August 2021. The Upnp problem was noticed on this forum right away. 3 months later same crap! I'm not a fan of putting my console in DMZ. It's simply not safe. Besides... port forwarding should not be an issue. I added number of custom prio rules for COD PS5, including TCP ports 1935, 3478-3480 (Duma OS classified games is off). Netduma never show any packets being prioritized. Strange, since The same TCP ports can be visible sometimes in Upnp table.