Josh.5

You cannot run this container in bridge network mode if you want to use inputs outside of steam big picture. Bridge will prevent things like controllers from working in game.

I took a quick look into this. This is happening because steam is creating a drive link "Z:" to your root path "/" as a symlink. If you then view this from the host Unraid OS it looks like this: This is not something that the Steam Headless container is doing as much as it is what the Unraid host shares are doing. It has created a symlink to / and so if you brows that you will see all the things in your root filesystem. Hopefully this helps you in finding a solution that works for you. As for this container, there is not really any point in finding a fix. The solution as far as I can tell is to better configure your network shares for Unraid.

This thread seems to be getting more popular this week.... I don't come here often to provide support. If anyone needs support fir anything from me, reach out to me on Discord through the link in the first post.

I'm not following sorry. Are you able to share a video or something explaining what is happening?

Would you be able to DM me on Discord to discuss your progress?

Awesome. Sure thing

Uinput plugin is no longer required in the latest Unraid release. I have never tried with Bluetooth devices. Only keyboard and mouse.

I think it may be time to retire this lancache-bundle template. I have not been using it since I got access to fibre internet (which downloads games faster than pulling them back off the array). And the official monolithic docker image from lancache has come a long way since I created this bundle to combine everything into an AIO. While I really appreciate the $12 donation I received this year for maintaining the lancache-bundle docker image and this template, I probably will have to hang up my hat on it this month.

I have not used the lancache container for a very long time. I tried to maintain it for people here who have been, but I cannot really test things and am flying under the assumption that things have been working fine for the people who have been using it. I'll probably be pulling the template from CA when I stop using Unraid next month as I have not intention of providing further support for it for this platform.

You do not need a GPU to use Unmanic. That is a pretty outrageous statement to make. Using a GPU inside the official Unmanic Docker container is an optional thing that you can do if you wish. You can also use Unmanic on the VM that you have passed your GPU into if you like. Unmanic is a tool with a lot of capabilities of which only a very small sub-set would even have the option to take advantage of a GPU.

Just as a notice here, I will soon be steeping away from using Unraid to develop and maintain my projects. I will still provide support for Unraid for all of my projects, but that will be moved and only provided via Discord with a focus of providing that support agnostic of the platform. Anyone wishing to reach out for any assistance or to provide any feedback should join us there. I will be focusing my future development on providing better compatibility for platforms that are not Unraid, and as such it makes no sense to remain here in this forum. I may still pop my head into this forum from time-to-time, but please do not expect support from myself from this thread going forward. Please move all support related questions to Discord. https://unmanic.app/discord

Don't unplug the other GPU. You need a GPU to use Steam Headless. You cannot use the GPU that you have isolated for the VMs. Without full logs, I cannot really say exactly what the issue is. You should also post any logs found in ~/.cache/logs inside the container.

First post updated. You probably will find that you cannot use the GPU on the host for anything if it is being passed through to a VM. I'm pretty sure (but am not going to test this for you) that the NVIDIA docker runtime will not work without installing a NVIDIA driver on the host. Therefore, I'm pretty sure the linked documentation is correct for anyone who wishes to use Unmanic with the latest version of Unraid and a NVIDIA GPU.

These are all games I downloaded from the steam headless container

Still working fine for me. I've played Batman, Control and Jackbox this weekend.

I would need to look into it. I think this may be happening because the X config is using a dummy monitor. I will need to run a few tests to see if we can massage this feature a bit to allow us to "force" a particular output for people such as yourself. I don't think the setup is any different between your server boards or the consumer hardware like I have. The end result is the same. So I should be able to replicate your requirements and produce a solution.

Please note that I may be removing that flag in a future update. This will be in favour of running sunshine inside its own docker container to improve compatibility and also to remove my responsibility to maintain the service.

Your assumption is incorrect. As I just mentioned in my post a few hours ago: For moonlight streaming, you can use sunshine with Intel and AMD GPUs. I don't have an AMD GPU at this time so I cannot provide direct support, but as Intel and AMD GPU drivers are supported in the Linux kernel, these work without any additional steps like an Nvidia GPU would require. There are numerous people in this thread and on Discord who are using this container fine with their AMD APUs and GPUs. I use a 4th, 6th and 11th gen i5 as well as a GTX 1050 ti for development and testing of this container and my other containers.

I am not a big retroarch user, but I found the steam version to have everything that the non-steam version had. You can still add custom cores to your steam version and it works fine. If you don't want to install retroarch via steam, do it with 'apt install retroarch'

Any GPU will work (Intel, AMD, Nvidia. And any integrated or dedicated GPU). I noticed myself that Intel GPUs did not work very well with no monitor plugged in. It works fine with a dummy HDMI plug tho. I will eventually get around to looking into why the monitorless setup limited monitor resolution to be so low.

This plugin uses regex. So just add a string to include everything except 2160p and it will ignore everything except files with 2160p

It is possible. I do it with my little SFF (non unraid) box. That only has an Intel igpu tho. Do you have your Titan configured as the default output in the bios? I believe it only ever detects monitors on the default output at this time. I have not paid much attention to setting it up any other way.

You should be able to do this with NVIDIA_VISIBLE_DEVICES https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/user-guide.html

This is not something I have seen. Could be something specific to your CPU or the game you are running. (I'm using 4th, 6th and 11th gen Intel for testing) Have you seend what a download or file copy looks like on your CPU? Does it use only one core also?

Are your games stored on the array when you load them in the VM?