Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 08/07/2019 in all areas

  1. 30 points
    Hi Everyone, We hope you and your families are keeping safe. The virus is going to be a challenge for everybody, but at Netduma we are doing everything we can to power through it. Some of us are now working from home, but we will not let it slow us down in delivering DumaOS 3.0 to you. After all, the quality of your online gaming & home network is an even higher priority than before! We will also be keeping all our support channels open as usual in case you're having any problems. The whole team is safe and we hope you are as well. The Netduma Team
  2. 28 points
    The Future of DumaOS: Version 3.0 UPDATE: Sign-ups are now open for the DumaOS 3.0 beta! More info here: https://netduma.com/blog/beta-signups-live/ Last year we released our first major update for DumaOS, Milestone 1.3. You guys loved it, so we quickly got to work on the next milestone, packing it full of features to make your router even more powerful. This next milestone will instead be a new version, DumaOS 3.0, and it marks the biggest leap forward in our history. It will contain a huge amount of features never seen before on a router. Instead of just sending out each of the features piece by piece, we needed to wrap them all up into one giant release. We will explain why soon 😉 (but don't worry, we're not doing an EA!). We know you guys will want to get your hands on 3.0 as soon as possible and we are working very hard to make this happen. But until we are sure, the release date is ‘to be confirmed’. But in the meantime, here is a teaser one of the many features coming to your router in 3.0: Data History. With Data History you can see how much bandwidth you’ve used over time and drill-down to see which devices and/or applications are eating up all your data or find out how many hours you spent gaming over the weekend. If you are under a data cap, you can also see if you are nearing your monthly limit. This is just a small glimpse into 3.0. We will be gradually revealing more features over the next few weeks so keep an eye out for more announcements. One final thing, we launched DumaOS Insiders yesterday. This will be a private subforum where we share first-looks at features we are currently working on and using your feedback to shape them. There are only a few spaces left, so sign up here if you haven’t already: https://forum.netduma.com/topic/29480-sign-up-to-dumaos-insiders/ Big things are coming. Thank you for your support. The ND Team
  3. 19 points
    Netduma Jack

    Sign up to DumaOS Insiders

    EDIT: The response to to this has been brilliant. Thank you. We are now locking signups - but we will leave the form up in case anyone wishes to register their interest in becoming an insider in the future. ___ Hi guys - we have a big announcement coming tomorrow about our next development milestone, which will be the biggest set of new features ever released for DumaOS. Our number one focus is building new features, and we want them to be the best they can be. This is why we're starting up DumaOS Insiders, where we will be sharing exclusive first-looks at some of our new features and using your feedback to shape them. If you are interested, please sign up to DumaOS Insiders using this form: https://forms.gle/4TptvkBkqBfVeW669 When you sign up you will be entrusted with exclusive Insider information. Please do not share this content outside of the DumaOS Insiders subforum.
  4. 14 points
    RedBull2k

    Caddy 1.2

    I thought i would start this off with its own thread. I have expanded slightly from my first app, screen shots are below. now you can save and load your allow and deny list. This is very ideal if you have to factory reset. plus sharing of lists is possible. you can clear your allow/deny list with a single click. for those of you who are fed up of seeing your offline devices can with 1 click remove all offline devices that no longer hold an ip address you can also create your own custom black/whitlist just make a text file named with the following Server_Blacklist.txt Server_Whitelist.txt Peer_Blacklist.txt Peer_Whitelist.txt and insert ip addresses, only 1 ip address per line for example from where ever this file is saved just drag and drop into the white box, this will automatically add here is the file caddy 1.0 caddy 1.1 caddy 1.2 @Mobel @GHOST-1-EC @TrayDay @MikeyPython @Sable @WalkedDave @Bert @Locosano @Sherman85 @DanyKTM @Zippy @Grafti @Fuzy @[email protected] @HaBlo0
  5. 9 points
    I HAVE UPDATED IT FOR COD MW READ JUST BELOW HOPE ITS NOT TO CONFUSING BUT THIS TOPIC WAS STARTED A LONG TIME AGO It also now shows you how to traffic protize cod mw ports 2019 below I WILL POST COD MW PORTS jUST BELOW HERE these are the ones i found so far i will keep updating it with new ones here I recently upgraded to new dumar os fw and think its great but its missing one thing important i think In network monitor it now does not show you what ports the game you play is connected to uses In cod bo4 now cod mw 20019 i used this feature all the time In cod bo4 same for cod mw19 everytime you would join a new lobby it would show us new ports it was connected to. You would always be connected to two ports in every game this first port is always port 3074 udp the second was always diffrent ever new lobby you join uses diffrent ports If you stayed in the same lobby for an hour the two ports would be the same for an hour or how long you stayed in that lobby . Once you change lobbys the game changes ports it uses so you need to put new ports in traffic priortaztion I think this is why the connection keeps varying For cod mw 2019 its now three ports instead of two HERES WHY ITS IMPORTANT when i put in the ports it uses for that game in traffic priortization my hit registration would get a lot lot better i did this before on cod ww2 now i do it for cod mw2019 and it helped my hit registration .And on cod bo4 Somtimes i would do this during a game. i would be playing a game and struggling to get a kill then in same lobby same people playing i would enter those port number in and the hit registration was great easier kills same for cod mw2019 EVEN IF YOUR NOT PLAYING COD you still might need it for other games. i used it for all my other games to help get a better connection and i would like to use it in the future for new games I really dont wanna downgrade to an older fw just to use this feature as it was so GREAT SO ANY GAME YOU WANNA SEE WHAT PORTS IT USES YOU NEED THIS As some games it dosent tell you all the ports it uses I would love to use this for red dead redemption 2 online when its released soon Fraser told me if enough peole want this feture back in the firmware they would put it back in SO I JUST PUT A POLL UP SO PLEASE VOTE THANKY YOU So i am asking any who might use it before or might wanna use it in the future please vote on the poll here if you would like to see it in i future update I hope i made sence sorry for any typos And please post to say you would like it the more people who say they want it they saidthey would reinstall it if the demands there Thanks i have now edited to update for cod mw READ FROM HERE for cod mw 2019 and how to set up ports correctly From members who know how to set it up correctly below RL317 shows how to in this post below He knows more about it than i do ahe advised me how to set it up correctly Just letting you guys know i think now playing cod mw that the next update that the dumar has has to reinstall the older network monitor My hit detection \hit registration is now brilliant since i done these steps Heres why If you want your hit registration or hit detection to be great read this When playing cod mw the game uses 3 ports to play thats if you want godd hit detection \hit registration The first is port 3074 this is on ps4 i think its 3075 on xbox but i am not sure i dont know about pc The second port stays the same untill you restart the game i think this is the data centre or either matchmaking The 3rd port is changes every new game this is the dedi or peer your playing on Thats why you see new people every game and thats why you do good one game but not the next Thats because you changed dedis and the ports have changed So thats why you need 3 ports every game the first is 3074 the send is the matchmaking or data centre the 3rd is for the game mode you play Atm i am making a list for the ports it uses Just letting you know you can do this yourself to see what ports is needed but you have to downgrade to the older firmware well thats on netdumar1 I dont know about other routers Also this cane be done if you have a router with openwrt on it You would have to ask admins as i dont know anything about the other routers Heres a way to put the ports in traffic priortization Source 3074-3075 destination 30000-45000 udp rule 1 Source 30000-45000 destination 3074-3075 udp rule 2 Source 3074-3075 destination 3100-3500 udp rule 3 not nessasery optional Source 3100-3500 destination 3074-3075 udp rule 4 not nessssery optional HERES A LOAD OF PORTS TH GAMES COD MW USES Heres is a copy of my upnp settings screen after playing a losd of cod mw 2019 192.168.88.119 9308 9308 192.168.88.119 UDP DemonwarePortMapping 3074 3074 192.168.88.119 UDP DemonwarePortMapping 3163 3074 192.168.88.55 UDP DemonwarePortMapping 3153 3074 192.168.88.55 UDP DemonwarePortMapping 3172 3074 192.168.88.55 UDP DemonwarePortMapping 3184 3074 192.168.88.55 UDP DemonwarePortMapping 3155 3074 192.168.88.55 UDP DemonwarePortMapping 3123 3074 192.168.88.55 UDP DemonwarePortMapping 3102 3074 192.168.88.55 UDP DemonwarePortMapping 3148 3074 192.168.88.55 UDP DemonwarePortMapping 3111 3074 192.168.88.55 UDP DemonwarePortMapping 3124 3074 192.168.88.55 UDP DemonwarePortMapping 3131 3074 192.168.88.55 UDP DemonwarePortMapping 3150 3074 192.168.88.55 UDP DemonwarePortMapping 3192 3074 192.168.88.55 UDP DemonwarePortMapping 3176 3074 192.168.88.55 UDP DemonwarePortMapping 3125 3074 192.168.88.55 UDP DemonwarePortMapping 3129 3074 192.168.88.55 UDP DemonwarePortMapping 3177 3074 192.168.88.55 UDP DemonwarePortMapping 3115 3074 192.168.88.55 UDP DemonwarePortMapping 3162 3074 192.168.88.55 UDP DemonwarePortMapping 3116 3074 192.168.88.55 UDP DemonwarePortMapping 3147 3074 192.168.88.55 UDP DemonwarePortMapping 3134 3074 192.168.88.55 UDP DemonwarePortMapping 3133 3074 192.168.88.55 UDP DemonwarePortMapping 3100 3074 192.168.88.55 UDP DemonwarePortMapping 3109 3074 192.168.88.55 UDP DemonwarePortMapping 3095 3074 192.168.88.55 UDP DemonwarePortMapping 3127 3074 192.168.88.55 UDP DemonwarePortMapping 3190 3074 192.168.88.55 UDP DemonwarePortMapping 3117 3074 192.168.88.55 UDP DemonwarePortMapping 3126 3074 192.168.88.55 UDP DemonwarePortMapping 3084 3074 192.168.88.55 UDP DemonwarePortMapping 3182 3074 192.168.88.55 UDP DemonwarePortMapping 3138 3074 192.168.88.55 UDP DemonwarePortMapping 3175 3074 192.168.88.55 UDP DemonwarePortMapping 3171 3074 192.168.88.55 UDP DemonwarePortMapping 3165 3074 192.168.88.55 UDP DemonwarePortMapping 3180 3074 192.168.88.55 UDP DemonwarePortMapping 3169 3074 192.168.88.55 UDP DemonwarePortMapping 3085 3074 192.168.88.55 UDP DemonwarePortMapping 3105 3074 192.168.88.55 UDPDemonwarePortMapping 3194 3074 192.168.88.55 UDP DemonwarePortMapping 3074 3074 192.168.88.55 UDP 192.168.88.55 9308 9308 192.168.88.55 UDP Btw i noticed everytime i reset cod mw 2019 these more was added they were added one at a time So i thought these ports are needed as well but now i think there optsinal Here are the ports network monitor shows are in use for cod mw 2019 i will add more when i find them 30410 35710 30350 31300 35300 37160 31350 36360 32700 32710 39860 38280 39500 42420 43300 30040 30080 32560 31080 32540 30110 30020 30030 30070 30230 30500 30600 31030 32930 33640 34260 36050 36290 36930 39550 43610 43840 44790 30020 :30010 :32680 32310 :32350 :30190 :34790 :34790 :30070 30100 32560 :32580 30060 33420 33420 40820 36800 32310 30550 30520 30130 30060 35310 32550 30040 30310 30160 32590 39300 32460 32490 32550 35800 3258032570 These ports made into a range by east so thank you to them They have a brilliant guide on these forums i recken you guys read it I think its the best one Please if you found this helpful please vote this thread was started over a year ago and we are still have no clue if there gonna bring it back SORRY IF I DOUBLE POSTED A FEW PORTS TWICE BUT I HAVENT HAD TIME TO EDIT THIE LIST YET BTW ANY PORTS LISTED BELOW HERE ARE FOR OLDER COD But you can still see how the people use traffick prortization correctly you just input your ports instead of the outdated ones
  6. 9 points
    I've now owned the XR500 for 1.5 years and to this day: No IPv6 without killing off the QOS. No USB printer support. Incorrect network activity stats. No control over VPN settings. Bugs and glitches in the management GUI. Very questionable QOS performance is some games. Very poor update support. At this point this product should be considered as abandonware. Netduma's/Netgear's lack for transparency with such a vocal community is truly disturbing. There are other manufacturers with devices out there that have a much more active support than Netgear/Netduma and according to my preliminary research, as good, if not better implementations of QOS and AQM. I am no longer actively using this router and will soon be totally replacing it. Hats off to those of you who will be sticking around for the long haul, still beta testing a 2 year old AC router.
  7. 7 points
    IPV6 is coming! We’ve got it working on our development units
  8. 6 points
    Zennon

    ANNOUNCEMENT: The Netduma R2 is here

    Congratulations on the announcement to all of the Netduma staff.
  9. 6 points
    Checking email for 15 days.
  10. 6 points
    We're still planning on doing the announcement today, it'll be a bit later though... About 8pm UK time? I know it's late but we're rushing here to get everything ready!
  11. 5 points
    xolhid

    COVID-19 and what it means for Netduma

    Would you please stop using that word in this context. It doesn't mean what you seem to think it does. You have been saying that for nearly a year. All you are doing by using that word is creating false hype. It's inconceivable.
  12. 5 points
    PUBzZz

    how to get better hit detection

    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.
  13. 5 points
    Be respectful to one another, mobel is Just trying to help, he is giving you decent advice, although it isn’t helping your situation.
  14. 5 points
    bagsta69

    MW4 open nat PS4

    Hi all, I played the Alpha and had moderate nat type, Just played a few games on the beta with moderate nat and did a few changes to get open nat. Playstation static Ip adress Turn off upnp TCP and UDP external and internal port range 3074 =NAT TYPE OPEN
  15. 4 points
    willphule

    ANNOUNCEMENT: The Netduma R2 is here

    YES, YES & YES!!! So happy to see this! 😁
  16. 4 points
    I'm not saying that, we just want it to as bug free as we can make it. The more people that test it the more bugs will be found.
  17. 4 points
    Netduma Alex

    DumaOS 3.0 Beta

    I think the first few people have been invited to the XR500 beta so I imagine the emails will start rolling out more widely very soon.
  18. 4 points
    pollutionblues

    Auto ping vs in game ping

    In game ping meters add processing delay etc. All games do this, that is why the in game ping is higher. Auto Ping is your direct ping to the server and this is what you should focus on as it is what you can control.
  19. 4 points
    So for anyone wanting information on FW updates and support for updates should be posting over in the NEGEAR forums: https://community.netgear.com/t5/Nighthawk-Pro-Gaming-Routers/bd-p/en-home-nighthawk-pro-gaming-routers Stop bugging NetDUMA about FW updates. XR routers are NETGEAR products, not NetDUMA. NETGEAR only uses NetDUMA as a 3rd party developer for this series of routers and uses a portion of DUMAs code to include in NETGEARs FW. If you want information about the XR series FW, post over in the NETGEAR forum. Up to NETGEAR to update there FW and test it out and release it. It's NETGEARs routers and ball game when it comes to there products. And don't forget, since this CD19 virus has slowed and delayed current events and business progress, the end results and release times maybe delayed as well. Many people and businesses are being effected. For those interested, there maybe a beta version for some XR series which you'll need to contact the NETGEAR forum moderator there to gain access too. So far I've only see a beta for the XR700. Something to inquire about and see if maybe there is one for the XR450/500 series if your so inclined to do so. Any router mfr doesn't have to or is required to divulge when new FW maybe forth coming. Been like this for many years. EOL!!!
  20. 4 points
  21. 4 points
  22. 4 points
    We've made notes of everyone who has expressed an interest in the beta. We may make an official list closer to the time for people to sign up to.
  23. 4 points
    Nice gameplay against Level 155 TryHards in SnD, they were trash talking in lobby before the match lol.
  24. 4 points
    Killhippie

    Devices not showing online

    Isn't it a known bug, Alex? There have been a lot of people with this issue including myself. Hopefully one that 3.0 will fix, even though Netduma haven't actually patched it, just re wrote it so it now works (isn't that technically patching?) from what Fraser said and of course if I got the gist of what he was saying correct. Looking forward to seeing these bugs vanish with DumaOS 3.0.
  25. 4 points
    I'm sorry, but I've never seen such a lack of competence with firmware updates. Other companies release firmware updates on frequent bases, but the response that we hear over and over and over at Netduma is "Were have a lot of features in the pipeline, but we don't know when Netgear will release them". Literally half a year will go by with the same nonsense. You guys really need to revise your business model. Releasing firmware updates every 2 years? Seriously?
  26. 4 points
    Im certain i got it now. this is the boy that is right.
  27. 4 points
    Netduma Alex

    Were these routers given up on?

    I don't know how much i'm allowed to say regarding which hardware we'll put DumaOS 3.0 on due to legal mumbo jumbo that i'm restrained by... What I will say is that we're not dropping support for any existing hardware, and we're planning to release DumaOS 3.0 for every current DumaOS device. I can't promise it yet, but that's what we're planning on.
  28. 4 points
    We're not going to give away any details outside the previews we show Insiders and in announcements but you'll be very pleased with what we have in store for 3.0!
  29. 4 points
    Netduma Alex

    New profile fields

    I just made a few small changes to profiles. It is now mandatory to specify which DumaOS routers you own. You will be asked this question when you next sign in. This will help us loads with tech support! There are now optional profile fields for Discord, Steam, PlayStation Network, Xbox Live, Nintendo Switch and Battle.net - please suggest any more you would like added Some old/outdated protocols were removed, such as MSN, ICQ, AIM and Jabber. Thanks for being a part of the community! EDIT: I'll add Twitter as well EDIT2: You can now use Facebook to login to the forums if you feel like it
  30. 4 points
    If we do that we'll let you know. For the moment keep an eye out for more feature teases over the next few weeks.
  31. 4 points
    Netduma Alex

    Sign up to DumaOS Insiders

    You can thank Jack for that He's also just spruced up the icons on the forums
  32. 4 points
    Well make sure you keep an eye on the forums over the next few months, and also make sure you're signed up to the newsletter, because IF we had any amazing new products to announce, and i'm not saying we do, but IF we were to announce an amazing new product that was so sexy you'd have to buy it instantly, we'd certainly make sure everybody knew about it via the newsletter. https://netduma.us11.list-manage.com/subscribe/post?u=87a7aef5725cff4be341f1b26&id=5341b993d5
  33. 4 points
    People need to realize that the ultimate owner of the XR series IS NetGear. If you want to keep complaining and nagging, then you should be discussing this over on the NetGear forums and or filing support tickets. NetDuma is only the 3rd Party or Co-Developer for a portion of the FW that is developed and marketed BY NetGear. NetGear holds all the plans, policy's and release dates of when actual FW updates that go to public. It's up to NetGear and NetDuma to work together in getting code fixed based on which side of the code needs fixing. If there is problems with the NetDuma portion, then NetDuma needs to get this corrected then handed back to NetGear. If there are problems on the NetGear side of the fence, then NetDuma has nothing to do with it and NetGear needs to make the corrections. However NetGear needs to know what all the problems are first and foremost. There's a long processing and development and in house testing that needs to be done. So this can take a long time, several months. So FW just cant' be released willy nilly based on users complaints and nagging. If there are legitimate complaints, users need to post about these in the NetGear forums as well as NetDuma and troubleshooting should be performed to narrow down where the real problem is and also might find out which side of the fence it resides. I most cases, this will be NetGear and they need to see and review ALL information to determine who needs to take corrective actions. IMO, most of you people are barking up the wrong tree. If you want to voice your opinions and complaints, you need to field them with NetGear first. They hold the entire responsibility of the XR series. It's there product. If this was a NetDuma R series router, then you would be in the right right tree. Please give NetDuma a break on this. They can only do so much and say so much. There are reasons why the public gets limited information about FW updates and product releases. This is business and how router business is ran. Be patient and show some understanding.
  34. 4 points
    CrossFitKila717

    Need Help With XR500

    I gotcha man.......go to “firewall” tab, then you’ll see “IP Passthrough”. Click that & choose device (xr500 should show up). Select that and select “fixed” on the other drop down. It’s pretty much that simple. There’s only IP Passthrough not Bridge mode. Restart your device under “device” tab, then your console. Should see “open” NAT as well. Make sure to turn your WiFi off on the gateway as well, assuming you’re using the WiFi from xr500. All port forwarding done through the xr500 as well.....don’t do any funky things to the Gateway, just leave that as is......remember, it’s just passing your IP through it. All control is at xr500.
  35. 4 points
    Bullshit, skill is long ago gone in COD. COD is very connection depending. If someones server sync is better than yours, no matter what you'll lose the gunfights all day long.
  36. 3 points
    Pre ordered with part of my stimulus check 😁😁
  37. 3 points
    Bert

    NETDUMA R2

    To be honest, the tech specs are not that impressive. The XR500 / XR700 probably have better hardware. It is a step up from the R1 though and really for $150 is a good chunk cheaper than the XR line. One advantage I can think of though is that the support from Netgear is lacking and with the R2 you would have support straight from Netduma.
  38. 3 points
    Newfie

    ping-lag-shoot 1st die 1st

    I did, I spent even more on the RAX120. There comes a time if you get issues and you don’t get the performance you want and that includes hardware for better coverage it’s time to move on. I’m not alone on this either. You could sell the the 500 on and take a hit and move on.
  39. 3 points
    I said back in 2018 when the R1 Beta was launched that Netduma needs to communicate with the community to avoid impatience and general frustration. I feel both Netduma and Netgear needed to send out an email immediately after a potential beta tester registered to indicate in which wave(group) they are and which estimated date their waves download links will be sent out unless there's some major issue. This kinda leads me into my second point that if they wanted to alpha test the software with a limited control group they should have done so without notifying the community that there's a beta (you don't dangle a bag of candy asking the class who wants some and then just share with your friends).
  40. 3 points
    TryHardUndies

    27 k/d MW Gameplay

    Why post non-Netduma gameplay on a Netduma forum?
  41. 3 points
    MikeyPython

    Caddy 1.2

    Try upgrading your gaming chair. That sees to do the trick.
  42. 3 points
    MikeyPython

    Caddy 1.2

    About to try it in the next thirty minutes. Thank you @RedBull2k I’m sure I can speak for all of us involved here since you brought out your first version. It’s awesome. They have all worked great so far, and you continue to upgrade it with more detail. Not many people would help out a community like you are doing without asking for anything in return except for feedback.
  43. 3 points
    TeCNeEk

    New XR500 owner needs big time HELP!

    Thanks for that! A technician is coming tomorrow so I will find out how everything goes.
  44. 3 points
    Bat 'n' Ball

    XR500 freeze? Logs?

    Hi Netduma Fraser, Thanks for your reply. If I have issues again, I'll follow your suggestions and post back to this thread.
  45. 3 points
    So i finally figured it out after i had to factory reset my phone. When i did this i started getting no internet at all for my phone , even after a delay. I set everything to static and hard set my dns to google. After i did this i had internet instantly. After a bit of fiddling i figured out it is indeed my PiHole acting up(seems like my new ISPs way of doing stuff puts off my pihole, as before it had no problem). I am very sorry for wasting your time, you very correct from the beginning. All i had to do was set my dns to a set one other than pihole on the phone AND flush my internet settings (seems like the pihole dns was getting cached so just changing without flushing didnt help, thats why i didnt notice. It stucks even through phone resets). Thank you so much and sorry i wasted your time.
  46. 3 points
    Is there something you would have liked to see or hear that we didn't mention? If you're having issues with the router just make a new topic and we'll be glad to help.
  47. 3 points
    Thanks for the feedback. I appreciate it's frustrating to have to wait so long for an update, but I assure you that this upcoming version update is totally real, and totally on track. Regarding the XR500, why would we want to leave this update off our most popular product? We are planning on releasing this update to every DumaOS router. We can't promise that it will be a simultaneous release, but any delay would only be caused by time constraints. We would not use a delayed release as a marketing ploy. Bear in mind that the XR500 is by far our most popular product so it's going to be a priority for us. Regarding lack of updates so far, I will say that the vast majority of routers only get bug fixes and security updates. We are bringing a massive update that will add many new features and will represent a huge leap forward for DumaOS, and it will be provided to all existing customers free of charge. How many routers have you had that received an update that overhauled the entire experience and made your router feel like a brand new product all over again? That's what 3.0 is doing to do. Anyway, i'm sorry that you won't support us any longer, but I hope that you'll take another look at us once 3.0 is released.
  48. 3 points
    Netduma Alex

    Sign up to DumaOS Insiders

    Everybody's welcome to join while applications are open!
  49. 3 points
    Bert

    Must Be Magic?!

    Not even throttling but there is instances where the lagger can gain the advantage simply due to in game mechanics. If I play at 150ms and you at 4ms. Assume the game has approx. 50ms interpolation lag for 60Hz servers. We are playing on Freqency. You run through the middle, I camp one of the hallways on either side of the map. As soon as I come out of cover and aim and shoot at you, this needs to be put in an update by my console, 0-16ms, send to the server, which takes 75ms, they need to process it in the master gamestate, which takes 0-16ms in theory (time between 1 update) then it gets send to your console, which takes 2ms. Then this gets processed by your client, 50-83ms interpolation lag (time between updates and frame rounding. in the best case it takes 127ms for me to be visible on your screen, worst case it will take 192ms. Average, 160ms. If I use a gun that kills in 300 ms I can have killed you before you finished raising your gun. Also in the above example, in CoD damage is dealt directly, so there is no interpolation delay, but there is a delay for it going in the update to the server, 0-16ms. So actually you would receive damage after just 0+75+0+2 = 77ms best case, or 16 (update rate)+75+16+2+32(frame rounding) = 141ms. So you can actually start recieving damage or be instakilled before I even appear on your screen fully. Also, my shots lag but register at the server after 75ms best or 107ms worst case scenario. What a lot of people forget that with high latency connections, that it gives the lagger a window to shoot at you without having flinch, because you can't shoot back yet. Where it hurts him is that hitmarkers will come at a delay. If situation above was reversed. You would come out of cover and this would be visible to me after 2+0+75+50 = 127ms best case or 16+2+16+75+83 = 192ms. Same numbers. But you fire and your shots hit at the server in 2ms best or 18ms worst case scenario. So I would already be dead at the server before I even see you moving. Now 2 players that both have 4ms to the server: Best case for coming out of cover: 0+2+0+2+50 = 54ms Worst case for coming out of cover 16+2+16+83 = 117ms Average, 85ms delay. You you see, it's not just your ping, but the other guy's ping plays a big role in the gunfight. And this is assuming clean connections which is usually not the case in a online environment. And a server that is not limited by CPU cycles etc etc. If you do the math for LAN with no latency then you will see that it's still not 100% fair. In reality. Most of the times latency is not symmetrical. And game updates are not recieved in exact 16ms intervals etc. Server can be at max capacity. It can go on forever. Low ping just means that you have the lowest possible path to the server. Less hops in between so the least chance of something going wrong. You have the advantage when coming out of cover and in straight up fights. But there is times where you are disadvantaged.
  50. 3 points
    Does it include bug fixes for DumaOS in between milestone launches? Because all the new features in the world wont help if you don't patch the bugs that exist after updates, like the bugs that never got patched in milestone 1.3 and were not patched in the last update for some unknown reason, I mean Netduma did have 8 months to fix these. There has to be a change of direction in patching DumaOS bugs, there are still major bugs from December 2018, which result in people having to turn off QoS like the VLAN tagging bug for instance. These bugs are still causing people issues 8 months into Milestone 1.3 and that's after that's a recent update too. No new feature set in Milestone 1.4 will fix what is pretty much a non existent patching cycle for bugs in DumaOS. I really hope you have thought and worked on this aspect of DumaOS's life cycle in tandem with Netgear, otherwise nothing has really changed no matter what you add feature wise. Maybe you need to slow down creating new feature's and concentrate on fixing the broken ones first?
×
×
  • Create New...