Might be worth to open up an issue on Github or a thread on Discord. I haven’t tested pipewiresrc but there’s probably some clue in the Wolf logs. Besides, have you mounted the host XDG_RUNTIME_DIR, passed the right env variables and so on?
For streaming the host desktop Sunshine might be a better fit btw…
Is each “game entry” in moonlight a shared instance?
Quite the opposite, at the moment each Moonlight client will have a completely isolated session and they can play different games. This obviously defeats co-op which is something that I’d like to work on by adding proper user management and a remote UI in the next release.
How would I go about making a generic linux desktop from a given Linux distro?
In our latest images we have default support for Sway, you could easily expand that base Dockeer image with all the apps you need or make a different image with the DE that you’d like to use. The project is very open ended and only a few base components are needed in order for any image to be streamed to a remote client.
Yep, this is one of the main reasons why I started this project in the first place: I wanted to stream games from the same VM where Jellyfin is running.
Yep that’s perfectly possible, the sessions that will run under Wolf will be completely isolated from the host. Besides, that’s how I run it on my desktop dev machine!
No worries! Let me know how it goes, any feedback is highly appreciated!
Sounds like this is exactly what this is capable of: you run Wolf on one beefy machine, and then you connect to it from multiple clients to play games or run a full desktop remotely!
I’m not sure what you are referring to but in the chart Mesa and Kernel layers are shared between the running applications and Wolf in a single host, no VMs involved. One of the main reasons behind the project was to allow exactly this so that you wouldn’t incur in the big penalty hit that incurs in GPU splitting
As others have pointed out below it’s going to run multiple separated instances of Steam with the limitations that Valve impose (there’s not much we can do there). This project is not limited to Steam though, you could easily run another session from a different device with something like Lutris or Pegasus.
The patches aren’t included by default because I’m not sure about the legality of them and I really don’t want to get into troubles over this. I should research a bit more into this though.
Not yet, but we are working on it!
It does! It’ll automatically create new virtual displays on demand when a new client connects and it’ll match the client resolution and framerate.
Thanks! The concept is fairly simple but it took me a long time to get to this point! 😅
Thanks! Let me know how it goes!
Great questions!
Did you look into memory deduplication?
For the Steam library I suppose? There’s been some discussions around it both in Discord and Github #83 #69 It’s something that I should definitely research further but I’d really like to address it even if it’s just something that might be done outside of our container… Would you like to help us?
Is client software sunshine or custom software?
Wolf is an implementation of a full Moonlight backend from scratch; there’s has been many reasons for this but mostly it’s because Sunshine has a lot of global and intertwined state and it would be very hard to add support for multiple independent users. I try to contribute upstream where possible; for example I’ve helped merging our custom library for virtual inputs so that users of Sunshine could also benefit from the new virtual joypad implementation and support for Gyro, Acceleration and so on…
Ooops that was a lazy leftover from my side, sorry about that. Thanks for letting me know, I’ll fix it soon!
It’s probably failing to parse the config.toml file, although that should usually print a proper error line. Have you tried deleting the file or copy and paste the default?
Others have asked for it and I guess some of it might even work given that WSL2 has GPU support. I’ll keep this issue updated as I get some progress on this front!