Fixing V Rising lag starts with identifying which side is failing. If one player stutters, start with that player’s connection, background traffic, drivers and game files. If everyone rubberbands together—especially when a local world saves—test save compression and host workload. On a dedicated server, inspect server performance, UDP ports, firewall and list-registration settings. The safest first pass is reversible: use wired Ethernet, stop downloads and streams, restart the router and PC, verify Steam files, and update the game, drivers and operating system. Then apply the host-specific tests below without deleting your world.
This guide covers rubberbanding, disconnects, servers missing from the browser and the “Unknown Status” message on PC, including local co-op worlds and the current 1.1.x dedicated-server setup.
What kind of V Rising problem are you seeing?
Match the symptom to its likely cause before changing settings. The pattern—one player or everybody, only during saves or all the time, list failure or actual reachability—usually tells you which branch to test.
| Symptom | Most likely branch | First checks |
|---|---|---|
| Only one player rubberbands or sees disconnect notices | That player’s network path, local workload or client files | Wired test, stop background traffic, verify files, update drivers and OS, then test JobThreads 1 |
| Everyone freezes or rubberbands at the same moment in a local world | Host save I/O, especially compressed autosaves | Back up the host settings, test CompressSaveFiles: false, and restart |
| All players lag on a dedicated server | Server CPU/FPS, ports, firewall, forwarding or server software | Check server performance and logs, confirm UDP ports, update and restart |
| Server is absent from the browser | Query-port or list-registration problem | Allow both configured ports, check ListOnSteam/ListOnEOS, wait after launch, try the external IP |
| “Unknown Status” | Malformed host JSON or an owner who is not currently hosting | Repair the two JSON files if it is your server; ask the owner whether it is running |
| “Error: Server Error” while loading | Corrupted newest autosave | Roll back to the previous save, accepting possible progress loss |
Steam describes online lag as high network latency. Stunlock’s guidance also distinguishes that from save-compression stalls and background-thread work on a local host, so do not treat every rubberband as an Internet problem.
How do I establish whether my network link is the problem?
Run these reversible checks before editing server files. They are designed to expose packet loss, latency spikes and local congestion without changing your world.
- Use wired Ethernet for a test session. Connect the host or affected player directly to the router. A Cat6 Ethernet cable can remove Wi-Fi interference and signal variation; it cannot repair a corrupted save or an overloaded dedicated server. A USB-to-Ethernet adapter is an option for a computer without a reliable Ethernet port.
- Stop competing traffic. Pause game downloads, cloud synchronization, video streams, torrents and other network-intensive applications on the household network. Check upload activity as well as downloads, because saturated upstream capacity can produce severe latency.
- Restart the network path. Power-cycle the router, wait for it to reconnect, then restart the PC. This clears a stale local session and forces a fresh connection without changing V Rising data.
- Verify the game installation. In Steam, open the game’s Properties, choose Installed Files, and select Verify integrity of game files. Let the process finish before launching again.
- Update the software stack. Install the current V Rising update, graphics-driver update and operating-system updates. Reboot after driver or operating-system installation so the new components are actually loaded.
- Compare players. If only one person still stutters while others remain smooth, keep troubleshooting that player’s connection or client. If everybody stutters at the same instant, move to the host or server branches.
Steam also recommends checking server latency, background applications, router conditions and required port forwarding. Port forwarding matters for a remotely reachable host; it will not improve a purely local Wi-Fi link.
How do I test the JobThreads workaround?
JobThreads is a client-side diagnostic workaround. Stunlock reports that some systems become more stable with one job thread, but it is not a universal performance setting.
- Open Options > General > Interface.
- Enable Console Enabled.
- Return to the game and open the console with the key immediately below Esc (the physical key differs by keyboard layout).
- Enter
JobThreads 1and press Enter. - Reconnect to the affected server and reproduce the problem. Test long enough to include the activity that normally causes the stutter.
- If it does not help, or you want to restore the default used in Stunlock’s workaround, enter
JobThreads 4.
Each client can change this value independently; the host does not need to impose it on every player. Record which value was active when you test so support can reproduce the result.
How do I stop rubberbanding caused by a local autosave?
If every player freezes together during a save in a world hosted from a player’s PC, test save compression. Stunlock says disabling compression can speed save operations and reduce save-related lag spikes, at the cost of more disk space. This setting affects local hosting only; it does not change a dedicated server run by someone else.
- From the main menu, choose Load Game.
- Select the local server and choose Go to Directory.
- Make a backup copy of
ServerHostSettings.jsonbefore editing anything. - Open the original in a plain-text editor. Find
"CompressSaveFiles": trueand change it to"CompressSaveFiles": false. If the value is already false, do not add a second entry. - Save the file as valid JSON, preserving quotation marks, commas and braces. Do not let the editor append a second extension such as
.json.txt. - Restart the local server and test the same save-triggering activity.
Stunlock’s official bug-board discussion also records a temporary combination of "AutoSaveInterval": 120 and "CompressSaveFiles": false. Treat that interval as a user-reported workaround rather than a guaranteed fix: changing it delays automatic saves, so keep a backup and understand that a crash could leave more progress unsaved. Never increase the interval as a substitute for diagnosing a failing disk or corrupted world.
What should I check on a dedicated V Rising server?
For a dedicated server, separate game traffic from Steam-list traffic and verify the whole path from the server machine to the Internet. Stunlock’s current instructions apply to the 1.1.x PC dedicated-server application, which is available in Steam’s Tools section.
Confirm the configured UDP ports
The Port setting carries game traffic. QueryPort carries Steam-list query traffic. Use the actual values in your server configuration rather than assuming a default, then allow both UDP ports through the host computer’s firewall and forward both ports on the router when players connect from outside your home network.
- Check that the firewall rule targets the dedicated-server executable and the correct network profile.
- Check that router forwarding points to the server PC’s current local IP address. A changed DHCP address can silently invalidate an otherwise correct rule.
- Make sure another application is not already occupying either port.
- After changing a rule, fully stop and restart the server before testing.
Check list registration
ListOnSteam and ListOnEOS determine whether the server registers with the corresponding browser. A server can be reachable by direct IP while missing from a list if query traffic is blocked or the relevant registration option is disabled.
Allow time for registration and try direct IP
Stunlock says a fresh dedicated server can take several minutes to appear. Wait after launch, then search again. If it still does not appear, give players the server’s external IP and configured game port for a direct connection. Direct-IP success points toward list registration or query-port handling rather than basic reachability.
Maintain the host
Keep a copy of the supplied start script because updates can overwrite it. Schedule regular restarts; Stunlock’s current instructions recommend daily restarts for consistency and updates. Before each update, stop the process cleanly, apply the update, verify the configuration and launch again.
Why is V Rising showing “Unknown Status”?
On a server you own, “Unknown Status” usually indicates malformed ServerHostSettings.JSON and/or ServerGameSettings.JSON, often after a manual edit. On someone else’s server, Stunlock says the most likely explanation is that the owner is not currently hosting it.
If you own the server
- Stop the server completely.
- Restore the most recent known-good copies of both JSON files, or undo the last manual change.
- Check JSON syntax carefully: matching braces, quoted property names, commas between entries and no trailing comma before a closing brace.
- Start the server and test again. If the status returns, reapply changes one at a time, restarting after each change.
Do not paste configuration fragments from a different game version without checking the current file structure. Keep an untouched backup so you can recover from a bad edit.
If someone else owns it
Ask the owner whether the server is running and whether it was recently updated or reconfigured. You cannot repair another owner’s host JSON from the client side.
How do I recover from “Error: Server Error” when loading?
Stunlock says the newest autosave is often corrupted when loading ends with Error: Server Error. Rolling back to the previous save can recover the world, but any progress made after that save may be lost.
- Exit the game and stop the host so it cannot overwrite files during recovery.
- Back up the entire save directory before deleting or moving anything.
- Identify the newest autosave and the immediately preceding save by timestamp.
- Move the newest autosave out of the active save folder rather than permanently deleting it.
- Load the previous save. If it opens, play briefly and create a fresh manual backup before making further configuration changes.
If the previous save also fails, stop experimenting with random files; preserve the directory and logs for support. A rollback is a recovery measure, not proof that the network caused the original failure.
How can I tell whether the problem is network latency, save I/O or server load?
Use timing and scope rather than guesswork. The same visual symptom—characters snapping backward—can come from different layers.
| Observation | Interpretation | Next action |
|---|---|---|
| Rubberbanding aligns with local autosave activity and affects everyone | Save-compression or host disk work | Back up settings and test compression disabled |
| Only one player is affected, including outside save moments | Client link, Wi-Fi, background traffic or local workload | Wired test, traffic cleanup, file verification, updates and JobThreads 1 |
| All players lag continuously on a dedicated server | Server CPU/FPS, network path, firewall or port configuration | Inspect server performance and logs; verify both UDP ports and restart |
| Players can connect by external IP but cannot find the server in the browser | Query-port or list-registration issue | Check QueryPort, firewall forwarding and list flags |
| No one can connect after a host restart | Server process, address, firewall or forwarding failure | Confirm the process is running, the external IP is current and both ports target the right machine |
Do not use a list-visibility failure as evidence that the server is offline. Browser registration and direct reachability use related but distinct traffic paths.
What should I send to Stunlock support?
If the checks and workarounds do not resolve the issue, preserve evidence before changing more files. Note the date and time, whether the session was local or dedicated, which players were affected, the exact symptom, the last setting changed and the steps that reproduce it.
Stunlock’s official bug-board response requests Player-server.log and Player.log. Attach the relevant copies for the affected session and describe whether JobThreads was changed on the client. Include the server version, operating system, network type (wired or Wi-Fi), and whether the issue coincides with autosaves. Logs are most useful when they come from the session that actually reproduced the failure.
Which fixes apply to local hosting versus dedicated hosting?
Choosing the correct hosting model prevents wasted changes. Local worlds expose host-save settings that a remote dedicated server does not, while dedicated servers expose port, query and restart controls that a client host may not.
| Control or symptom | Local/client-hosted world | Dedicated server |
|---|---|---|
CompressSaveFiles |
Relevant; disabling it can reduce save-time spikes and uses more disk space | Not a client-side fix for a server hosted by someone else |
JobThreads |
Can be tested by each player, including the host | Can still be tested by each client; it is not a substitute for server maintenance |
| Firewall and router forwarding | Needed when remote players must reach the host through the Internet | Core requirement for remote access; verify game and query UDP ports |
| Server-list flags | Depends on the host’s published configuration | Check ListOnSteam and ListOnEOS directly |
| Autosave rollback | Use the local save directory and backups | Use the dedicated server’s save directory and its backup policy |
No official source establishes a failure percentage for Wi-Fi, JobThreads, save compression or port configuration. Treat each as a diagnostic branch, not a guaranteed cause.
Frequently Asked Questions
Can I fix V Rising lag without changing server files?
Yes. Start with a wired test, stop background traffic, restart the router and PC, verify Steam files, and install current game, driver and operating-system updates. These steps are reversible and help separate a client or network fault from a host-save problem.
Will disabling save compression damage my V Rising world?
The setting changes how local saves are written and increases disk use; it is not a world reset. Make a copy of the host-settings file and the save directory first, and restore the original value if the test provides no benefit.
Why can friends join by IP but not see my server in the list?
Direct IP uses game reachability, while browser discovery also depends on query traffic and list-registration flags. Check the configured QueryPort, allow it through the firewall and router, verify ListOnSteam/ListOnEOS, then allow several minutes after launch.
What information helps support diagnose intermittent rubberbanding?
Provide the session time, reproduction steps, hosting type, affected-player count, connection type and any settings changed. Include the matching Player-server.log and Player.log files from the reproduced session.