Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
https://vrising.fandom.com/wiki/V_Rising_Dedicated_Server
if he did all the steps above, check if on the ServerHostSettings.json there is a parameter like this > "LanMode": true and if have the -lan parameter set on the start server bat.
check also the github page for more parameter explanations if needed
https://github.com/StunlockStudios/vrising-dedicated-server-instructions
It's a private server though?
To connect to a LAN server, I had to enable the console in the game options and then from the main menu, use the ConnectLan command with the correct LAN IP, port and password. (press ~ key to toggle the console once enabled.)
It should also work from the Direct Connect box with the LAN Server option ticked, but I kept timing out even when I had the correct IP and port entered (maybe because there was a password set on my Wife's LAN server).
There are quite a few ways to figure out what the LAN IP of the host server is:
-On the host PC, click the wifi adapter in system tray and then go in the properties and look at what the IPv4 IP is.
- Go into your router and look at the DHCP client list and pull the IP by computer name
And then unless it's been specifically changed by whoever is hosting, the default port should be 9876.
For me the whole console command to join was
I suspect that they may just be running a hosted game without installing the dedi, which is fine and trying to connect will be the same, but the problem is that a LAN server is unknown to the Steam API as it is basically offline and also doesn't show up in the master server list, so friend invites don't work and normal searching in the server browser will never see a LAN server.
Luckily, once I had connected normally and made a character, the LAN server would just show up in my Continue list from the main menu and I could easily reconnect that way.
You may also have to double check that the host enabled the game through Windows Firewall or it will block all connections including LAN ones. Your router's firewall shouldn't matter, because it's LAN, so we had no need to configure port forwarding on the router to get it working.
Did you copy a local world to create the dedi?
If so, the reason why this happens (only to the host) is that you still have a local world using the same Session ID as the server, so it will only display the local world in the Continue Menu and not your DS.
The easiest way to fix this is to go to %USERPROFILE%\AppData\LocalLow\Stunlock Studios\VRising\Saves\v1\ (copy that into explorer address bar)
Then go into the folder for your local world you copied (random series of characters), and open the SessionId.json file in notepad. Then just change one character in that file. Doesn't matter which. For my local world, I just changed the last character in the file from a 3 to a 4, but I suspect that you can change any single character in the session ID string for this to work. Save the file and restart your client.
That should fix the issue.
TL;DR
If you have a server using the same session ID as a local world, only the local world will show up when you try to continue so you have to reassign the session ID of that local world to something, anything else, in order for the Dedi to show up in the Continue Menu. That, or simply delete the whole local world's folder inside of ..\VRising\Saves\v1\
(the one with the random series of characters).