stutter and high frame loss over wired network connection #2075
Comments
HertogArjan
changed the title
|
Having same problem on my Shield/Moonlight and PC/Sunshine config with Windows10, AMD Ryzen 7 5700X, RTX 4070Super, 2.5Gb NIC hardwired with Cat5e to Shield 2017. Stutters every 20/30 seconds. |
Your issue may be different though. In my case the stutter is very frequent, practically constant. Have you tried setting the 'FEC percentage' to 100% in the Sunshine configuration and does that fix your issue? |
|
I did try setting it to 100%, it didn't solve the problem. It is hard to find the root cause in my case. Tried resetting NIC, fiddling with energy saving which always helped before but now it still stutters. Maybe I will also try Nvidia driver rollback although hard to imagine how it could affect things since I do not use/install Gamestream at all. Strange thing is that it was ok day before and next day it stutters even though I did not make any changes. Maybe my router is dying. So many variables, so many questions. Update: Ok, made my network setup simpler (removed one router from equation), Shield connected via Wifi 5GHz to router on table, router wired to PC. No stutters no matter what. All runs great. Hmm maybe my other router (DSL) is dying or one cable is damaged along the way. Will check later. Update 2: Yesterday I fixed it. Restored previous network setup with 2 routers and cat5 cables. Not sure what item on list below exactly did it but it all works now, not a single stutter. Sunshine Version 0.21.0 Sunshine config: Services disable/set to manual in Windows: Disabled VRR option in Windows. Ethernet settings->Advanced config: Update 3: So stutter is back. Strange thing is that one day it is ok and next day it stutters... Either it is my old VDSL router dying or faulty cable. Not sure what else it could be. Update 4: Hmm these options seemed to fix it... All good/no stutters when running from ShieldTV downstairs through 2 routers and cables to host PC. |
|
Later discovered that ethernet cable downstairs had a hole in it (caused by a nail) ... heh. Also seems that restart of vdsl router helped for while, so it is probably reaching EOL. Will check with new router/cable on Tuesday. |
|
Ok, so the new router works as expected so far. No stutters observed...yet. |
Is there an existing issue for this?
Is your issue described in the documentation?
Is your issue present in the nightly release?
Describe the Bug
Whenever I connect with Moonlight to my host pc running Sunshine there is a visible stutter in the stream. If I enable the performance overlay in Moonlight I can see the 'frame loss due to network' hovers between 0 and 25% and correlates with the stutters.
Expected Behavior
I expect no (or at least much less than 25%) 'frame loss due to network' when streaming locally over a wired connection.
Additional Context
The host and client machines are connected with a wired network connection. Running iperf3 between the client and host pc shows the link is stable with a bandwith of ~940mbps and no packet loss.
Steam Remote Play does not visibly suffer from frame loss, nor have I noticed any packet loss in any other application on either machine.
I tried Sunshine v0.21.0, v0.20.0 and the latest nightly (2024-01-28T20:01:21Z) and all suffer from this issue.
I also tried forcing software decoding in Moonlight, or forcing HEVC or H264, but neither had any effect on the issue.
A workaround is to set the FEC percentage to 100% in Sunshine. This allows me to stream again with no frame loss, but it is obviously not ideal in terms of efficiency.
My host pc is based on a AMD Ryzen 3600 and AMD RX 5700 and runs Windows 11. My client PC is based on a Intel i5-6200u with Intel HD Graphics 520 and runs Arch Linux.
Host Operating System
Windows
Operating System Version
Windows 11
Architecture
64 bit
Sunshine commit or version
0.21.0
Package
Windows - Scoop (Third Party)
GPU Type
AMD
GPU Model
AMD RX 5700
GPU Driver/Mesa Version
24.1.1
Capture Method (Linux Only)
No response
Config
Apps
No response
Relevant log output
The text was updated successfully, but these errors were encountered: