Menu
Reply
Joining in
  • 6
  • 0
  • 0
Registered: ‎10-06-2017
Message 1 of 9 (283 Views)

CS:GO Recoil Lag & Ping Spikes

Hi, I wonder if anybody can help me... I'm having problems playing CS:GO without lag. Recently I've been getting choke and ping spikes constantly making the game near enough unplayable for me. I've tried putting the Super Hub in modem mode and I've even spent 500 upgrading my pc just incase it was a hardware issue. I had an engineer come out a few months ago to have a look at it and he said it was fine but he changed some of the wiring around and ever since its been even worse. Can anyone help?

Reply
0 Kudos
Forum Team
  • 10.27K
  • 283
  • 606
Registered: ‎07-04-2015
Message 2 of 9 (231 Views)

Re: CS:GO Recoil Lag & Ping Spikes

Afternoon tdown,

 

Thanks for taking the time to post on the community.

 

Sorry to read you are experiencing lag and ping spikes whilst playing CS:GO.

 

Is the device you are gaming on, connecting through wired or wireless? If wireless, can you try through wired please to see if that will help?

 

Does this only happen on CS:GO, or can it be on other games also?

 

Are you able to post some ping tests/trace routes for us to check over please?

 

Hope to hear from you soon

Sam


New around here? To find out more about the Community check out our Getting Started guide


Reply
0 Kudos
Joining in
  • 6
  • 0
  • 0
Registered: ‎10-06-2017
Message 3 of 9 (205 Views)

Re: CS:GO Recoil Lag & Ping Spikes

Hi, I'm connected to the router via Ethernet. I have tried putting the router into modem mode with no luck too, I don't really play any other games but I sometimes have problems streaming HD videos via youtube.

Ping test - http://www.netmeter.co.uk/ping-test/201735-47085-de62.html

I'm not sure what to do when it comes to traceroutes but I think I've done it? 

This is a traceroute to a CS:GO server I play on - http://www.monitis.com/traceroute/index.jsp?url=87.117.231.143&testId=1815714

Thanks


 
Reply
0 Kudos
Joining in
  • 6
  • 0
  • 0
Registered: ‎10-06-2017
Message 4 of 9 (201 Views)

Re: CS:GO Recoil Lag & Ping Spikes

I see other people are having issues with the superhub 3.0 also.. would it be possible to go back to the superhub 2? I had no problems before the superhub change

Reply
0 Kudos
Up to speed
  • 124
  • 2
  • 30
Registered: ‎19-07-2013
Message 5 of 9 (192 Views)

Re: CS:GO Recoil Lag & Ping Spikes

Trace Routes and Ping results must be performed from your PC

Start CMD - to bring up the Command Prompt and type 

tracert 87.117.231.143

ping 87.117.231.143 -n 100 (This will send 100 packets to the game server)

You are correct there are known issues with the Hub 3 - "Latest" is a firmware update due in Q4 2017 , you have a very slim chance of getting your Hub 2 Back 

http://community.virginmedia.com/t5/Gaming-Support/Hub-3-Compal-CH7465-LG-TG2492LG-and-CGNV4-Latency...

 

 

Reply
0 Kudos
Joining in
  • 6
  • 0
  • 0
Registered: ‎10-06-2017
Message 6 of 9 (160 Views)

Re: CS:GO Recoil Lag & Ping Spikes

[ Edited ]

1 <1 ms <1 ms <1 ms routerlogin.net [192.168.0.1]
2 * * * Request timed out.
3 14 ms 10 ms 12 ms cdif-core-2a-xe-203-0.network.virginmedia.net [62.252.32.157]
4 * * * Request timed out.
5 19 ms 17 ms 17 ms brhm-bb-1c-ae0-0.network.virginmedia.net [62.254.42.110]
6 34 ms 26 ms 20 ms tcl5-ic-2-ae0-0.network.virginmedia.net [212.250.15.210]
7 20 ms 21 ms 22 ms be20.asr01.thn.as20860.net [195.66.224.207]
8 19 ms 20 ms 20 ms po111.net1.north.dc5.as20860.net [62.233.127.174]
9 21 ms 28 ms 20 ms po4-50.bor1.dc5.as20860.net [212.84.161.145]
10 24 ms 23 ms 21 ms 62.128.199.1
11 21 ms 20 ms 19 ms 87.117.231.143

There is my traceroute and below is the ping 

