Re: Just Hardwired - Still LAGGING! WTH

Also I thought I should mention that about a week ago I was playing and it was 1AM when I started and ended around 3AM.

The game felt FANTASTIC. The best It's ever felt. I went on a 3 game winning streak in Ranked and was having such a blast tracking my shots on what felt to be the smoothest game I've ever played.

Now it seems that I'm always going to be chasing that feel I had a week ago. I thought hardwiring was the end all be all but admittedly, I don't know how the internet works LOL

@92F0XBody_HD I mean, I'll take a wire over wifi any day of the week. True, when wifi is working properly the latency SHOULD be comparable to a wired connection, but all too often you have invisible signal interference, either from your neighbors, electrical fields, etc. By switching to a wire, you should have eliminated those possibilities. The issue is that your speed tests don't usually test for line quality, just raw speed. Raw speed is more important than line quality for downloads, but when it comes to gaming you need both, to a degree. Honestly, consistent line quality would be far better than faster speeds. If you have a PC you can use to test while gaming, you can open up a command prompt : click start, type cmd, then click command prompt from the choices (this assumes you have windows 10 and not an earlier version). Once the command prompt opens up you would type the following (minus the "" marks) "ping 8.8.8.8 -t ". This will initiate a constant (until you close the window or press ctrl+c at the same time) ping to Google's free DNS server. Now, this is where it gets a little tricky, as those ping results aren't time stamped and you're going to want to have a real time view of them when your lag issues are happening. If, during your lag issues, your ping responses to 8.8.8.8 are jumping up over the 30 ms times to triple (or heaven forbid quadruple) digits, then it is your line quality that is the problem. If the ping remains constant, then it is likely something on the Apex server side. I say likely, because the routing between you and Google's DNS will differ somewhat from the routing between you and Apex, and the issue may be somewhere in the different path, in which case good luck getting it fixed.