PUBzZz

Hi Fraser, Can I please get early access to the beta firmware also? Thanks, Chris

Hi, Can I get access to the beta please. Thank you, Chris

ok thank you for looking into it

R3_2024-09-27T12_58_14.619Z_logs.txt

where do I get the logs?

on that speedtest it's 29ms on the ping optimizer it's 15ms both

yes, I can access that site. Speed test there is no issues.

Yes, All speed test work only site that didn't was DSL Reports. I tried Speedtest.net and Waveform.com. At 100% I get a little above my advertised speeds for both up/down no issues. When I turn on congestion controls speed test reflect those changes no issues there either. Just when trying to use ping optimizer it only test 100%. Modem Router is ZTE F680

Hi Fraser, So I just moved and switched to a different internet provider. On my old service, Ping Optimizer worked as it should. However, now with my new internet when running ping optimizer it tests at 100% over and over and says "Can't be reduced". I have my Duma R3 setup in the DMZ of my new Modem/Router. Is there anything else you think I need to change or add to the router to correct this issue? Thanks

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

no adblocker. using http://192.168.77.1/ to access duma os page. It started happening again today.

actually, it's happening again. So it's no longer showing any servers on the geo filter and filtering anything out. Any ideas? RPC error 'ERROR_UNKNOWN': Unterminated JSON encoded object found at position in [] -> stack traceback: ?: in function <?:73> [C]: in function 'assert' ?: in function 'decode' ?: in function <?:123> ?: in function <?:370> [C]: in function 'xpcall' ?: in function 'try' ?: in function <?:334> [C]: in function 'run' ?: in function <?:427> [C]: in function 'xpcall' ?: in function 'try' ?: in function <?:268> (tail call): ? ?: in function <?:39> [C]: in function 'xpcall' ?: in main chunk [C]: ?

It just started last night. However, it seems fine now. Rebooting did help last night but I guess the pc being off overnight fixed the issue for me. I spoke too soon.

I keep getting this pop up on the geo filter page every few seconds. Any idea how to get rid of this? RPC error 'ERROR_UNKNOWN': Unterminated JSON encoded object found at position in [] -> stack traceback: ?: in function <?:73> [C]: in function 'assert' ?: in function 'decode' ?: in function <?:123> ?: in function <?:370> [C]: in function 'xpcall' ?: in function 'try' ?: in function <?:334> [C]: in function 'run' ?: in function <?:427> [C]: in function 'xpcall' ?: in function 'try' ?: in function <?:268> (tail call): ? ?: in function <?:39> [C]: in function 'xpcall' ?: in main chunk [C]: ?

I think at this point we have done all we can do with improving our in game experience. MW uses 3 different types of Netcode and it's random as to which version will be used in your game as it's game by game. Next you have to deal with the SBMM which in no way prioritizes connection which again creates more randomness for us. It will be interesting to see how this game plays a month or two from now when the player count drops off as it will stretch the SBMM even further.

@kinel The last thing I got from A7 back then was this. Hypertraffic Udp:bothport: 3074 Udp:bothport: 3076 tcp:dport:443 He used "Reactive" with 88/88 on the sliders His internet package was 120 down / 2.5 up port forwarding 3074-3076 udp 9307-9308 udp

Nevermind

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

Ok so how did you do the 30000-45000 in hypertraffic?

@kinel I just downgraded from DumaOS back to the Original Firmware so I can do some testing. I don't feel like search through all the post of your but how did you have your "prioritizing" written in the original firmware? I forgot that hypertraffic was a bit limited compared to traffic prioritizing in the DumaOS.

your chasing a Ghost. His settings aren't going to help you as it's clear this was all netcode related.

He's actually saying he likes the original firmware not the DumaOS. So you going from the DumaOS on the 500 to the DumaOS on the R1 is kind of the same.

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.

@blackfirehawk So in your opinion the only thing we should have in the Traffic Prioritizing section is for 30000-45000? Is this how you have it entered? Source 3074:3074 - Destination 30000:45000 UDP Also are you doing any port forwarding or just using UPnP?