Jump to content

ich777

Community Developer
  • Posts

    15,752
  • Joined

  • Days Won

    202

Everything posted by ich777

  1. Then I would recommend to stick with the official container, since they now also have AMD GPU support I think I will deprecate my container sometime in the near future since I've mainly created this container for the users with AMD GPUs because the official one hadn't support for that.
  2. Can you please try to install a second instance from my container with different directories and a different name? This wouldn't be the first time I see that some changes break the container and it wont transcode for whatever reason. And please use VA-API and not QSV!
  3. You got a 139 Error, this actually means that ffMPEG crashed before it exited. Have you yet tried the official Jellyfin container for testing purposes if it's the same there too? Have you already tried another file too?
  4. I will think about that again what could be done how in my container, but at least the BepInEx version should download fine if I'm not mistaken. I really learned to hate Terraria in general the last few years because first the developers from Terraria changed one or two things that broke my container, then the developers from tModloader changed I think about 4 times things that ultimately breaks the container. When is the last update/patch released? Keep me updated and I will look into it after it is released.
  5. Can you send a log with VA-API, I really recommend to use VA-API instead of QSV! Have you already upgraded to 6.10.3?
  6. What I really think needs to be done is that the developers from Valheim+ release a new package with a updated BepInEx package included.
  7. Please switch from QSV to VA-API and disable "Allow encoding in HEVC format".
  8. I've deprecated this version from the game since the developers changed again something and broke the whole container again, this is really frustrating for me and I will not fix or release a new container for tModloader. I will maybe support BepInEx but not Valheim+ I think... Haven't decided yet what to do...
  9. Never done such a container and if there was one in the CA App then it was not from me... I can look into this but I have to say that I've stopped creating containers for games that I don't own because giving support if something breaks is a real pain for me and in this case, I don't own the game... If you are willing to Donate the game to me I will of course look into it but can't tell for sure if it is working through WINE.
  10. This has strictly speaking nothing to do with the exporter itself this is more of a Unraid thing because Unraid doesn't use systemd. You can try of course to add both but I don't think that you have any benefit when adding the systemd parameter because as said above Unraid doesn't use systemd.
  11. Can you post your Diagnostics please? On what Unraid version are you? What CPU are you using...? I've now tested it on my i5-10600 and everything works as expected.
  12. Please remove this line from your go file: modprobe i915 because you have installed the Intel-GPU-TOP plugin and it will actually enable your iGPU if needed. I would strongly recommend that you upgrade to Unraid 6.10.3 too. Please also post a screenshot from your Jellyfin Playback section.
  13. Yes, why not? But I don‘t understand why you would add —collector.systemd since Unraid doesn‘t use systemd
  14. What do you mean with before? Are you sure that this is caused by the update to 10.8.0? Have you yet tried to disable transcoding to h265?
  15. Please try to use VAAPI instead of QSV if you are using QSV
  16. With that little information I can't help any further, please post your Diagnostics.
  17. I think I will remove BepInEx and Valheim+ from my container in the future because this causes only headaches for me... That's why I usually don't support Modding in my containers and provide only the base functionality.
  18. WORKAROUND for Ubuntu, Debian Bookworm+, Fedora 36,... containers that wont start. Add this line to your container config at the end: lxc.init.cmd = /lib/systemd/systemd systemd.unified_cgroup_hierarchy=1 This will actually enable the containers to start.
  19. Then simply disable Valheim+ and enable BepInEx in the container template. Valheim+ is actually downlaoded from GitHub. BepInEx is downloaded from Thunderstore that‘s correct but it isn‘t downloaded when Valheim+ is enabled because Valheim+ bundles his own version from BepInEx. Valheim+ has to update his BepInEx version that is bundled, please also create a post on the issue tracker on GitHub, this will hopefully speed things up.
  20. It‘s „photprism“ in between the slash and questionmark.
  21. Here are the two log files from my server with Valheim Plus enabled and disabled, the first also just segfaults where the one with Valheim Plus disabled runs just fine. ValheimPlus.txt ValheimVanilla.txt This is the exact same server...
  22. Can't confirm that... From my testing if I enable ValheimPlus the container doesn't starts and segfaults. When I disable ValheimPlus lthe container starts just fine.
  23. Since you are using Valheim Plus there is nothing I can do about, see this post please: I think the last update to the game (not the container) messed up a lot of dedicated servers... The only change to the container was to move the world files to the new location...
×
×
  • Create New...