CoZ

For anyone that is/was having issues copying the single player world over to the dedicated server, they've changed how it's done (again). The easiest way that I have found is to copy the entire \Username\appdata\local\R5\Saved\SaveProfiles\{Bunch of random numbers' folder\RocksDB and the RocksDB_V2 folders over to your \appdata\windrose saved world location. Then go into your windrose directory on your server, delete everything out of RocksDB and RocksDB_V2 folders that IS NOT "worlds" subdirectoy. There was an issue with the patch changing the RocksDB to RocksDB_V2 and the single player world not migrating correctly blah blah blah. I tried every which way to get it to "stick" otherwise it would just create a new world and overwrite any changes to the Serverdescription.json file that you put into it.

They aren't making it easy for us - they keep introducing breaking changes. Now for instance, since today's update, they've changed the location of the "world / save" folder. I've fixed the crashing on the container start. I've figured out the new format for copying over a single player to the dedicated server with no crashes. However, now I'm unable to connect anymore to the dedicated server as I could before with just the invite code. It's back to dropping me back into the main loading screen. Sigh. LoL

Got to post #2. You need to delete a file to "kick start" the update. It's been mentioned in this thread 30+ times now.

I sent in a bug report with what I posted earlier, the errors. I have been tinkering in the meantime. It seems that the P2pProxyAddress entry in the server.json MUST match the IP Unraid assigns it. For example, I earlier had that P2pProxyAddress set to my tower's IP address of 192.168.X.XXX and it was working fine before the updates were pushed out. I've changed it to the internal IP set by the container (172.17.0.28) and I am no longer getting the crash/restart cycle.

Yes. It's the same procedure I've used in the past to move over the world.

Just started the container after a few weeks because I'm about to travel for work and wanted to test it out. However, it's now in some sort of loop. Spits out these error messages and then re-starts... spits out the same error messages, re-starts... etc.. I've nuked the /appdata/Windrose folder. Pulled down the windrose folder again fresh. Starts fine. The error occurs when I copy over my world folder now from my localPC to the /appdata/Windrose folder and try to start the container. Maybe some permission error or something? LogOutputDevice: Error: === Crash Stack Trace: === LogOutputDevice: Error: LogOutputDevice: Error: [Callstack] 0x0000000141475686 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x000000014413ba9d WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x00000001414024b3 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x0000000141370d0a WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x0000000149139e6f WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x00000001490ff629 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x000000014451e1d9 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x0000000144500f21 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x0000000144500903 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x000000014c01d8e9 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x00006ffff91f1074 VCRUNTIME140_1.dll!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x00006ffff91f239c VCRUNTIME140_1.dll!call_catch_block4() [Z:\usr\src\packages\BUILD\dlls\msvcrt\handler4.c:440] LogOutputDevice: Error: [Callstack] 0x00006fffffc3f869 ntdll.dll!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x0000000144ee2abe WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x0000000146b76117 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x0000000146adbd13 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x0000000146b51a9e WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x0000000141427842 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x0000000146a6a404 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x0000000146a72458 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x000000014141ec48 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x000000014128a9d1 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x0000000141284e7f WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x00000001416e7ec5 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x00000001416ee665 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x00000001416e971e WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x00000001416c088f WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x00000001438550d0 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x0000000144101b61 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x000000014410512c WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x00000001441051aa WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x0000000144105c1d WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x000000014410b094 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x000000014bf6aace WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x00006fffffa64819 kernel32.dll!BaseThreadInitThunk() [Z:\usr\src\packages\BUILD\dlls\kernel32\thread.c:61] LogOutputDevice: Error: [Callstack] 0x00006fffffc3fa1b ntdll.dll!UnknownFunction []

I have done it successfully finally. You are copying the world file from your /Users/Username/appdata/local/R5....etc..etc.. to your /appdata/Windrose/R5...etc..etc.. worlds folder? Then right-click the worlds folder name, copy it. Open up serverdescription.json and paste it into the WorldIslandId entry and save it. All while the docker container is not running. I had forgotten to rename the WorldIslandId in the serverdescription.json file the first time and it just kept creating a "new" world over and over every time I deleted the old world file that it created.

I saw the same issue. Since I currently have no friends that have the game, I only start the container when I'm about to play. Otherwise, it stays off. Once I join, the "cores to 100" stops and everything levels out. It's damn strange.

Ok so deleting the container and the 'template container' won't delete the Windrose Appdata folder.

I just pulled down the update and none of the new parameters that you've listed show up when I edit the docker. What's the trick to getting them to show up or, should I just follow along your guide and manually create them?

Just tried that. It only copies the "map" over. No buildings, fast travel locations, etc..etc... Even the places I've visited are still "shrouded" by the fog of the map. So, unless something is very wrong with those instructions.... I'm not sure what it's supposed to "bring" over from your solo play to the dedicated one?

I haven't had an issue in bridge mode since I put my Unraid's internal IP in the server config. I can NOT vouch if it works for external access as I am still waiting on some friends to get the game. Would you not just need to point your SFTP program (FileZilla, etc) to the /appdata/Windrose/R5 directory? I would assume the mods go into there? Really? That is wild. I haven't left my running because I was watching 2 cores of my CPU spike to 100% when it was running with no one in it. (not due to Nodiaque container, it's just EA)

@Poundsy have you tried changing the "P2pProxyAddress": to the IP address of your Unraid? I am still running it in bridge mode, and I am able to connect to my server using after changing what the default entry was on that line.

@Nodiaque Greetings from Belgium. After waiting a few hours trying to download Windrose on the horrible Hotel WiFi speed and then Wireguarding into my Unraid server to start your container, I can now report that it works!!! I did not need to change it from bridge to host. It just works now. As others have stated, wow does this thing eat up some CPU and RAM even with no players on it. The DEVs need to do a lot of optimization and, quickly. Thanks again.

No I haven't tried to "self host" locally. I've got to head out to Belgium for a few days in a little bit so, I will keep an eye on this thread. When I come back, I will try the "self host" thing and report back if any issues. Sorry I can't do more at the moment. I have to pack and get ready to go. Where are you located in the World? I'm wondering if it is the whole "Russia" ISP blocking thing that someone mentioned earlier?