[Dedicated Server, Windows downloaded] Settings loaded from ServerHostSettings.json incorrectly

5 votes

BRANCH: (Live)

REPORT:
When trying to host a server using the dedicated server github as a guide, I couldn't make my server connectable, as it previously was.
When I checked the logs, a few key settings were read wrong, or as their default values, such as both ports, address (being "null"), and "ListOnSteam" set to false.
Issue has been reproduced on two different PC's on the same network, using dedicated server dowloaded from the same Steam account.

Have you tried any solutions?
PC Restart
Updating Steamworks Common Redistributables
Tried using different ports
Reinstalling the dedicated server software

For server issues, is the server Official / Public non-official / Private?
N/A

DISCORD ID:
Sphyrwa#8940
--------------------------------

Known issue Suggested by: Sphyrwa (18 May, '23) • Upvoted: 06 Jul, '23 • Comments: 7

Comments: 7

18 May, '23
shortybsd
Use on your launch parameter example -address "192.168.1.100" or whatever your ip is. Here is my batch file for an example

@echo off
set SteamAppId=1604030
title Blood Raven
echo "Starting V Rising Dedicated Server - PRESS CTRL-C to exit"
REM -serverName "Blood Raven"
@echo on
VRisingServer.exe -persistentDataPath .\save-data -saveName "BloodRaven" -GameSettingsPreset "BloodRaven" -address "192.168.1.242" -gamePort 9876 -queryPort 9877 -logFile ".\logs\BloodRaven-VRisingServer.log"
19 May, '23
Chris Merged
Branch: None

Report: We're now unable to launch our dedicated server after the update. The command window opens, I can see task manager allocating memory, then it just drops and the cmd window closes. The log doesn't seem to provide much info (but can post/send if needed). We've already completely uninstalled and reinstalled and tried launching a new server with default everything and still nothing.

This is a dedicated private windows 2019 server.
19 May, '23
ImPopoto Admin
"Unable to launch dedicated server" (suggested by Chris on 2023-05-19), including upvotes (1) and comments (0), was merged into this suggestion.
Click to enlarge

19 May, '23
Maddie
Was about to post my own report and saw this, I went to setup a server today and got a similar situation, server launches for about 30 seconds then crashes with Unity errors.

"Microsoft Media Foundation video decoding to texture disabled: graphics device is Null, only Direct3D 11 and Direct3D 12 (only on desktop) are supported for hardware-accelerated video decoding."

Is the server build meant to need a GPU?
This was done in a KVM based virtual machine running windows 2019 server so if the error is there on my end would love to hear why and any solutions.
20 May, '23
Sphyrwa
Update:

Have also tried forcing ports and address with the bat launcher, but then the server does not start at all, with log saying it failed to open sockets with those ports with Steam.
I have also tried installing the server on the windows drive, but that yielded same results.
Tried launching the server in admin mode for same result.

Server could be connected to through localhost IP if I launched the server straight from the dedicated server .exe, but the settings were all default, and the server was not listed on the server browser.
20 May, '23
Sphyrwa
Additional update: I got the server to get listed and connectable with Windows Game Server Manager https://survivalgamingclub.com/windows-game-server-manager/ and a plugin for V Rising https://github.com/dkdue/WindowsGSM.VRising .

So there is something wrong with how the dedicated server loads in the configuration files by default.
21 May, '23
Kapzy
I had some issues with mine being connectable both internally and externally until I realized I needed to open both TCP and UDP ports on the windows firewall and on the router port forwarding to the server.
EDIT: It may actually only need UDP - but I know it worked after I did both :)