cancel
Showing results for 
Search instead for 
Did you mean: 

Call Of Duty Cold War & FPS's

simon692k
Joining in

I don't know if anybody can help me. I'm playing Call Of Duty Cold War on my PS5 and seem to be a second behind everybody else in online games. The game feels jittery and I lose 90% of gun fights that I should probaly win. I have the Superhub 3, 200gb package, play wired and believe it is down to ping and latency. I pay a lot for my monthly package and am currently out of contract, and wondered if I should look elsewhere for a smoother experience or stick with Virgin to resolve or up my current speed. I don't want a new contract if nothing changes. Any advice would be greatly appreciated.

Simon

12 REPLIES 12

Andrew-G
Alessandro Volta

Let's see how latency and packet loss are on your connection: Setup a BQM over at https://www.thinkbroadband.com/broadband/monitoring/quality that'll show what's going on with your VM connection.  Post a LINK to a LIVE, SHARED graph here and we'll see what's happening.  Usually needs to run for 24 hours before we can draw reasonable conclusions, but the live graph will continuously update so you can post the link immediately.

Nope, that's your logged in view, so all we see from that link is a blank log in page for Thinkbroadband.  That's why there's a "share graph" option, and using the share facility also removes your IP address which is visible on the logged in view (so don't cut and paste that).

https://www.thinkbroadband.com/broadband/monitoring/quality/share/89317ea2c8a592c224b690583cc62473f8ba03af

That's the one!  Good news, it's not an over-utilisation fault, so chances of getting it fixed are reasonable.  Bad news, it looks like an intermittent fault, so it may not be a quick fix unless we/you/field techs get lucky.

Next step: Connect to the hub by clicking on this link http://192.168.0.1/ (so long as you're not in modem mode). That should pull up the log in page for the hub.  But don't log in, just click on the link "Check router status"  That'll bring up a window with five tabs.  Open the Downstream tab.  Select all the text (Ctrl-A if using a keyboard), copy it (Ctrl-C), then paste it (Ctrl-V) into a reply here as TEXT not screenshots.  Post that, do the same for the Upstream and Network log.  You'll get an error message when you post the Network log, just click on "post" a second time.

Then we can check for any obvious problems with power, noise or error counts.

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1499000000-1.240256 qam32
2203000000340256 qam9
32110000002.540256 qam10
42190000002.740256 qam11
52270000002.240256 qam12
62350000002.240256 qam13
7243000000240256 qam14
82510000002.240256 qam15
92590000002.240256 qam16
102670000001.940256 qam17
112750000002.240256 qam18
122830000001.940256 qam19
13291000000240256 qam20
142990000002.440256 qam21
15307000000240256 qam22
163150000002.240256 qam23
17323000000240256 qam24
18443000000040256 qam25
19451000000-0.540256 qam26
20459000000-0.240256 qam27
21467000000-0.540256 qam28
22475000000-0.440256 qam29
23483000000-140256 qam30
24491000000-1.238256 qam31



Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1Locked40.96372455
2Locked40.35432316
3Locked40.95282781
4Locked40.95342507
5Locked40.95992633
6Locked40.36142739
7Locked40.38202845
8Locked40.35672589
9Locked40.35412757
10Locked40.36202668
11Locked40.95922698
12Locked40.36562556
13Locked40.36532642
14Locked40.36432815
15Locked40.36982442
16Locked40.96882456
17Locked40.36832717
18Locked40.36712415
19Locked40.96922168
20Locked40.37052398
21Locked40.36562241
22Locked40.36792178
23Locked40.36102298
24Locked38.97032272

Upstream bonded channels Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
14620000446.8512064 qam1
22580000045.3512064 qam4
33260002646.8512064 qam3
43940000046.8512064 qam2



Upstream bonded channels Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1ATDMA0000
2ATDMA0010
3ATDMA0000
4ATDMA0000

Network Log

Time Priority Description

19/07/2021 12:07:26Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/07/2021 12:07:26criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/07/2021 12:07:23Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/07/2021 17:03:7criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/07/2021 08:01:21Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/07/2021 03:50:19criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:02:25noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:02:19criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/07/2021 22:38:36Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/07/2021 22:29:8Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/07/2021 22:28:23Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/07/2021 19:16:45Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/07/2021 19:16:45criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2021 12:55:28criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2021 09:45:9noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2021 09:45:9ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/07/2021 09:18:5criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/07/2021 01:25:29Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/07/2021 02:12:55criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2021 22:46:47Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Network log is poor, there's too many downstream post-RS errors, and the downstream power levels look to me to have an unhelpfully wide range.  I'll mark this for the forum staff to comment.  Could be an area fault, or something unique to your cable.