ich777

You should not use the whole path, I recommend doing it like that: and: IIRC this should work fine.

Where do you append this pattern? Can you be a bit more specific please?

Have you tried it like that: [P-Zp-z]* (please note that this pattern has to be appended to the end of the source like: /path/from/source/[P-Zp-z]* ) Since luckyBackup uses rsync as the backend this should work totally fine if I'm not mistaken.

Is this what you where after? 535.43.02.txt

You can always use: nvidia-persistenced if you are expiriencing any issues related to the fan or power draw since nvidia-persistnenced is in place to make the card think that it is running a dektop environment even when it's not running a desktop environment. Sadly enough you can't controll the fan from the Nvidia cards from the command line at least not on Unraid. Please give my server a bit, I've started the build for RC6 for the latest driver revision, but please keep in mind usually I'll compile the driver for RC versions only one time. Hope this helps, the build should be done right now and you should be able to see it if you visit the plugin page.

It is available for Unraid 6.11.5 but I assume you are on Unraid 6.12.0-rc6 correct? I've stopped auto building new drivers for RC releases only those which are avilable at the release from the Unraid RC version will be compiled and there fore listed in the plugin. Please wait for a new RC release and as said above the newest version will be compiled. As said above for Unraid stable all driver versions are usually compiled when they are released by Nvidia. May I ask why do you need the latest driver version and for what do you use the card? EDIT: I almost forgot to say that the driver which you are mentioned is from Nvidias Beta branch.

Where do you expect it to go? It is located in: .../satisfactory/.config/Epic/ If you open up the log it will also tell you where the saves go.

Sure thing, give me a bit, I‘m currently not at home and have to put the Nvidia card into my test server.

Yes, this is the newest beta driver released a few days ago. It is possible that this is an oversight from Nvidia but in my opinion it is more likeley that they drop this feature when its not reported anymore.

Please post your Diagnostics with the plugin installed.

A screenshot won't do much, the whole zip. But I'll bet that you get much better results with a whole block device.

I don't fully understand but I would always recommend to use a whole disk (block device) for iSCSI because it's simply faster than a image (fileio). Please click on the link Diagnostics, these are not your Diagnostics.

I can't tell if it's making it in the release from the next RC release but I'll try my best.

I would never recommend to use a image file for iSCSI. Is it not possible in your case to use a whole block device (SSD) <- have you already tried that? On what Unraid version are you, please post your Diagnostics.

So is it now working or not, I need a definitive answer, I'll hope you understand that. Are you able to tune a channel and watch it? If it's working I'll add the firmware to the package ASAP.

You've wrote above that you are using the card only with Docker container so I assumed this will be the case anyways. Not with nvidia-persistenced since this will most likely causes a hard crash from your server. If you are using nvidia-persistenced you have to make sure that you've stop nvidia-persistenced before you start the VM. The easiest way would be that you start a transcode (of course where the dGPU is used) after you've rebooted and wait a bit so that it goes to a higher power state. I'm pretty sure it was the same because if you read back a couple of pages (20 or 30) you will find multiple reports about the same behaviour and that is caused because of the above explained reasons. You can safely downgrade and try it again, it will be the same as on the current build. There is nothing changin inside the driver and the driver makes the card even work.

Was sagt "nö"? Brauchst du denn die Pakete aus dem Nerdpack denn überhaupt? Das system temp plugin von Dynamix braucht nur Perl und auch nur dann zu Erkennung welche chips verbaut sind, sprich wenn du auf Detect klickst, spielt aber jetzt auch keine Rolle mehr da Perl jetzt fixer Bestandteil von Unraid ist.

As said, there is nothing I could do about that since this seems to be related to the dedicated server itself and not the container as the container behaves almost the same as if you run it on bare metal.

@andritolion have you yet tried the new files? Wihtout positive feedback I won't implement the firmware files since I don't know if they are working.

Are these friends hosted servers also dedicated servers or do they host that directly in the game? I don't play the game anymore because I simply have no time playing games currently but I didn't noticed micro stutters. You don't have to do anything special and I can't really think why you would experience micro stutters because only of the game server and TBH you are the first one who reported that and I've even never heard of that that a dedicated server is causing this. Maybe report it on the V-Rising Discord or support forums, maybe it has to do with the latest update but I really don't think that it is caused by that. Oh and it is a simple dedicated server running in a Docker container, I do nothing special in the container and it is almost the same as if you run the dedicated server on bare metal.

Are you really sure that the container has write access to the share that you are trying to write to? As said I've tried it and over here it's not crashing, the only thing different is maybe that I'm on Unraid 6.12.0-RC6 but that shouldn't make a difference.

This is really strange, I've now tried it with my account and I have no issue syncing the files. May I ask what files it tries to sync, are there any special characters in there? Is the directory where you are trying to write to writable to nobody:user? A alternative to my container is the rclone plugin which is available through the CA App.

I have attached the new files. The procedure is the same except that the correct path for 6.12.0-rc6 is: /boot/config/plugins/dvb-driver/packages/6.1.29/ libreelec-20230517-6.1.29-Unraid-1.txz.md5 libreelec-20230517-6.1.29-Unraid-1.txz

@Spectral Force is this expected behaviour? Have you ever seen this? I would also recommend that you join @Spectral Force's Discord server for 7DtD help because he helps me out with it since I'm really not familiar with the game: https://discord.gg/VwwYA5h

You can do all of that in the Docker template, just enable the Advanced View in the top right corner after that you can assign cores to the container and limit the RAM. CPU Pinning should be pretty obvious: You can limit the memory that a Docker container can use with this parameter: --memory=4g you have to put this parameter here: The above example will limit the Docker container to use only 4GB of RAM, but I would strongly recommend to not limit RAM usage because you will most likely cause crashes from your game server.