What's even more annoying, is running a speedtest on the shield through a mobile browser or an app, yields good results.
Pings in the 8 ms range to a close server, over 400Mbps.
After finally buying a Nvidia Shield Pro for over 300$ because Linus has often said it's the best for streaming device, I've found it's a piece of garbage for game streaming.
High pings, dropped packets etc.
All other devices on the LAN work fine.
Router -> Itself:
PING 127.0.0.1 (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: seq=0 ttl=64 time=0.153 ms
64 bytes from 127.0.0.1: seq=1 ttl=64 time=0.120 ms
64 bytes from 127.0.0.1: seq=2 ttl=64 time=0.096 ms
64 bytes from 127.0.0.1: seq=3 ttl=64 time=0.109 ms
64 bytes from 127.0.0.1: seq=4 ttl=64 time=0.061 ms
--- 127.0.0.1 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.061/0.107/0.153 ms
Router -> Desktop, Intel 12700k (Ethernet)
PING 192.168.50.214 (192.168.50.214): 56 data bytes
64 bytes from 192.168.50.214: seq=0 ttl=128 time=0.291 ms
64 bytes from 192.168.50.214: seq=1 ttl=128 time=0.291 ms
64 bytes from 192.168.50.214: seq=2 ttl=128 time=0.301 ms
64 bytes from 192.168.50.214: seq=3 ttl=128 time=0.300 ms
64 bytes from 192.168.50.214: seq=4 ttl=128 time=0.353 ms
--- 192.168.50.214 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.291/0.307/0.353 ms
Router -> HP Printer (Ethernet)
PING 192.168.50.135 (192.168.50.135): 56 data bytes
64 bytes from 192.168.50.135: seq=0 ttl=255 time=0.241 ms
64 bytes from 192.168.50.135: seq=1 ttl=255 time=0.161 ms
64 bytes from 192.168.50.135: seq=2 ttl=255 time=0.195 ms
64 bytes from 192.168.50.135: seq=3 ttl=255 time=0.172 ms
64 bytes from 192.168.50.135: seq=4 ttl=255 time=0.158 ms
--- 192.168.50.135 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.158/0.185/0.241 ms
Router -> Google Chromecast Ultra (Wifi 5Ghz)
PING 192.168.50.131 (192.168.50.131): 56 data bytes
64 bytes from 192.168.50.131: seq=0 ttl=64 time=0.941 ms
64 bytes from 192.168.50.131: seq=1 ttl=64 time=0.930 ms
64 bytes from 192.168.50.131: seq=2 ttl=64 time=1.109 ms
64 bytes from 192.168.50.131: seq=3 ttl=64 time=1.378 ms
64 bytes from 192.168.50.131: seq=4 ttl=64 time=1.499 ms
--- 192.168.50.131 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.930/1.171/1.499 ms
Router -> Nvidia Shield (Wifi 5Ghz)
64 bytes from 192.168.50.146: seq=91 ttl=64 time=119.210 ms
64 bytes from 192.168.50.146: seq=92 ttl=64 time=21.586 ms
64 bytes from 192.168.50.146: seq=93 ttl=64 time=228.526 ms
64 bytes from 192.168.50.146: seq=94 ttl=64 time=140.345 ms
64 bytes from 192.168.50.146: seq=95 ttl=64 time=43.863 ms
64 bytes from 192.168.50.146: seq=96 ttl=64 time=261.827 ms
64 bytes from 192.168.50.146: seq=97 ttl=64 time=1.903 ms
64 bytes from 192.168.50.146: seq=98 ttl=64 time=1.395 ms
--- 192.168.50.146 ping statistics ---
99 packets transmitted, 99 packets received, 0% packet loss
round-trip min/avg/max = 1.017/159.041/615.978 ms
I cannot wire the Shield with Ethernet, it's one floor up and a couple of walls away.
It's fast, and snappy in the interface, loading up streaming services like netflix and youtube is great.
Anything realtime like game streaming is a pretty awful experience and it was better on the Chromecast Ultra.
This happens when game runs out of VRAM. I can replicate this exact behavior when I use the extreme preset. This has been around for 6+ months, Turn10 still havent fixed it.
Yeah the MH751's are the best you can get for the price. Good studio headphones that are good quality with good pads and the mic is the best I've heard on any "gaming" headset under 200 dollars.
Sam2791 got a reaction from WereCat in FORZA HORIZON 5 GRAPHICS GLITCHES
Sam2791 got a reaction from TheSLSAMG in Forza Horizon 4 - Texture Popping
