sidestep6
R3 Early Access-
Posts
44 -
Joined
Basic Info
-
Interests
The R1's Pre-Emptive QoS is God-Tier, bring it back Netduma.
-
DumaOS Routers Owned
Netduma R1
Netduma R2
Netduma R3
Gaming
-
Connection Speed
Don't know/Won't say
Recent Profile Visitors
1,690 profile views
-
Where is the new firmware? 4 Months is too long.
sidestep6 replied to Freshjive's topic in Netduma R3 Support
Netduma didn't do their "Due Diligence" with the R2 or R1 when they were launched what in the world makes you think they'd get it right this time? Don't get me wrong I'm not agreeing with him I'm just pointing out that anyone who has previously purchased a Netduma OS router should already be aware of their track record and how slow they can be. A lot of people myself included probably forgot about the R2's launch, for my purposes I couldn't really use the R2 until over a year after it was released. Is it weird for a company to release a device in a state that makes you question whether it was ever tested before release? Sure but until there is a direct competitor that releases a device with the same features in a similar simplified and convenient way they have no real competition so they don't really have to change the way they work or do business. -
Hard to tell with consoles and the latency at the top said n/a so wasn't sure if things were setup correctly.
-
sidestep6 reacted to a post in a topic: R3 Stuck on bootlop first time booting
-
Wired or wifi for your console?
-
carmine19 reacted to a post in a topic: Feedback on 4.0.23 Beta
-
Yes even when it can't stabilize it shows increased ping in game, it does this for any game even World of Warcraft, it probably does it for any activity using UDP. It wouldn't be so bad if it functioned like you explained where it doesn't increase ping when it can't stabilize but since it doesn't function that way and it's always on it should at least respect whatever the user has defined for the slider under the Expert area of Steady Ping. Then you could make it function like I mentioned before as a generalized buffer to artificially increase your ping or not by adding 0 to the slider as the lowest possible buffer size.
-
sidestep6 reacted to a post in a topic: Feedback on 4.0.23 Beta
-
sidestep6 reacted to a post in a topic: Feedback on 4.0.23 Beta
-
As far as I can tell with how you have DumaOS 4 setup for PC players if they go to the Geo Filter and try to add their PC it adds it differently than if it were a console or pretty much any other device. It shows the following screen: So when trying to add your PC that you play games on it makes you select a specific game when adding it as a device under the Geo Filter. This means you have to add it over and over again for every game you play in order to get Steady Ping to work for your PC, well that is assuming it would work. Like I said it doesn't appear to work for Frostbite games like Battlefront or Battlefield it never stabilizes and even though it never stabilizes it still increases the ping. The fact that it still increases ping even though it never stabilizes leads me to think it's either flawed design or a bug and as I mentioned before it increases ping for other games not listed or supported which makes it seem like Steady Ping is just always on or always messing with your latency regardless of what you are doing. I think this is a bad approach. I see it on routers for other companies and adding gaming specific features that are specific to a list of games. What if it stops getting updated by the manufacturer? What if it doesn't support some slightly older but really popular games (WoW)? While yes it's an interesting feature if it's so specialized or specific to only certain games isn't it going to cause more harm than good? Don't get me wrong in this case with "Steady Ping" I'd like it to work for everything, just make it a generalized buffer for the device added instead of tying it to specific games. Why? Because being able to artificially increase my ping in a game would give me an advantage in some games with bad lag compensation. I am curious if you guys knew that when first implementing the feature since it seems like that is the intended purpose with the slider.
-
oh wow they made that way less intuitive than it was in the previous OS
-
I mean exactly what I said. Even when setting up prior to launching the game it doesn't function or work correctly. I have yet to see it stabilize with Frostbite games like Battlefront or Battlefield and no major fluctuations to indicate why it is never able to. My guess was you guys are writing off PC players again especially when this version of DumaOS doesn't let us tell it to consider PCs as a console device. Your wrong in this case, it isn't able to stabilize and it still adds around 10 ms of ping. The only way to stop it from doing so is to manually disable Steady Ping. Oh and even when playing a game not supported by Steady Ping it still adds to your ping which raises even more questions.
-
It doesn't even work for the game's listed under the same area of the Geo Filter for when adding devices. Or maybe it doesn't work for PC players, hard to tell. Also not sure why the slider is there for the Expert area of Steady Ping since it doesn't matter what it is set to. With the few games I've tried all it does is increase ping by 7-10 ms regardless of what the slider is set to. It's like it ignores it entirely and if Steady Ping is never actually able to "stabilize" why does it still function or act like it is enabled by increasing your ping? If it can't do it shouldn't it automatically disable that part? Otherwise it's just inflating your ping for no reason is it not?
-
sidestep6 reacted to a post in a topic: Higher Base Ping
-
sidestep6 reacted to a post in a topic: Higher Base Ping
-
ANNOUNCEMENT: The Netduma R2 is here
sidestep6 replied to Netduma Admin's topic in News & Announcements
So then it's as I said, misleading or isn't an in house solution for the QoS as someone from Netduma already confirmed Reactive or what was left after Preemptive was removed is a variant of codel. -
ANNOUNCEMENT: The Netduma R2 is here
sidestep6 replied to Netduma Admin's topic in News & Announcements
So "Preemptive" is coming back? Otherwise what you said is a bit misleading. -
raf1212 reacted to a post in a topic: ANNOUNCEMENT: The Netduma R2 is here
-
Nalsano_ reacted to a post in a topic: ANNOUNCEMENT: The Netduma R2 is here
-
ANNOUNCEMENT: The Netduma R2 is here
sidestep6 replied to Netduma Admin's topic in News & Announcements
What is the actual CPU specs? It just lists "Multi-threaded Dual Core Processor" under the tech specs. I'm just curious how it stacks up against the Netgear lineup. -
Zippy reacted to a post in a topic: Announcement: DumaOS Development Milestone 1.3
-
Yes I understand Netduma can't maintain or handle deadlines of any kind you guys as a company have proven that many times. But still over 3 years since that blog post and the endless mentions of "it will be included with the new DumaOS" and teasing from you about how great those features are compared to current industry alternatives on here and Twitter make it frustrating when those kinds of features aren't base features or core to this new OS especially when they would have a greater affect on a players connection than the majority of the features included. It would be nice to know how many years we'll have to wait for those features to be included so we know when upgrading will actually be worth it. Although considering Netduma's usage of the word "soon" and the fact that the features aren't in the beta build 2 years minimum is probably accurate.
-
HaBlo0 reacted to a post in a topic: NEW FIRMWARE OUT (Netduma R1): DumaOS Development Milestone 1.3
-
FQs19 reacted to a post in a topic: Announcement: DumaOS Development Milestone 1.3
-
Announcement: DumaOS Development Milestone 1.3
sidestep6 replied to Netduma Luke's topic in News & Announcements
When will the anti-jitter anti-spike features be implemented in the DumaOS? Currently they aren't in the beta build. -
That sounds like the bug from the previous version that wouldn't save some settings through a power cycle unless you did a software reboot prior with all the settings you had configured the way you wanted them. Just pointing it out in case it is the same bug as it would be great to have it fixed in the new OS.