Jump to content

Kerry Aldae

R3 Early Access
  • Posts

    13
  • Joined

  • Last visited

Everything posted by Kerry Aldae

  1. precisely why R3 is unfit for gaming. R2 doesn't usually disconnect during MTU or subnet changes. For you, (not team as i've never spoken with them), to think that default subnet is always the correct subnet, proves that you are new to networking. or have a one dimensional understanding of networking. disconnects are always an issue for anyone. hence the return. now, i understand your impulsive dismissiveness. i gave you a step by step how to prove it. or you could've invited me to a private lobby and discord. it would've taken mere minutes. but clearly you weren't interested in making the product better, bc its easier for you to assume that you are always correct when you're rarely ever. which is why liam was always a zillion times more insightful than you to be honest. subnet and MTU are advance settings. advance setting are often rarely tweaked by anyone outside of advance users. so your dismissiveness holds no validity. to summarize your dismissiveness: we're too understaff to look into anything that is simply easier to dismiss. its funny how your dismissiveness is endless, YET email logs between myself and liam would LIKELY PROVE that my feed back on the matter LEAD TO devs coding R3 TO disconnect upon setting changes. which makes your dismissiveness even more so disingenuous.
  2. what do you mean by this exactly? since the only recommended change, regarding the subnet resetting entire routers connection, was a reversion back to how the previous OS did not disrupt connections upon subnet tweaks. simply code it to not hard reset connection. i don't think reverting, or an option to revert, is a request for anything special. forced hard connection resets aren't practical. as far as you saying what the team will and won't do. well they haven't spoken with me about it. what i said is provable. and i offered to prove it. which would've been brief. but get it. you prefer that it not be true. it's imprudent to assume that anyone knows all. forum is for feedback. i provide feedback and its dismissed. fascinating.
  3. invalid speculation. on the fly subnet changes are essential. the default automatically assigned subnet is often not the correct subnet to utilize HALF the time. i'm a network engineer. so simply ask one from your local area. or invite one to forum. if the wrong subnet is assigned, then manual adjustments is the remedy for which such manual input option exist. manual tweaks is standard in all routers. the subnet which is auto assigned to a network router is done so randomly. not often properly. sometimes the auto assigned subnet is correct. sometimes its incorrect. yes. due to the automatic disruptive needless connection resets, that occur due to simple subnet and mtu tweaks + delayed ethernet port + custom ping list removed. my point about subnet has never been refuted.
  4. simple subnet tweaks. simple mtu tweaks. which the R2 handled fine without rarely ever disconnecting. R3 disconnects upon simple tweaks/changes bc it was deliberately coded to do so. making it unsuitable in a streaming/gaming environment. hopefully Alex will consider my passionate feedback and remove forced needless R3 disconnects.
  5. yes. its the primary reason i'd bought an R3. negative. connection disruption is the wrong direction. for a gaming router. imagine streaming or gaming, you make a minor subnet adjustment, then abruptly disconnected, whereas previous R2 OS, rarely ever disconnected, upon simple tweaks. the ideal and proper direction to resolve this, is providing users the option to select whether or not they want their connection disrupting over simple network tweaks. needless disconnections make R3 unusable/unsuitable. in 2024 it is beyond unacceptable to stream or game and get disconnected over simple router tweaks. an astronomical oversight. imo. the R2 configuration with regard to handling tweaks without disconnecting user is the way forward. or providing R3 users the option of R2 resiliency with little to no disruption. please add command: connection reset upon user changes: false. (as in on/off option)
  6. i don't see how you understood. you cannot add custom ping list in R3. as i originally stated. R2, you can add custom ping list as image illustrates. what would be a bug? inability to add custom list in R3? surely i can't be the first to have noticed such. if you're suggesting its a bug. ALSO R3 losing connection anytime users saves a different network setting is a catastrophic downgrade. Imagine noticing ping spike, so you adjust network settings, only to be disconnected then suspended from ow all because R3 was deliberately coded to disrupt connection upon any setting adjustment. Whereas R2 rarely ever disconnects whenever adjusting network settings. R2's resiliency at keeping users connected is impeccable compared to R3.
  7. R3 OS: you cannot add a custom list in ping map. maybe an oversight somehow. R2 OS: you can add custom list as screenshot illustrates. nothing i said was a bug. proof? R2 saves any network setting adjustment that user submits, without device rebooting connection each time. R3 reboots connection each time upon saving/updating any submitted network setting adjustment, resulting in nuisance disconnects. whereas R2 does the same task, yet rarely ever disconnecting upon user submitted network setting adjustments. .
  8. well sadly, the R3 is a massive downgrade. its as if someone bought the company and internally sabotaged it. devs went from useful features to watering down OS. deliberately. for example. Before purchase, helpful patch notes would be: 1. Removed ability to save network changes without router disconnecting each and every time. Can’t save network settings without being disconnected. R3 is deliberately coded to disconnect as previous OS, doesn't. R3 = massive downgrade. 2. Removed ability for players to have a custom ping list in ping map. Which means players are limited to only a hand full of preloaded games automatically curated. Can’t ADD a custom list to ping map. A function which once made ping map actually useful to begin with. 3. R2 ethernet port is instant. R3 ethernet port is delayed. Indicating zero care or concern for wired users. Imagine anytime that you plug in your ethernet cable, there's a 10 second delay before you actually have a connection. Whereas with R2 your connection was instant. R3 = massive downgrade.
  9. @fraser your email did not included refund amount. it basically just said processing. i will be refunded the full purchase amount, correct?
  10. @frasercheck email
  11. @fraser it's been a month. where is refund?
  12. Fraser asked for the order# which wasn't included with device btw I inform Fraser that no receipt slip was included, as in, physically shipped. I then ask Fraser what info is needed to find order#? He ignored msg or got fired. I dig through past emails and provide order# as requested. Which should've been printed out and shipped with device to begin with. You have my order# What's the hold up.
×
×
  • Create New...