chandz05
-
Posts
6 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by chandz05
-
-
On 7/19/2023 at 9:28 PM, RebelLion1519 said:
So after further fiddling, I've gotten Steam to stay open in the VM. Games themselves aren't opening, though. Steam shows they're open, and Steam Link shows that there's a game in progress. But the game never actually appears. If I go into System Settings in Steam though, I don't think it's detecting my actual graphics card. Maybe that's the problem, it's trying to run stuff on the virtual card? I have the Radeon TOP plugin installed, am I missing a step?
Can you see your graphics card in the VM? Hopefully someone else with a discrete AMD graphics card can help you from here
-
On 7/17/2023 at 6:05 PM, RebelLion1519 said:
Hey, I finally successfully downgraded to 6.11.5, and I'm still having issues. The "loading user data" window goes away, and I think Steam is running in the system tray. But I can't actually get the Steam interface open. I only need to be able to get Steam Link connected to my TV, then I'm fine with a UI in the container. I'm on an AMD dGPU now. Forgive my not understanding what you mean, but how do you apply the -vgui workaround? How do you get the "small mode" option?
Sure! For -vgui, in the VM, navigate to this location:
/home/default/.config/autostart
and edit (right-click->open with->gedit) the Steam.desktop file. At the end of the "Exec" line, add "-vgui" and save. Since this is the autostart file, I would do a container restart. I believe you can edit the Steam executable itself, so it will start with -vgui enabled whenever you open Steam, but I did it the autostart way. When the container restarts, Steam should load up. At this point, only the store page was loading for me. In Steam, on the top menu, click "View -> Small Mode". Your steam library games list should pop up. You can also switch to Big Picture mode from the View menu, but like I said, I have not had success with that.
Edit: it is worth noting that as time goes on since the new Steam UI was launched, the old UI seems to get more and more broken, so there may be a point where this workaround will not work at all
-
On 7/6/2023 at 8:23 PM, Josh.5 said:
Do not upgrade to Unraid 6.12. I cannot express enough how annoyed I am with the amount of time I've wasted this week upgrading my system to 6.12 to explore this issue. This is headache inducing. The OS version has so many underlying issues that are not at all related to Steam Headless and is preventing me from be able to even improve the container. Eg. issues with the mover. Issues with services like SSH just stopping outright, issues with Dockerd.
I cannot stress enough, do not upgrade to 6.12.x. If you are on 6.12, then consider backing up your /config directory on your USB stick and downgrade back to 6.11. This is what I am doing at the moment.Hello, so I have been lurking this thread and testing out this container on UnRaid 6.12, then 6.12.2 and now 6.12.3. I was also getting the never-ending "Loading User Data" screen on 6.12.2, and the -vgui launch option didn't seem to work. However I have now done a clean install on 6.12.3 and -vgui *does* work, steam launches beautifully, but some of the screens (including the library lol) do not load. The workaround for that is to hit "view"->"small mode". This will load your library list, with none of the fancy game art. It is worth noting that I am *not* using a dedicated GPU but have passed-through my Intel CPU integrated graphics (/dev/dri). I can install and launch games (tested with FTL). There is a caveat though, which kinda defeats the whole purpose of the being "headless" - with -vgui enabled, Big Picture mode is also broken. It just doesn't load. It seems like Steam has also removed the option of loading into the old Big Picture mode. I am assuming the reason the new Steam UI/BPM doesn't load is because I'm using integrated graphics, so I am hoping someone with a dedicated GPU can now test this and get it working on 6.12.3+
-
14 hours ago, veritas2884 said:
I fixed my issue. I browsed to /boot/config and renamed the network.cfg to network.cfg.old and rebooted. It forced unraid to recreate the file and now everything works.
Thank you so much! This fixed the issue for me too. Only noticed it yesterday when I was actually trying to access my server from outside my network and have been fighting with it since.
-
On 2/1/2022 at 5:15 AM, RobV said:
I used the SWAG recipes example conf file and just changed the upstream app to point to my unraid server IP and upstream port to the host side port. I made sure I had the media share in the SWAG docker container as per the instructions in the example conf file. Restart SWAG and it is now working perfectly!
Hey sorry for reviving this, but how did you get your media working correctly? I've been playing around with the docker container but can't seem to get images etc to render through SWAG. Works fine locally though
UPDATE: I figured it out... for some reason I had blinders on and completely missed the multiple instances of reading that I need to update the SWAG docker container itself.
[SUPPORT] EUROTIMMY - Reactive Resume v4 (RxV4)
in Docker Containers
Posted
Hello, thanks this helped a lot to get my instance working! However I would like to note that for STORAGE_URL I had to set it to <MINIO IP>:<MINIO API Port> in order to get PDF downloads working. Hope this helps someone else too!