mirror of
https://github.com/games-on-whales/wolf.git
synced 2026-10-15 21:12:08 +00:00
[GH-ISSUE #117] Host machine stops sending stream feed #75
Labels
No labels
🧠 1 - 🤖 999
AMD
bug
bug
cannot reproduce
documentation
duplicate
easy
enhancement
enhancement
enhancement
fixed?
fixed?
good first issue
hard
help wanted
Intel
invalid
LXC
medium
moonlight-protocol
Multi GPU
nixos
not a bug
nvidia
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
games-on-whales/wolf#75
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @IvanCharcos on GitHub (Sep 5, 2024).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/117
Hello,
I noticed this happens on a laptop and Steam Deck and ruled its happening on the actual host machine running Wolf.
The game stream just stops. The game is still running though, Controls still work, audio still works, but the video feed is frozen.
Any ideas?
@ABeltramo commented on GitHub (Sep 6, 2024):
Are you running the latest stable version? You can update using
And restart the Wolf container.
If that still cause you issues, can you please share the full logs from the start of Wolf?
@IvanCharcos commented on GitHub (Sep 6, 2024):
Yes, I start docker CLI with the following parameter:
--pull=always.Let me know if I need to run specific log levels.
@ABeltramo commented on GitHub (Sep 6, 2024):
Right, so you have two GPUs, and you are trying to use them at the same time, am I correct? How have you set that up? If you run everything on a single GPU does it work?
See the docs for reference: https://games-on-whales.github.io/wolf/stable/user/configuration.html#_multiple_gpu
@IvanCharcos commented on GitHub (Sep 6, 2024):
Originally, I had different GPUs for WOLF_RENDER_NODE and WOLF_ENCODER_NODE.
I since switched to a single GPU for both ENV.
The same problem manifested itself in both configurations.
@salty2011 commented on GitHub (Sep 6, 2024):
In your docker compose can you try changing
-device /dev/dri/
To
-device /dev/dri/renderD12x
Replace x with the card number. Don’t think this will fix it but reduces variables within container
Also just to confirm, both cards are AMD? Looking through the logs it shows AMD driver loading
@IvanCharcos commented on GitHub (Sep 7, 2024):
7900xtx and ARC A770
@masterkoppa commented on GitHub (Sep 7, 2024):
I'm also running into this issue on a fresh install, two AMD GPUs (AMD iGPU and 7800 XT).
Happy to share more details if it's useful but everything here matches my experience as well.
@ABeltramo commented on GitHub (Sep 7, 2024):
Yes, please!
How are you running Wolf, is it the latest version and logs from starting the container up until the error message manifests. Possibly with the
WOLF_LOG_LEVEL=DEBUGset.@IvanCharcos commented on GitHub (Sep 7, 2024):
I am still running some tests.
This is more complicated because there are a lot of variables, like which kernel is being ran and which drivers are being used.
I have had some issues with 6.10.7-xanmod1 that seems to have been fixed recently.
I will continue to test, and by test I mean play games, and see if I can get the issue to manifest itself again.
@IvanCharcos commented on GitHub (Sep 7, 2024):
Will get you the DEBUG level log shortly.
logs.txt
@IvanCharcos commented on GitHub (Sep 7, 2024):
I think I see what is happening here. It has something to do with the bitrate set in Moonlight.
For both laptop and Steam Deck OLED, both of these devices are using Wifi-6e.
If I push for bitrates around 50Mbps, it seems to reach the crashing point much faster than if I used a lower bitrate, say 30Mbps.
DEBUG_logs.txt
Error is at line 18136.
I will do some more testing.
@masterkoppa commented on GitHub (Sep 8, 2024):
I can confirm IvanCharcos suspicion, I can do 4K, 150MBps streaming while on gigabit Ethernet without issues now. As soon as I switch to WiFi it starts to cause the original bug.
@IvanCharcos commented on GitHub (Sep 8, 2024):
I will close the issue. I think this is more of a WiFi issue than it is a Wolf one. Thanks again. Awesome software BTW!