ich777

I think what happened is that you still had the old version installed, the Plugin Update Helper updates only when you reboot or you are installing a new plugin which needs modules for specific Kernel versions. I've tested upgrading and downgrading between various versions from Unraid. EDIT: If you are curious to test, you can downgrade to 6.10.1 and after a reboot again upgrade to 6.10.2 and it should work just fine.

What message did the Kernel Helper gave you?

Thank you, keep me updated. Have you yet tried to cinnect through you local IP if it‘s the same?

Isn‘t Unraid enough to monitor the containers? I really don‘t know how you can do that, maybe through RCON on some games… But for other games I really can‘t tell…

Does the container maybe restart? Have you changed anything in the template or in the config from ArmA itself? I‘m not too familiar with ArmA…

Are you testing 4K to 4K? If yes h264 is not really made for 4K (that‘s what Emby tries to transcode to) h264 is made for up to 1080p, but you can of course transcode to 4K with it but that‘s not verry efficient… that‘s why h265 exists. Can you share the transcoding logs? I will do my own testings hopefully after weekend.

Please note that throttling is by default enabled in Emby. This seems more like a driver thing… Have you also tried with no display connected on 6.9.2 and 6.10.0? Also are we talking about dropped frames or FPS while transcoding? On what client did you tested that?

Please share your results here. I'm really curious to see them and test this on my machines.

This has nothing to do with transcoding on the server usually, dropped frames are usually caused by the player (client) and not by the server... Do you have throttling enabled in Emby? On my test machine which is a Intel J3160 there is no difference in transcoding if a display is connected or not. As said above this was simply a bug in the GVT-g or Intel-GPU-Top plugin which actually prevented the display from outputting anything or better speaking the output also happened but not visible.

Disable "Wait for F1 on Error" or something like that in the BIOS, every manufacturer names it a little bit different...

Why do you not disconnect it if you don't need screen output?

About what container are we talking here? Please also notice that GitHub had some issues about 2 or 3 hours ago.

As said over in the GVT-g thread this is expected behavior that it stays on. Is it not possible to turn of the monitor or disconnect it entirely?

AFAIK no. For RCON you can upvote this here: Click That should be possible through RCON.

No, please see this post here:

The CPU governor should not affect the GPU…

Nope, only the Core-i series and Xeon series are supported as mentioned in the first post. This is basically a "Atom" CPU and is not supported.

Wouldn‘t it be better to crate a non root user and log into that account? Depending on what you are want to do that‘s not what you want to do… I have to look into what LXD does to change the language in the container, but from what I saw my container changed to the right locales when I changed it, have to look into this again. What happens when you try the following from your Unraid Terminal with this command: lxc-attach CONTAINERNAME su root Edit: lxc-attach CONTAINERNAME su

This is really strange, most people that are having issues are on AMD systems… Please check if the container data is spread over multiple disks if they are spread over multiple disks delete the container and the directory for the game, pull a fresh copy from the CA App and change the path to the gamefiles to /mnt/diskX/appdata/vrising (change X to the disk where you want to have the data on) and see if it works.

I think it would be great to do sich things throught the CA App rather than through the plugin itself, this will be only integrated for testing. I have already made two scripts. The first will install a full (minimal) Desktop Environment and the second one will install Homeassistant Core to a fresh installed Bullseye container, these two scripts are more a PoC and for testing, but the work perfectly fine. 😁

Have you yet tried to set the locales in your container if yes, how dod you try it? Please read the first post again. LXD is not included in the package because it will add more complexity and you can basically do everything without it.

Nice, that depends always which is set as basic shell in the container for the user.

Yes, exactly, this plugin is currently in development and features will be added over time like mentioned in the first post. I've updated the plugin today because my PR was accepted yesterday that quickly that I had to implement it like it is now, I will maybe add a drop down or something like that so that you can choose which shell you want to connect to, but I'm not too sure about that now. I'm currently on a short vacation and this will take some time. Yes, the coding in the LXC containers is different that's why it looks a little awkward, you can theoretically change that in the LXC container but you don't have to by using simply bash, fish, or whatever is the shell of your choice. I'm also open to ideas and feature requests but it can take some time since I'm really busy currently (like always... ).

Please update to 6.10.1 This means that the server doesn't even start, on what CPU are you running the container? Do you have a cache drive installed? Do you changed anything in the template?

Did you even take a look at the plugin page itself yet, the driver version 470.94 maybe??? On what Unraid version are you? The driver 470.94 is available for every Unraid version so far and I will compile it as long as it compiles on newer Kernel versions. Of course when you are on Unraid 6.9.2, which is now outdated because Unraid 6.10.1 stable was released, you won't see the version because I list only the last 8 drivers but it's there and you have to enable it manually.