PUBzZz

I experienced  this on day 1 of launch of bo6 in every single game, I have stopped playing and waiting for the next update to fix these issues which would be likey season 1 update unlikely they will release a hot fix for this before then.
To everyone with this issue, there is nothing wrong with your set-up or anything you can do about it. It's the game, not your Internet or netdumar fault.
The game is broken, some people are just lucky to be on the advantage end of the gun fight they know this and they are abusing it. Reason why I taken a break from bo6 until it's fixed.

ok thank you for looking into it

R3_2024-09-27T12_58_14.619Z_logs.txt

😉
Enregistrement 2024-09-27 143612.mp4    

Pre-ordered can't wait even with my R2 running great looking forward to Dumo OS 4

We need the Duma Dev's to chime in at this point.  I know they busy with 3.0 but I think we need to address why one of the key features of the Duma "Anti Bufferbloat" seems to do more harm than good with MW. Also maybe the Dev's can gives us a detailed list of what they see MW doing port wise for PS/Xbox/PC.  
I can say since I stopped using the Anti Bufferbloat and prioritized those port ranges the game plays much better hit detection wise.  I'm a little mind blown in the difference.  
 

Thanks Fraser.  Yeah I see it just cuts off part of the name so you don't see the ports.  
Got this setup and see how it goes in game.
udp:sport:3074-3075
udp:dport:30000-45000

Yeah I been using different variations of prioritizing over the past week or so to see what gives me the best results game after game day after day.  I have MW on both PS4 and Xbox and test all setups on both.  I just like to ask questions when people throw info out so that I'm clear on what they are saying so I can test it.  
My opinion on this is first and foremost this all starts by not using the Anti Bufferbloat sliders. If you use those that's where the problems start.  Prioritizing the ports is the gravy in all this.  However too much gravy and you mess the meal up.   I just kind of feel the Duma Team could have gave us all this data. I mean they can pull that raw data real quick and break it down step by step for a universal way for everyone to setup.  

Yeah I been using different variations of prioritizing over the past week or so to see what gives me the best results game after game day after day.  I have MW on both PS4 and Xbox and test all setups on both.  I just like to ask questions when people throw info out so that I'm clear on what they are saying so I can test it.  
My opinion on this is first and foremost this all starts by not using the Anti Bufferbloat sliders. If you use those that's where the problems start.  Prioritizing the ports is the gravy in all this.  However too much gravy and you mess the meal up.   I just kind of feel the Duma Team could have gave us all this data. I mean they can pull that raw data real quick and break it down step by step for a universal way for everyone to setup.  

I agree with you 100% with this:  I just kind of feel the Duma Team could have gave us all this data. I mean they can pull that raw data real quick and  break it down step by step for a universal way for everyone to setup. This is the most popular game used by duma and gets their respective router sold. Amen to you brother!

Yeah New York

Yeah I been using different variations of prioritizing over the past week or so to see what gives me the best results game after game day after day.  I have MW on both PS4 and Xbox and test all setups on both.  I just like to ask questions when people throw info out so that I'm clear on what they are saying so I can test it.  
My opinion on this is first and foremost this all starts by not using the Anti Bufferbloat sliders. If you use those that's where the problems start.  Prioritizing the ports is the gravy in all this.  However too much gravy and you mess the meal up.   I just kind of feel the Duma Team could have gave us all this data. I mean they can pull that raw data real quick and break it down step by step for a universal way for everyone to setup.  

Yeah I been using different variations of prioritizing over the past week or so to see what gives me the best results game after game day after day.  I have MW on both PS4 and Xbox and test all setups on both.  I just like to ask questions when people throw info out so that I'm clear on what they are saying so I can test it.  
My opinion on this is first and foremost this all starts by not using the Anti Bufferbloat sliders. If you use those that's where the problems start.  Prioritizing the ports is the gravy in all this.  However too much gravy and you mess the meal up.   I just kind of feel the Duma Team could have gave us all this data. I mean they can pull that raw data real quick and break it down step by step for a universal way for everyone to setup.  

Yeah I been using different variations of prioritizing over the past week or so to see what gives me the best results game after game day after day.  I have MW on both PS4 and Xbox and test all setups on both.  I just like to ask questions when people throw info out so that I'm clear on what they are saying so I can test it.  
My opinion on this is first and foremost this all starts by not using the Anti Bufferbloat sliders. If you use those that's where the problems start.  Prioritizing the ports is the gravy in all this.  However too much gravy and you mess the meal up.   I just kind of feel the Duma Team could have gave us all this data. I mean they can pull that raw data real quick and break it down step by step for a universal way for everyone to setup.  

We need the Duma Dev's to chime in at this point.  I know they busy with 3.0 but I think we need to address why one of the key features of the Duma "Anti Bufferbloat" seems to do more harm than good with MW. Also maybe the Dev's can gives us a detailed list of what they see MW doing port wise for PS/Xbox/PC.  
I can say since I stopped using the Anti Bufferbloat and prioritized those port ranges the game plays much better hit detection wise.  I'm a little mind blown in the difference.