Jump to content


DumaOS Insiders
  • Content Count

  • Joined

Everything posted by RiotControll

  1. Also the angles are broken like in MW. You can be killed without seeing the opponent.
  2. Probably the play on Google servers, we normal people barely see in matchmaking.
  3. Again, it's their servers fault not yours or ISP's. Packet Loss was no issue till the end of June last year. When Season 5 hit the Paket Loss Symbol appeared. Personally I think around that time dumbass Raven Software got the Lead on Warzone and they had no clue what they were doing.
  4. Packet Loss is standard in Warzone. Even without a Netduma you get Packet Loss. The servers are pretty degenerately configured & maintained. So there's no worry.
  5. Per Lan an die Fritzbox anschliessen und das wars schon und alle Geräte die per Wlan laufen über die Xr500 laufen lassen. Wlan kannst du bei der Fritzbox dann auch ausschalten.
  6. It's server depending. Packet burst appears when the servers hoster carriers have depleted their peering capacity. So data packets get thrown away or queued at the major exchange points. Telia/Cogent/GTT are notoriously known for this. They won't extend their peering capacities at the major exchanges points because it costs money.
  7. Lol, Telia can't get even their own shit together. 19ms from the first Telia hop to the second although the networkrouters are in the same building. Can't understand why COD uses such bad server hosters which use even worse carriers like Telia/Cogent/GTT.
  8. Battle Royal & Plunder plays laggy & I have a sluggish movement while pre lobby is fluid and shots connect as supposed.
  9. In Warzone you can the artificial lag on your connection. If you play Battle Royal or Plunder the connections are crisp in pre game lobbies where the countdown ticks down to zero. The bullets connect as it should be and the character movement feels lighter. But when the main game starts it gets laggy and the character movement is sluggish.
  10. I've watched enough Twitch streams and YT videos and these people had also the latency & packetburst signs popping up.
  11. You don't need to worry. Packetburst is a general problem since season 6. It's a fault on their end. Prior Season 6 I had no latency & Packetburst problems.
  12. I don't know what you are doing because I have a ton of IP adresses from Frankfurt/Paris & London but they don't really help you because you need local ones.
  13. I mean you have the server IPs which you connect to, paste them into Pingplotter and run them. If your ISP's network router is congested at the exchange points you can show them that it's their fault because without evidence the say always everything's alright. As you see there are peering problems with my ISP and Telia who are the carrier for Choopa/Vultr for the WWII servers because Telia didn't extended their capacities.
  14. I'm also getting the the Paketburst & the High Latency sign even on my nearest server which is in Frankfurt. The problem is that the series has 6-10 different server hosters. Most of them are useless because they have bad carriers like Telia/Cogent/GTT. When their peering capacities are full they don't expand their capacities. So packets get lost and leads to a data jam which leads to superbullets for example. Only Amazon Web Services/Google & Blizzard's own servers are good.
  15. I downloaded & deleted the game 3 times during the Beta. The developers & Demonware (btw. Demonware moved the authentication server away from Ireland to Warsaw in Poland) are connection cheaters; they somehow filter/delay your packets then to have in & out problems. Every small studio is capable to provide a working neutral netcode to let the players decide the outcome of the gunfight unlike the Gay Of Duty series. Imo in general the COD developers are mentally handicapped people who don't see their programming faults. Also a problem is that these people have no gameplay advisors. That's why they put so much bullshit is put into the games.
  16. Warzone is generally unplayable since Season 6. They have server problems; I get the high latency and packetburst emblem although I'm connected to nearest server plus they tightened up the SBMM algorithms.
  17. Then please make a screenshot of it. I've never seen a WZ server with constant 50 tick rates in Europe.
  18. Download Ping Plotter and run some tests to the COD servers.
  19. You h That's packetloss what you have. Either something is wrong with your line or it occurs at your exchange point or there are problems with the carriers which bring your packets to the COD server. Have you tried it with a normal router?
  20. The end of the powercord was overbend so I had to bend it at a certain angle that it functioned.
  21. I haven't changed anything. The issues started 2 months ago but somehow after some tweaking of the power cord the R1 worked normally up to yesterday. Maybe something inside the power cord broke or I don't know. I'll get a new power adapter on Friday then I will report again.
  22. It's not accessible. I get this information. lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP> inet netmask 0xff000000 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 nd6 options=201<PERFORMNUD,DAD> gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 stf0: flags=0<> mtu 1280 en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 options=400<CHANNEL_IO> ether 78:4f:43:7c:f0:33 inet netmask 0xffffff00 broadcast media: autoselect status: active en3: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 options=460<TSO4,TSO6,CHANNEL_IO> ether 82:6c:b3:23:a8:01 media: autoselect <full-duplex> status: inactive en1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 options=460<TSO4,TSO6,CHANNEL_IO> ether 82:6c:b3:23:a8:00 media: autoselect <full-duplex> status: inactive en4: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 options=460<TSO4,TSO6,CHANNEL_IO> ether 82:6c:b3:23:a8:05 media: autoselect <full-duplex> status: inactive en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 options=460<TSO4,TSO6,CHANNEL_IO> ether 82:6c:b3:23:a8:04 media: autoselect <full-duplex> status: inactive bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 options=63<RXCSUM,TXCSUM,TSO4,TSO6> ether 82:6c:b3:23:a8:00 Configuration: id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0 maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200 root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0 ipfilter disabled flags 0x0 member: en1 flags=3<LEARNING,DISCOVER> ifmaxaddr 0 port 7 priority 0 path cost 0 member: en2 flags=3<LEARNING,DISCOVER> ifmaxaddr 0 port 9 priority 0 path cost 0 member: en3 flags=3<LEARNING,DISCOVER> ifmaxaddr 0 port 6 priority 0 path cost 0 member: en4 flags=3<LEARNING,DISCOVER> ifmaxaddr 0 port 8 priority 0 path cost 0 media: <unknown type> status: inactive p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304 options=400<CHANNEL_IO> ether 0a:4f:43:7c:f0:33 media: autoselect status: inactive awdl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1484 options=400<CHANNEL_IO> ether 1e:4e:ab:84:dc:19 inet6 fe80::1c4e:abff:fe84:dc19%awdl0 prefixlen 64 scopeid 0xc nd6 options=201<PERFORMNUD,DAD> media: autoselect status: active llw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 options=400<CHANNEL_IO> ether 1e:4e:ab:84:dc:19 inet6 fe80::1c4e:abff:fe84:dc19%llw0 prefixlen 64 scopeid 0xd nd6 options=201<PERFORMNUD,DAD> media: autoselect status: active utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380 inet6 fe80::c034:de05:eb6a:1765%utun0 prefixlen 64 scopeid 0xe nd6 options=201<PERFORMNUD,DAD> utun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000 inet6 fe80::828b:30e6:c554:3a3f%utun1 prefixlen 64 scopeid 0xf nd6 options=201<PERFORMNUD,DAD> utun2: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380 inet6 fe80::e55a:248f:f049:7a54%utun2 prefixlen 64 scopeid 0x10 nd6 options=201<PERFORMNUD,DAD> utun3: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380 inet6 fe80::126b:62c5:d9dd:6e5b%utun3 prefixlen 64 scopeid 0x12 nd6 options=201<PERFORMNUD,DAD> en5: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 ether ac:de:48:00:11:22 inet6 fe80::aede:48ff:fe00:1122%en5 prefixlen 64 scopeid 0x4 nd6 options=201<PERFORMNUD,DAD> media: autoselect status: active
  23. I have exactly the same issues. The lights are on maximum disco/wifi not showing up and the reset button is not responding. Is this a hardware or software defect?
  24. I'm slowly starting to think that Activision & the developers whitelist certain YouTubers to promote the game.
  • Create New...