xWeegix

If I remember correctly you have to move the contents of the "South Weoca Valley" folder to the ../7dtd/saves/South Weoca Valley/<GameName> where <GameName> is the value you put in the serverconfig.xml file and leave the <GameWorld> value as RWG. You'll likely have to make those folders. edit: fixed typo

ahh good to know. App ID 2334200 It looks like it just stalls on asking for 2FA but it gave the reason of too many logins from this IP for rate limiting so it was my fault trying quickly to automate the 2FA. I was just about to manually try to download it with steamcmd so I would have found that sadness of the 2 steamclient.so files taking the 70MB~ still. Thanks for trying 💕 and I guess we'll have to wait and see for steamcmd to work.

I was trying to get The Front to work with your dockerhub image (admittedly I'm much too early) and it seems like the anon login doesn't allow you to actually download the game server files but it downloads fine when logged in on windows. I'm just fighting with their 2FA to get it all working in one session since the code changes with each session. Since I'm rate limited from trying to log into steam I was looking at GitHub - Weilbyte/steamcmd-2fa as a possible solution that could be added as a variable to the docker template or as a secret in the shared steamcmd. Dunno if any of this helps but hopefully it becomes much easier to get this running in docker.

I'm not an expert but as far as I know you can't comment out ffmepg since it's required.

I'm going to pick up an A750 to use replace the 1080 in my main rig... mostly to follow along with Linus' Arc challenge but once the Unraid kernel gets to v6 I'll move it over that way. Keeping an eye on this thread and hopefully all goes well enough to replace my old quadro. 🤞

This only works via IPMI on Supermicro and Asrock motherboards. Sorry but you'll likely need a fan controller to set those fan speeds.

I would start with checking those links to where some people have modified the plugin to see if there are settings files there. I'd bet there is a few ways to figure it out but it depends on where and how far you wanna dig. Probably easier would be to check the plugin page on github and look for the path there. edit: just a quick look in the install script make this look like a good place to start

You'd have to ask @dmacias although there was an update this year with the frequency on a downward slope. Seems like you'll have to make your own updated profiles for anything that isn't supported out of the box.

I'd also throw a +1 since the new BMC versions add some nice functionality. Edit: I forgot about this. So I'll report back after going through some of that level of jank. Edit2: So just going through replacing the ipmi2json and ipmifan files and running configure it actually detected Fan1 as Fan2 and found no others. In the Fan Control tab it populated Fan1 as Fan1 afterwards but when you made changes to Fan1 in the it would update Fan2 in the BMC and set Fan1 to the minimum 20% quickly causing an overheat if you have a load. So looks like some debug time is required if someone has the time but it's not too far off... just not for me in the early morning on a Saturday.

I uninstalled Nvidia driver plugin, rebooted, reinstalled Nvidia driver plugin, restarted, then reinstalled GPU Statistics. Downloaded your jellyfin docker and it kept the old template so I added the --runtime=nvidia to extra parameters and the jellyfin docker now boots and nvidia transcoding works. I checked the transcode logs and the GPU stats plugin and found it is all working as expected. ：D I did end up checking the driver package with that method and it passed the checksum. I even changed the driver from the most current version v470.63.01 to v465.31 which I knew worked and that didn't fix anything. So the nvidia driver plugin install broke for some reason and a full reinstall of the Nvidia driver plugin was required.

Ahh yeah so using by brain and some moderately intellegent googling it seems like my Nvidia driver installation broke and the container toolkit isn't working with docker atm. I just reinstalled the Nvidia driver plugin. I should've known when the GPU Statistics plugin was also not working but still installed. As for the versions it was probably coincidental that I updated jellyfin from 10.7.5 and some other things where things ended up breaking. Thanks for the quick reply.

I seem to be having an issue starting the docker with the extra parameter after the last update. --runtime=nvidia When I update and run it the docker fails to start saying the --runtime=nvidia parameter is invalid. Any idea what would cause that? P.S. Going short of reverting to the last version I did force download and reinstall the lastest docker image without clearing the appdata folder. P.P.S. It was working wonderfully prior to the update and I do have the Nvidia Visible Devices parameter set using the Nvidia driver plugin.