Pinging 87.117.231.143 with 32 bytes of data:
Reply from 87.117.231.143: bytes=32 time=19ms TTL=54
Reply from 87.117.231.143: bytes=32 time=21ms TTL=54
Reply from 87.117.231.143: bytes=32 time=19ms TTL=54
Reply from 87.117.231.143: bytes=32 time=20ms TTL=54
Reply from 87.117.231.143: bytes=32 time=27ms TTL=54
Reply from 87.117.231.143: bytes=32 time=21ms TTL=54
Reply from 87.117.231.143: bytes=32 time=20ms TTL=54
Reply from 87.117.231.143: bytes=32 time=21ms TTL=54
Reply from 87.117.231.143: bytes=32 time=20ms TTL=54
Reply from 87.117.231.143: bytes=32 time=20ms TTL=54
Reply from 87.117.231.143: bytes=32 time=27ms TTL=54
Reply from 87.117.231.143: bytes=32 time=27ms TTL=54
Reply from 87.117.231.143: bytes=32 time=27ms TTL=54
Reply from 87.117.231.143: bytes=32 time=19ms TTL=54
Reply from 87.117.231.143: bytes=32 time=21ms TTL=54
Reply from 87.117.231.143: bytes=32 time=20ms TTL=54
Reply from 87.117.231.143: bytes=32 time=25ms TTL=54
Reply from 87.117.231.143: bytes=32 time=36ms TTL=54
Reply from 87.117.231.143: bytes=32 time=19ms TTL=54
Reply from 87.117.231.143: bytes=32 time=22ms TTL=54
Reply from 87.117.231.143: bytes=32 time=19ms TTL=54
Reply from 87.117.231.143: bytes=32 time=20ms TTL=54
Reply from 87.117.231.143: bytes=32 time=19ms TTL=54
Reply from 87.117.231.143: bytes=32 time=24ms TTL=54
Reply from 87.117.231.143: bytes=32 time=20ms TTL=54
Reply from 87.117.231.143: bytes=32 time=26ms TTL=54
Reply from 87.117.231.143: bytes=32 time=20ms TTL=54
Reply from 87.117.231.143: bytes=32 time=19ms TTL=54
Reply from 87.117.231.143: bytes=32 time=21ms TTL=54
Reply from 87.117.231.143: bytes=32 time=20ms TTL=54
Reply from 87.117.231.143: bytes=32 time=21ms TTL=54
Reply from 87.117.231.143: bytes=32 time=21ms TTL=54
Reply from 87.117.231.143: bytes=32 time=19ms TTL=54
Reply from 87.117.231.143: bytes=32 time=19ms TTL=54
Reply from 87.117.231.143: bytes=32 time=63ms TTL=54
Reply from 87.117.231.143: bytes=32 time=20ms TTL=54
Reply from 87.117.231.143: bytes=32 time=20ms TTL=54
Reply from 87.117.231.143: bytes=32 time=19ms TTL=54
Reply from 87.117.231.143: bytes=32 time=21ms TTL=54
Reply from 87.117.231.143: bytes=32 time=33ms TTL=54
Reply from 87.117.231.143: bytes=32 time=20ms TTL=54
Reply from 87.117.231.143: bytes=32 time=26ms TTL=54
Reply from 87.117.231.143: bytes=32 time=27ms TTL=54
Reply from 87.117.231.143: bytes=32 time=20ms TTL=54
Reply from 87.117.231.143: bytes=32 time=36ms TTL=54
Reply from 87.117.231.143: bytes=32 time=21ms TTL=54
Reply from 87.117.231.143: bytes=32 time=21ms TTL=54
Reply from 87.117.231.143: bytes=32 time=19ms TTL=54
Reply from 87.117.231.143: bytes=32 time=21ms TTL=54
Reply from 87.117.231.143: bytes=32 time=22ms TTL=54
Reply from 87.117.231.143: bytes=32 time=20ms TTL=54
Reply from 87.117.231.143: bytes=32 time=21ms TTL=54
Reply from 87.117.231.143: bytes=32 time=23ms TTL=54
Reply from 87.117.231.143: bytes=32 time=20ms TTL=54
Reply from 87.117.231.143: bytes=32 time=19ms TTL=54
Reply from 87.117.231.143: bytes=32 time=19ms TTL=54
Reply from 87.117.231.143: bytes=32 time=21ms TTL=54
Reply from 87.117.231.143: bytes=32 time=26ms TTL=54
Reply from 87.117.231.143: bytes=32 time=20ms TTL=54
Reply from 87.117.231.143: bytes=32 time=28ms TTL=54
Reply from 87.117.231.143: bytes=32 time=21ms TTL=54
Reply from 87.117.231.143: bytes=32 time=32ms TTL=54
Reply from 87.117.231.143: bytes=32 time=20ms TTL=54
Reply from 87.117.231.143: bytes=32 time=19ms TTL=54
Reply from 87.117.231.143: bytes=32 time=24ms TTL=54
Reply from 87.117.231.143: bytes=32 time=20ms TTL=54
Reply from 87.117.231.143: bytes=32 time=21ms TTL=54
Reply from 87.117.231.143: bytes=32 time=20ms TTL=54
Reply from 87.117.231.143: bytes=32 time=20ms TTL=54
Reply from 87.117.231.143: bytes=32 time=20ms TTL=54
Reply from 87.117.231.143: bytes=32 time=28ms TTL=54
Reply from 87.117.231.143: bytes=32 time=18ms TTL=54
Reply from 87.117.231.143: bytes=32 time=19ms TTL=54
Reply from 87.117.231.143: bytes=32 time=19ms TTL=54
Reply from 87.117.231.143: bytes=32 time=21ms TTL=54
Reply from 87.117.231.143: bytes=32 time=27ms TTL=54
Reply from 87.117.231.143: bytes=32 time=20ms TTL=54
Reply from 87.117.231.143: bytes=32 time=21ms TTL=54
Reply from 87.117.231.143: bytes=32 time=21ms TTL=54
Reply from 87.117.231.143: bytes=32 time=20ms TTL=54
Reply from 87.117.231.143: bytes=32 time=19ms TTL=54
Reply from 87.117.231.143: bytes=32 time=21ms TTL=54
Reply from 87.117.231.143: bytes=32 time=20ms TTL=54
Reply from 87.117.231.143: bytes=32 time=19ms TTL=54
Reply from 87.117.231.143: bytes=32 time=21ms TTL=54
Reply from 87.117.231.143: bytes=32 time=20ms TTL=54
Reply from 87.117.231.143: bytes=32 time=23ms TTL=54
Reply from 87.117.231.143: bytes=32 time=22ms TTL=54
Reply from 87.117.231.143: bytes=32 time=22ms TTL=54
Reply from 87.117.231.143: bytes=32 time=21ms TTL=54
Reply from 87.117.231.143: bytes=32 time=21ms TTL=54
Reply from 87.117.231.143: bytes=32 time=19ms TTL=54
Reply from 87.117.231.143: bytes=32 time=27ms TTL=54
Reply from 87.117.231.143: bytes=32 time=19ms TTL=54
Reply from 87.117.231.143: bytes=32 time=30ms TTL=54
Reply from 87.117.231.143: bytes=32 time=20ms TTL=54
Reply from 87.117.231.143: bytes=32 time=21ms TTL=54
Reply from 87.117.231.143: bytes=32 time=22ms TTL=54
Reply from 87.117.231.143: bytes=32 time=27ms TTL=54
Reply from 87.117.231.143: bytes=32 time=20ms TTL=54

