General Disclaimer
Mods
Mods can be a great way to enhance your experience, but they are used at your own discretion. While many are safe and enjoyable, we cannot guarantee full compatibility with the game. We strongly recommend creating a backup of your Save folder before experimenting with mods. Please note that we are unable to investigate issues that occur when mods are installed.
Running the Game on Linux
At this time, a Linux client is not officially supported. Given the wide variety of Linux configurations, we are unfortunately unable to investigate or provide support for issues that occur on Linux systems.
Dedicated Server Providers
There are many server providers available, each using their own infrastructure and deployment methods. If you encounter issues while using one of these services, we recommend reaching out directly through the provider's support channels.
Additionally, some providers may suggest renting servers with 10 or more player slots. While this is technically possible, we generally recommend playing in groups of up to 4 players for the best experience. Larger groups may encounter performance limitations, and certain gameplay systems (such as boss encounters) are not currently balanced for higher player counts.
Thank you for your understanding and support.
Save Issues
As of the current game update (0.10.0.5.120-073042fb), we've rolled out a patch intended to fix most Steam Cloud Saves (aka "corrupted" saves) issues. However, the information below may still be useful if you want to take additional steps or encounter any difficulties.
Recovering Save Files in Game
If you launch the game and see a message indicating that your save data is corrupted, the game may still be able to restore it automatically.
First, press Confirm on the error message and check whether your Characters and Worlds are present. Please note that some progress may already be lost due to the corruption itself.
If your Characters or Worlds are still missing, follow the steps below.
This guide only works for saves created before May 4th (before the current update 0.10.0.5.120).
Before starting:
• Disable Steam Cloud saves
• Do not skip backup steps
• Read the instructions carefully before attempting recovery
STEP 1 — Disable Steam Cloud
- Open Steam
- Right-click on Windrose
- Select Properties
- Under the General tab: Disable Steam Cloud
STEP 2 — Open Your Save Folder
- Press
Win + R - Paste the following path:
%localappdata%\R5\Saved\ - Press Enter
You should now see the SaveProfiles folder.
STEP 3 — Create a Backup Copy
Before making any changes:
- Copy the entire
SaveProfilesfolder - Paste it somewhere safe
This ensures you can undo changes if something goes wrong.
ATTEMPT ONE — Retry Automatic Recovery
Sometimes the automatic recovery process works after removing temporary migration folders.
- Open:
%localappdata%\R5\Saved\SaveProfiles - Open your Steam ID folder (the folder with random numbers)
- Inside, you should see:
RocksDB,RocksDB_v2,RocksDB_v2_Backups
0.10.0.5.120, your latest migrated saves should be located inside RocksDB_v2_Backups.RocksDB and %YOUR_STEAM_ID%_Backups contain older pre-update save data and backups. These folders may still be useful if migration failed or if you experienced issues during the update process.- Delete:
RocksDB_v2andRocksDB_v2_Backups
Do NOT deleteRocksDB. - Launch the game again
- Press Confirm on the error message
- Check whether your Characters and Worlds are restored
If they are still missing, proceed to Attempt Two.
ATTEMPT TWO — Manual Backup Restoration
Step A — Ensure Steam Cloud Is Disabled
Double-check that Steam Cloud is still disabled for Windrose.
Step B — Open Your Save Folder
- Press
Win + R - Paste:
%localappdata%\R5\Saved\ - Open:
SaveProfiles→ your Steam ID folder - Inside, you should again see:
RocksDB,RocksDB_v2,RocksDB_v2_Backups
Step C — Remove Migration Folders
Delete: RocksDB_v2 and RocksDB_v2_Backups. Only RocksDB should remain.
Step D — Clear Current RocksDB Data
Open the RocksDB folder and delete everything inside it. Do NOT delete the RocksDB folder itself.
Step E — Open Backup Saves
- Open another Explorer window
- Press
Win + R - Paste:
%localappdata%\R5\Saved\SaveProfiles - You should now see:
• Your Steam ID folder
• Another folder with_Backupsat the end (e.g.,765611XXXXXXXXXX_Backups) - Open the
_Backupsfolder - Inside, you will see backup folders organized by date
Step F — Restore a Backup
- Select one of the backup dates (recommended: start with a slightly older backup, not the newest one)
- Open the backup folder. Inside you should see:
• A folder named something like0.10.0
•AccountDescription.json - Copy BOTH: the version folder and
AccountDescription.json - Paste them into:
%localappdata%\R5\Saved\SaveProfiles\YOUR_STEAM_ID\RocksDB
Step G — Launch the Game
Start Windrose and check whether your Characters and Worlds are restored.
If the backup does not work: repeat the process with an older backup date.
Every time you launch the game, Windrose automatically recreates
RocksDB_v2 and RocksDB_v2_Backups.Because of this, before testing another backup, you MUST repeat:
• Step C (delete the recreated folders)
• Step D (clear RocksDB again)
Otherwise the newly copied backup files will not apply correctly.
After Successful Restoration
Once you confirm that your saves are working again:
- Re-enable Steam Cloud
Open Steam → Right-click Windrose → Properties → Enable Steam Cloud
When Steam detects a save conflict: choose LOCAL FILES.
Do NOT choose the Cloud version, otherwise the corrupted save may overwrite your restored backup.
Recovering Save Files on Dedicated Servers
Dedicated server save files follow the same recovery logic as local game saves. The main difference is that dedicated server saves are stored inside the server directory rather than inside AppData.
You can follow the same recovery steps described in Recovering Save Files in Game.
If your dedicated server keeps generating a completely new world instead of loading the intended backup, this usually means the server cannot locate the correct World ID.
Case 1 — No Backups Exist After Updating the Dedicated Server
If, after updating the server, you do not see any backups inside \R5\Saved\SaveProfiles\Default\RocksDB_v2_Backups, then the issue is most likely related to an incorrect WorldIslandID.
Fixing WorldIslandID
- Stop the Server
Close both the game and the dedicated server. - Locate Existing World Saves
Navigate to:\R5\Saved\SaveProfiles\Default\
InsideRocksDBor the backup folders, locate the intended world save. Copy the World ID. - Update ServerDescription.json
OpenServerDescription.json, find"WorldIslandID", replace its value with the correct World ID. Save the file. - Restart the Server
Launch the dedicated server again and verify whether the intended world loads correctly.
Case 2 — WorldIslandID Is Correct, But New Worlds Are Still Generated
If WorldIslandID is already correct, then some save data may be corrupted. The server detects the save, attempts recovery, fails, and generates a new world instead.
Try the recovery steps from Recovering Save Files in Game.
Alternative — Testing Dedicated Server Saves Locally
If your dedicated server keeps generating new worlds or fails to load existing saves, you can try opening the server saves locally through the game client to determine whether the save files themselves are functional or corrupted.
Update Windrose to the latest version → Launch the game once → Reach the main menu → Close the game.
This is required because the updated game version creates the necessary local save structure and migration folders.
Keep in mind that save files might be stored in different folders:
RocksDB— old main saves before update0.10.0.5.120%YOUR_STEAM_ID%_Backups— old backups before update0.10.0.5.120RocksDB_v2— new runtime folder used while the game is running to store required runtime files after update0.10.0.5.120. DO NOT TOUCH IT.RocksDB_v2_Backups— new backups after update0.10.0.5.120
Your goal is to locate the correct saves or backups (usually inside RocksDB or RocksDB_v2_Backups with the _Latest suffix) and transfer them locally for testing.
Steps
- Find all folders inside:
\R5\Saved\SaveProfiles\Default\ - Back them up somewhere safe
- Open:
%localappdata%\R5\Saved\SaveProfiles - Copy the dedicated server saves and replace the local save files with them
- Start Windrose normally through Steam
- Check whether the world appears correctly, characters load properly, and the save is accessible
If the world opens correctly locally, the save files are functional. You can then transfer the recovered save back to the dedicated server.
Restoring Recovered Saves Back to the Dedicated Server
- Locate the recovered save data inside:
RocksDB,RocksDB_v2,RocksDB_v2_Backups - Navigate to: Worlds → World_ID → Latest
- Copy the recovered files back to the dedicated server save location
- Restart the dedicated server
How to Sync Your Local Saves with Steam Cloud (Local → Steam Cloud)
This will upload your latest local saves to the Steam Cloud. Don't forget to close the game beforehand.
- Press
Win + R - Enter:
steam://open/console - Press Enter
- In the Steam console, enter:
set_spew_level 4 4 - Then enter:
Check the logs to confirm that RocksDB V2 backup files are synchronized.cloud_sync_up 3041230
Folder path:C:\Users\%username%\AppData\Local\R5\Saved\SaveProfiles\%your_Steam_ID%\RocksDB_v2_Backups - Finally, enter:
set_spew_level 0 0
How to Sync Your Steam Cloud with Local Saves (Steam Cloud → Local)
This will download your latest Steam Cloud saves to your local machine. Don't forget to close the game beforehand.
- Press
Win + R - Enter:
steam://open/console - Press Enter
- In the Steam console, enter:
set_spew_level 4 4 - Then enter:
Check the logs to confirm that RocksDB V2 backup files are synchronized.cloud_sync_down 3041230
Folder path:C:\Users\%username%\AppData\Local\R5\Saved\SaveProfiles\%your_Steam_ID%\RocksDB_v2_Backups - Finally, enter:
set_spew_level 0 0
Connectivity Issues
Common symptoms:
- I cannot join a server
- I cannot create a host game
- When I enter a server invite code, I cannot find the server
- When I try to join a game or create a host, all my connectivity services are shown as "Not Available"
- I (or my friends) get stuck on the loading screen when trying to join a server
- I or my friend cannot connect to our server
Try Force Relay Connection or Connect Through Direct IP
First, try connecting using the Connection Service. Simply enter the world code and click Connect. Keep in mind that all players must have the same Connection Service region selected (EU & NA, SEA, or CIS) in order to play together.
If that does not help, try enabling Force Relay Connection. This option does not work with Direct IP connections.
Sometimes direct P2P connections between players fail because the traffic is blocked somewhere along the route. This may happen due to:
- Router settings
- ISP restrictions
- Firewall rules
- Other network limitations
Enabling Force Relay Connection forces the game to use our relay servers instead of a direct P2P connection. This can improve connection stability, but may increase latency (ping).
If this still does not help, you can try connecting through Direct IP instead. This requires additional setup steps listed below.
Players on Different Networks (Different Routers / Different Homes)
Example: each player is connecting from their own home internet connection.
In this scenario, the person hosting the server must have a public external IP address assigned to their router. Some internet providers offer this as a paid service.
The host must configure port forwarding on their router using the following logic:
external_ip:external_port (TCP + UDP) → internal_ip:gameserver_port (TCP + UDP)
Both TCP and UDP forwarding are required.
Definitions:
| Term | Description |
|---|---|
external_ip | Public IP address assigned to the router by the ISP |
external_port | Port configured in router port forwarding settings |
internal_ip | Local IP address of the computer running the dedicated server |
gameserver_port | Port selected in the server UI when launching the server |
How it works
Connections made to the router's public IP and forwarded port are redirected to the local machine running the server.
Example:
203.0.113.25:17777 → 192.168.1.100:7777
The host then shares their:
- Public IP address
- Forwarded port
The second player connects using that IP and port in the game client.
Players on the Same Local Network (LAN)
Example: two players in the same house using the same router.
In this case:
- No public IP is required
- No port forwarding is required
The host simply launches the server and selects a port in the server UI. The host then shares:
- The local IP address of the server machine
- The selected server port
The second player connects using the local IP and port. Example:
192.168.1.100:7777
Troubleshooting Direct IP Connections
If connection problems occur, try the following:
- Verify the server IP address using:
Run this on the machine hosting the server.ipconfig - Try changing the port from
7777to a higher alternative such as:17777,27890, or any unused port below 65000 - Temporarily disable Windows Firewall
- Ensure the game client has permission to access the network
- Temporarily disable antivirus software
- Confirm that both TCP and UDP traffic are allowed for the selected port
- Make sure the server is fully started before attempting to connect
Something may have gone wrong with your network setup
It is quite common for issues to occur simply because your machine or router has been running for a long time without a reboot. Restarting everything can sometimes resolve these problems. Before trying more advanced solutions, we recommend starting with the basics:
- Reboot your PC
- Fully close Steam and log in again
- Reboot your router
- Verify the game's file integrity
- Disable your VPN
- Try reconnecting to the game server a couple of times
- Temporarily disable your antivirus or firewall (for Windows Firewall, see firewall settings below)
Blocked by your ISP
We are seeing cases where certain ISPs block access to our backend services that are required for players to connect. We are currently investigating why this happens and are reaching out to affected providers to resolve the issue.
Some ISPs have already responded and lifted the restrictions, allowing players to connect normally. However, this process may take time.
In the meantime, you can try the following:
- If your ISP provides an app or web portal with additional security settings, try disabling them temporarily
- If your ISP offers a list of blocked domains, check for entries containing windrose.support. This is one of our services. If found, please allow it
- Try switching connection regions in-game (for example, if you are in NA, try selecting Asia or CIS)
- While we cannot officially recommend third-party software, some players have reported that tools such as https://one.one.one.one/ or similar services may help bypass the block until it is resolved by the ISP
Your network settings prioritize IPv6 over IPv4
The game is currently designed to use IPv4. If your system prioritizes IPv6, this may lead to connectivity issues. Disabling IPv6 or adjusting your network settings to prioritize IPv4 may resolve the problem.
How to check protocol priority (Windows 10 & 11)
Windows uses a priority table to decide whether to use IPv4 or IPv6.
Open Command Prompt and run:
netsh interface ipv6 show prefixpolicies
You will see a table with Prefix, Priority, and Label.
| Prefix | Meaning |
|---|---|
::ffff:0:0/96 | IPv4 |
::/0 | IPv6 |
Higher Priority value = higher preference.
By default, IPv6 usually has higher priority. For Windrose, IPv4 should be higher.
How to prioritize IPv4 (recommended fix)
This keeps IPv6 enabled but forces Windows to prefer IPv4.
- Open Command Prompt as administrator
(Start → typecmd→ right-click → Run as administrator) - Run the command:
Some players on Windows 10 reported using these commands instead:reg add "HKLM\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters" /v DisabledComponents /t REG_DWORD /d 32 /fnetsh interface ipv6 set prefix ::/96 60 3 netsh interface ipv6 set prefix ::ffff:0:0/96 55 4 - Restart your PC
Verify the result
After restarting, open Command Prompt and run:
ping google.com
If successful, you'll see an IPv4 address (e.g., 142.250.x.x).
If not, you'll still see an IPv6 address (e.g., 2a00:1450...).
How to revert to default settings
To restore default settings:
reg add "HKLM\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters" /v DisabledComponents /t REG_DWORD /d 0 /f
Restart your PC after applying the change.
You are playing from the same network
We are currently aware of an issue where PCs on the same network may be unable to connect to each other using an invite code. We are working on a solution to restore normal connectivity for this setup.
In the meantime, we have introduced support for direct IP connections. Connecting via direct IP should allow you to play on the same network without issues.
Please note: If you want other players to connect to you via direct IP, you may need to configure your router.
Your PC name contains non-English characters
In some cases, having non-English characters in your PC name can cause issues.
It may sound unusual, but if nothing else works, please check that your PC name uses only English letters.
Your antivirus or firewall might be blocking the connection
Method 1: Via Windows Security (recommended)
- Press the Windows key, type Windows Security, and press Enter
- Click Firewall & network protection
- Click Allow an app through firewall
- Click Change settings (administrator permission may be required)
- Find Steam and your game (.exe file) in the list. Enable both Private and Public checkboxes
If the app is not listed
- Click Allow another app
- Click Browse
- Navigate to the game's installation folder and select the
.exefile - Click Add, then enable both Private and Public checkboxes
- Click OK to save
Method 2: Via Control Panel (alternative)
- Press
Win + R, typefirewall.cpl, and press Enter - Click Allow an app or feature through Windows Defender Firewall on the left
- Click Change settings
- Find or add the app, then enable both Private and Public checkboxes
- Click OK
I played before with my friends, and now it's not letting us in
- Something may have changed with your connection (see Connectivity Issues)
- Your save may have become corrupted (see Corrupted Saves)
Game Crashes
Something may have gone wrong with your graphics card / CPU / RAM setup
It is quite common for issues to occur simply because your system has been running for a long time without a reboot. Restarting your PC can sometimes resolve unexpected problems. Before trying more advanced solutions, we recommend starting with the basics:
- Reboot your PC
- Fully close Steam and log in again
- Update your drivers
- Update Windows
- Verify the game's file integrity
AMD video card issues
AMD Radeon GPUs are currently known to experience stability issues with the latest AMD Adrenalin driver (26.3.1), which may result in increased Unreal Engine 5 crashes.
Some players have reported improved stability when using an earlier stable version, such as AMD Adrenalin 26.1.1 WHQL.
We are also investigating whether there are improvements we can make on our side to ensure better performance and stability on AMD hardware.
RAM issues
- Try closing other applications while playing the game
- If you have less than 16 GB of RAM, it is very unlikely that the game will run properly, as this is below the minimum system requirements
- You can still try disabling GPU acceleration in Steam:
- Open Steam Settings
- Go to Interface
- Turn off "Enable GPU accelerated rendering in web views" (requires restart)
- You can still try disabling GPU acceleration in Steam:
- If you have 16 GB of RAM, you should be able to play, but some players may still encounter issues
- Increase virtual memory (page file) to approximately 2x your RAM (see below)
How to increase virtual memory (page file)
Step 1: Open virtual memory settings
Method 1 (fastest)
- Press
Win + R, typesysdm.cpl, and press Enter - Go to the Advanced tab
- Under Performance, click Settings
- Go to the Advanced tab
- Under Virtual memory, click Change
Method 2 (via search)
- Press
Win + S - Type Adjust the appearance and performance of Windows
- Open it → Advanced tab → click Change
Step 2: Configure page file size
- Uncheck Automatically manage paging file size for all drives
- Select the drive (SSD recommended)
- Select Custom size and enter the recommended values:
| Your RAM | Initial Size (MB) | Maximum Size (MB) |
|---|---|---|
| 4 GB | 6,144 (1.5x) | 12,288 (3x) |
| 8 GB | 12,288 (1.5x) | 24,576 (3x) |
| 16 GB | 24,576 (1.5x) | 49,152 (3x) |
Click Set → OK.
Step 3: Restart your PC
Restart your computer to apply the changes.
Additional tips
Low on disk space?
You can move the page file to another drive:
- Select drive C: → choose No paging file → click Set
- Select another drive → choose Custom size → enter values → click Set
If you have 16 GB RAM or more, you can reduce the page file size (e.g., 1024-4096 MB), but keeping it enabled is still recommended for stability.
Command line alternative (advanced)
Check current page file settings
Run PowerShell as administrator:
Get-CimInstance Win32_PageFileUsage
Set a custom page file size
Example: Set initial size = 8192 MB, maximum size = 16384 MB on drive C:
wmic pagefileset where name="C:\\pagefile.sys" set InitialSize=8192,MaximumSize=16384
Restart your PC to apply the changes.
"DirectX is not supported" message
If your system meets the minimum requirements, this message usually indicates that your drivers are out of date. Try updating your graphics card drivers and installing the latest Windows updates.
Other random crashes or performance issues
- Check if your GPU or CPU is overheating.
While the game is running, open Task Manager (Ctrl + Alt + Del) → go to the Performance tab and monitor temperatures. - If temperatures are too high, try reducing graphics settings and setting the FPS limit to 60
- If temperatures are normal, try the following:
- Limit the maximum FPS
- Disable Frame Generation
- Disable DLSS
- Set resolution scale to around 50%
- Check if the issue persists
- If you're using tools such as MSI Afterburner or ASUS GPU Tweak, try reducing any overclock or reverting to default GPU clock settings. Overclocking can sometimes cause instability during longer play sessions.
- If you are using an Intel 13th or 14th Gen desktop CPU, make sure your BIOS is up to date:
Intel Community: 13th/14th Gen Desktop Instability Root Cause - Make sure the game is using your dedicated GPU and not the integrated one. To disable the integrated GPU:
- Press
Windows key + Xand select Device Manager - Expand Display adapters
- Locate your integrated GPU (e.g., Intel UHD Graphics)
- Right-click it and select Disable device
- Confirm the action
- Restart your PC and verify that the integrated GPU has not been re-enabled
- Press
Other Common Issues
I upload or download saves via FTP and they become corrupted
If you are using FileZilla, it may be the cause. Try using a different FTP client.
Many players have reported that Cyberduck (available in the Microsoft Store) works well for them.
← Back to playwindrose.com