Menu
Reply
linwelin
  • 182
  • 0
  • 4
On our wavelength
987 Views
Message 1 of 34
Flag for a moderator

Geforce Now

Currently on VM 200 service so have plenty of speed for this but not running great, i don't know if it is the GeForce servers or VM or even me, quality isn't very good and is a bit laggy, i am just wondering if anyone here has any experience with GeForce now on VM?

0 Kudos
Reply
Adduxi
  • 6.08K
  • 511
  • 1.57K
Very Insightful Person
Very Insightful Person
955 Views
Message 2 of 34
Flag for a moderator

Re: Geforce Now

Setup a BQM to monitor your incoming circuit.  It maybe the BB is causing the lag.   www.thinkbroadband.com/ping

Once done, post a link to the "shared" graph and we can comment.  It will take a few hours to populate anything meaningful on the graph.

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks

0 Kudos
Reply
linwelin
  • 182
  • 0
  • 4
On our wavelength
935 Views
Message 3 of 34
Flag for a moderator

Re: Geforce Now

https://www.thinkbroadband.com/broadband/monitoring/quality/share/d5deca2f40db8cfb903c051f42e47d9e0c872418
0 Kudos
Reply
jpeg1
  • 6.86K
  • 352
  • 1.26K
Legend
896 Views
Message 4 of 34
Flag for a moderator

Re: Geforce Now

Your BQM trace so far shows your local circuit is quite busy with other users causing contention spikes and some packet loss at one point. But it could be much worse and some users do suffer more.

You could post here your Hub logs from 192.168.0.1 to see if there are any connection issues.

Is your games device connected to the Hub by WiFi or ethernet?  Ethernet is always best for gaming. 

0 Kudos
Reply
linwelin
  • 182
  • 0
  • 4
On our wavelength
863 Views
Message 5 of 34
Flag for a moderator

Re: Geforce Now

Thanks for the reply, i only use ethernet.

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

2533100000010.30000340.946209QAM25625
11390000008.90000240.946209QAM2561
21470000009.09999840.946209QAM2562
31550000009.50000040.946209QAM2563
41630000009.40000240.366287QAM2564
51710000009.19999740.946209QAM2565
61790000009.09999840.946209QAM2566
71870000009.09999840.946209QAM2567
81950000009.30000340.946209QAM2568
92030000009.40000240.366287QAM2569
102110000009.50000040.366287QAM25610
112190000009.40000240.946209QAM25611
122270000009.19999740.946209QAM25612
132350000009.09999840.366287QAM25613
142430000009.19999740.946209QAM25614
152510000009.40000240.946209QAM25615
162590000009.50000040.946209QAM25616
172670000009.09999840.946209QAM25617
182750000009.19999740.946209QAM25618
192830000009.50000040.946209QAM25619
202910000009.59999840.946209QAM25620
212990000009.69999740.946209QAM25621
2230700000010.00000040.946209QAM25622
2331500000010.30000340.946209QAM25623
2432300000010.40000240.946209QAM25624
2633900000010.40000240.946209QAM25626
2734700000010.59999840.946209QAM25627
2835500000010.40000240.366287QAM25628
2936300000010.30000340.946209QAM25629
3037100000010.40000240.946209QAM25630
3137900000010.40000240.946209QAM25631



3.0 Downstream channels

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

25Locked40.94620900
1Locked40.94620900
2Locked40.94620900
3Locked40.94620900
4Locked40.36628700
5Locked40.94620900
6Locked40.94620900
7Locked40.94620900
8Locked40.94620900
9Locked40.36628700
10Locked40.36628700
11Locked40.94620900
12Locked40.94620900
13Locked40.36628700
14Locked40.94620900
15Locked40.94620900
16Locked40.94620900
17Locked40.94620900
18Locked40.94620900
19Locked40.94620900
20Locked40.94620900
21Locked40.94620900
22Locked40.94620900
23Locked40.94620900
24Locked40.94620900
26Locked40.94620900
27Locked40.94620900
28Locked40.36628700
29Locked40.94620900
30Locked40.94620900
31Locked40.94620900

 

0 Kudos
Reply
linwelin
  • 182
  • 0
  • 4
On our wavelength
862 Views
Message 6 of 34
Flag for a moderator

Re: Geforce Now

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

