Jump to content

ich777

Community Developer
  • Posts

    15,751
  • Joined

  • Days Won

    202

Everything posted by ich777

  1. What have you done that it is working now? Others shouldn't have that issue, this is a very unique and strange issue to me... No you can leave it as it is but don't do these steps if now all is working for you because this will maybe mess up your existing installation. These are basically the steps that the plugin is doing.
  2. See my post above this one. This is theoretically possible when the VPN supports it and you use something like my OpenVPN-Client container in conjunction with the container that you want to route through.
  3. Please don‘t give advice that‘s not correct. What you are experiencing is that something seems wrong with your hair pin NAT, that‘s why you don‘t see the server on the Server List in game, but you should be able to connect to the game via Direct Connect and your local Unraid IP.
  4. Yes, for the desicated server that‘s true but I need the game too, what if a user has an issue with it? The I have no way of debugging. Anyways was about only a few Euros. Why would you pass over your Steam credentials, if they are needed thay are marked with a red asterisk in my temlate and they are visible and not hidden under the Show more settings. You don‘t need the sh file. This sh file is basically the same is if you run multiple Docker containers all from the same directory. Simply take the template from the CA app and set up your first server, after that click on the Add Container from the Docker tab at the bottom and choose your first Docker template again, then (this step is really important) change the name at the top to something different from the first server, change the ports in the Game Parameters Variabel, delete the two port entries and create new ones with the according ones that you‘ve changed in the Game Parameters and of course with the right protocol, change the server identifier and then click apply. This will start a second instance from the container but from the same directory (I hope I haven‘t forgotten anything but I think you get the point). The container was already created with this in mind. The only thing that I would recommend to is, if you‘ve enabled autostart on all your containers that you delat the start from the first to the second about 60 seconds (or more) to give the first server the chance to pull a update if there os one.
  5. You have to change the server name in the Docker template because the start parameters (that’s how I use the server name parameter from the template) override the files.
  6. You usally don‘t have to do that manually, please check that your container is up to date!
  7. Have you read the description from the container? If not the files are stored in …/vrising/save-data/Settings …and no, those files won‘t get overwritten on a update.
  8. Have you yet tried to restart the server once? Please post the log from the log directory.
  9. These setting are supposed to go into the game/server settings files not the game parameters.
  10. I think this has to be in lower case. Remove the double quotes from there. Otherwise it seems okay. This shoudl also help: Click
  11. Everything seems fine from what I see from your log. Can you try the following: Reboot without the driver plugin being installed Issue these commands and post the output here (copy and paste the whole thing should work fine): mkdir -p /tmp/nvdrv && cd /tmp/nvdrv wget https://github.com/ich777/unraid-nvidia-driver/releases/download/5.15.40-Unraid/nvidia-515.43.04-5.15.40-Unraid-1.txz installpkg nvidia-515.43.04-5.15.40-Unraid-1.txz depmod -a modprobe nvidia rm -rf /tmp/nvdrv nvidia-smi
  12. Should work fine when it's DisplayLink certified.
  13. You can of course send the Diagnostics.
  14. Yeah, in it's current state Alder Lake is a mess... Think about the new Alder Lake P/U processors. Sadly enough Alder Lake ≠ Alder Lake... Really curious if it works, hope the best for you...
  15. Looking perfectly fine. I think that Intel messed up the drivers really badly lately but it should be fixed in Kernel version 5.18-rc2+ but I haven't tried it yet because I have no hardware on hand to try it. You boot with UEFI from what I see in your log, is that correct? Have you yet tried Unraid 6.10.0 stable (TBH I think it would be also the same like on RC8)?
  16. Sorry for the delay... Forgot a bit about that... I've test it now and I can connect with any issue whatsoever. Can you share a screenshot from your configuration on the main iSCSI page?
  17. Hab vergessen zu posten, bei mir funktioniert es bisher auch einwandfrei, hab aber nur 2 Snapshots eingestellt und die sind von den letzten 2 Tagen.
  18. I think so but I would recommend that you ask this on the General sub forums here on the forums. I've never done this before but it should be somehow possible to turn it off with a parameter in the syslinux.conf
  19. Ah, if you are using it for GVT-g you can't do that, just leave it as it is. However you can install the Intel-GPU-TOP and GPU Statistics plugin in conjunction with the GVT-g plugin.
  20. You don't need too but in Unraid 6.10.0 the iGPU is activated by Unraid itself, however if you want to see the iGPU usage on the Dashboard from Unraid you have to install first the Intel GPU TOP plugin (which activates your iGPU) after that you install the GPU Statistics plugin then you have to go to the settings page from the GPU Statics plugin, select your iGPU and click Apply. After that you will have the iGPU usage listed in the Unraid Dashboard. This plugin was mainly created to enable GVT-g from your iGPU which activated as a side effect the iGPU.
  21. This was actually a bug... You don't need this plugin anymore or the Intel GPU TOP plugin to enable your iGPU.
  22. Isn't unplugging or turning off the monitor a option for you or are you running Unraid on a laptop? It should be possible to turn off the console output but I would recommend that you ask that in the General support forum.
  23. I will look into this ASAP and report back. Also please see my post above this one about the Cache and Mover situation. EDIT: I really have to appologize for the inconvenience, there was a mistake in my template where the UDP2 - Game Port was the wrong protocol type, please change that in your template to UDP and you can connect (already changed it in the template but you have to edit it manually in your template): After that I can connect fine. BTW did you also change the port in the default.ini which is located in the main directory from the container:
  24. Please don't do it like this, your appdata share should always stay on the cache (at least from my opinion), you are giving applications/games a hard time to run from a share which is transferred to another disk when the mover is running. I always recommend that you set your appdata share to use cache "Only" or "Prefer" in the Share settings. If you are not comfortable with that I would recommend to create a new share that use this settings and when installing container point them to this share (absolute path - not FUSE path) eg: /mnt/cache/games/vrising Which files did you edit, or at least in which location? The files are located usually in .../vrising/save-data/Settings On my server it works just fine otherwise the settings PvE and my server description won't work. If you want to take a look at it simply search for "Unraid" on the server list and try to connect. I can only think of an issue with the cache or your share settings that the Mover moves the files to a different disk.
  25. The default ports for this game are 9876 and 9877, nothing even listens or connects to 27015. Do you have the port 27015 in the V-Rising template? If not, nothing can connect to it because the port is basically non existent if you don't publish it in the template. I've made a screenshot from my server where you can see which ports are used (ignore the first two): Are you talking about the in game server browser or are you talking about the Steam Server browser. I also think that it's nearly impossible that KF2 can show up on the in game server list from V-Rising because those are two different engines, please double check your port forwarding in your router, maybe there is something messed up.
×
×
  • Create New...