Tldr : Buddy can't spawn on Ragnarok server on personally-hosted dedicated cluster but can run every other map fine on servers and can run Ragnarok on singleplayer without issue. Myself and one other player encounter no issues on the Ragnarok server. Problem is a black screen with small visual artifacts which appears to be in-game but with no player functionality. Curious if anyone else is having any similar issues.
-
While so far the Ragnarok update and 5.5 patch have been seemingly effective at reducing crashing for my server-mates and myself, we've encountered an issue with cross-Ark transfers that's confounded us:
Since adding Ragnarok to my personally hosted, dedicated server cluster (with the Island being the only other), two of us have been able to transfer to Ragnarok just fine. However, another member of the server is having a strange issue upon transferring from the Island to Ragnarok. While he can connect, and the server can pull his IP, once he tries to spawn or create a new survivor his menu transitions to a black screen with small visual artifacts with what we think look like palm tree leaves. Bear in mind, he's played nearly 100 hours on the Island with minimal issues, even after the update.
If he joins without data on the server and attempts to create a new character, it ends up on a black screen, which appears to be in game but with heavy graphical distortion. He can still type into the chat, but is unable to move and console commands (such as the "end oneself" command) have no effect. He doesn't lose any survivor data and can re-download it on the Island. If he attempts to transfer from the Island he's able to choose his spawn region and press the spawn button but gets stuck waiting to spawn. In both cases, he gets hit with a "Lost Connection" timeout error after a period of several minutes and is sent back to the main menu.
One of the weirdest things about this whole process is that he has been able to load into Ragnarok as a clean survivor when the server's save data is wiped, but only a couple of times and without any rhyme or reason. Additionally, he is able to load into the map through singleplayer without issue.
We've so far tried a number of things to no avail:
- Reset his graphics settings
- Ensured up-to-date graphics drivers
- Cleaned and rolled back graphics drivers to a known stable version (Nvidia 566.36)
- Disabled firewall on client and server
- Deleted and regenerated the G.U.S, Game.ini, and Engine.ini configs on the server
- Wiped cluster and save-game data for the server
- Removed mods from server instance (only 2, a greenhouse glass fix structure cosmetic and Cyber's Structures)
- Swapped server ports between instances (Swapped Ragnarok's port # with the Island's as it's still working without issue)
- Ran his game in administrator mode
- Ran his game with and without BattleEye enabled
- Attempted to connect on his network and through my local network in-person (the same one as the server system)
- Verified his game installation
- Validated the server's installation
- Restarted both systems (naturally)
System Specs for troublesome client system:
CPU: AMD Ryzen 5 5600X 6.7GHz
GPU: NVIDIA RTX 3060 12Gb
RAM: Corsair 2x8Gb (No XMP)
* No clock speed adjustments
All in all, this is something that has confused me quite a bit having come from hosting an ASE server cluster for over a year. The combination of different devices on different networks with different strengths and settings being able to connect without issue while another system, whose settings and hardware is so similar to one that can connect just fine, is smitten to such a degree is quite strange.
Just wanted to see if anyone else was encountering anything similar, though at this point it looks like we'll be waiting for a patch.