13260000046.0205995120 KSym/sec64QAM5
23940000046.7705995120 KSym/sec64QAM4
34620000046.7705995120 KSym/sec64QAM3
42580000045.7705995120 KSym/sec64QAM6



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_STDMA0010
2US_TYPE_STDMA0000
3US_TYPE_STDMA0000
4US_TYPE_STDMA0000
0 Kudos
Reply
linwelin
  • 182
  • 0
  • 4
On our wavelength
861 Views
Message 7 of 34
Flag for a moderator

Re: Geforce Now

TimePriorityDescriptionFri Oct 8 02:42:05 20216CM-STATUS message sent. Event Type Code: 4; Chan ID: 5; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 07:57:28 20215Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 07:57:31 20216CM-STATUS message sent. Event Type Code: 4; Chan ID: 5; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 11:43:28 20215Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 11:43:44 20216CM-STATUS message sent. Event Type Code: 4; Chan ID: 5; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 12:40:32 20215Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 12:40:33 20216CM-STATUS message sent. Event Type Code: 4; Chan ID: 5; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 12:50:22 20215Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 12:50:44 20216CM-STATUS message sent. Event Type Code: 4; Chan ID: 5; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 12:54:30 20215Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 12:54:34 20216CM-STATUS message sent. Event Type Code: 4; Chan ID: 5; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 13:17:52 20215Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 13:17:58 20216CM-STATUS message sent. Event Type Code: 4; Chan ID: 5; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 15:05:03 20215Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 15:05:04 20216CM-STATUS message sent. Event Type Code: 4; Chan ID: 5; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 15:05:31 20215Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 15:05:53 20216CM-STATUS message sent. Event Type Code: 4; Chan ID: 5; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 15:06:13 20215Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 15:06:44 20216CM-STATUS message sent. Event Type Code: 4; Chan ID: 5; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 15:06:55 20215Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 15:07:18 20216CM-STATUS message sent. Event Type Code: 4; Chan ID: 5; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 19:35:12 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat Oct 9 01:42:50 20215Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat Oct 9 01:43:06 20216CM-STATUS message sent. Event Type Code: 5; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue Oct 12 07:35:12 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue Oct 12 08:15:25 20216CM-STATUS message sent. Event Type Code: 5; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Thu Oct 14 16:43:21 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 15 13:32:56 20216CM-STATUS message sent. Event Type Code: 5; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 15 19:35:12 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Thu Jan 1 00:01:18 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat Oct 16 20:27:35 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Mon Oct 18 07:42:16 20216CM-STATUS message sent. Event Type Code: 5; Chan ID: 2; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Thu Jan 1 00:01:21 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Mon Oct 18 13:09:49 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Wed Oct 20 16:22:25 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat Oct 23 17:26:11 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Wed Oct 27 00:28:51 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Nov 5 02:39:57 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat Nov 6 12:28:51 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Thu Nov 11 03:35:11 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat Nov 13 12:28:52 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sun Nov 14 22:35:42 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue Nov 16 13:09:58 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Thu Nov 18 12:49:22 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue Nov 23 06:50:35 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Wed Nov 24 19:09:12 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

0 Kudos
Reply
Andrew-G
  • 10.38K
  • 1.66K
  • 4.74K
Alessandro Volta
847 Views
Message 8 of 34
Flag for a moderator

Re: Geforce Now

Having a Hub 4 on a 200 Mbps connection says that you're on a congested section of network, but the BQM looks like a different type of fault - ordinarily a pure congestion fault has a BQM that magically improves at 12:30am, and remains near perfect until 8-9am.  The small hours of your connection looks as poor as mid afternoon, and there's some suspiciously sustained (almost rectangular) latency bars showing, that's again not typical of a congestion fault.

I do note your downstream power levels are all pretty high.  Hold on for the forum staff to take a look and advise, they may be able to identify a known fault or get a technician booked for you.  If you get a "all looks normal to us" response, or they declare there's an over-utilisation fault with a fix date of next week, then it may be time to consider your options with other ISPs.

linwelin
  • 182
  • 0
  • 4
On our wavelength
835 Views
Message 9 of 34
Flag for a moderator

Re: Geforce Now

Thank you for the help, i shall wait for staff to respond then and see what they say, thanks again.
0 Kudos
Reply
jpeg1
  • 6.86K
  • 352
  • 1.26K
Legend
831 Views
Message 10 of 34
Flag for a moderator

Re: Geforce Now

Yes it's looking very odd this morning. The minimum latency is higher than average too. It's just possible the Hub has a fault, if nothing else can be done it might be worth arguing for a replacement.  Good luck!

0 Kudos
Reply