Reply
0 Kudos
Forum Team
  • 9.17K
  • 263
  • 584
Registered: ‎01-12-2014
Message 7 of 9 (110 Views)

Re: CS:GO Recoil Lag & Ping Spikes

Hello tdown,

Thanks for keeping in touch Smiley Happy

Sorry for the problems you're having. You mentioned the possibility of connecting a Hub 2, do you have one from before? We can only reactivate equipment if it's still listed on your account and if your current package is compatible.

Catch you again soon,

Take care.  

Heather_J

Tech fan? Have you read our Digital life blog yet? Check it out


Reply
0 Kudos
Joining in
  • 6
  • 0
  • 0
Registered: ‎10-06-2017
Message 8 of 9 (103 Views)

Re: CS:GO Recoil Lag & Ping Spikes

Hi, I have spoke to someone on the phone and had my old hub 2 reactivated on my account but the problem still persists, is it a problem with my power levels or something?
Reply
0 Kudos
Forum Team
  • 9.17K
  • 263
  • 584
Registered: ‎01-12-2014
Message 9 of 9 (33 Views)

Re: CS:GO Recoil Lag & Ping Spikes

Hi tdown,

Thanks for letting me know Smiley Happy

Good to know that you've got your Superhub 2 re-activated. I've taken a look at it and everything looks completely normal with regards to your power and SNR levels. Has this settled down yet?

Take care.

Heather_J

Tech fan? Have you read our Digital life blog yet? Check it out


Reply
0 Kudos