#Steam connection error loop trial
After some educated trial and error, I found one parameter that either caused or prevented the error every time.
#Steam connection error loop how to
However, with subsequent experimentation on and comparison of logs from my dedicated servers experiencing the same issue with certain clients, I found out how to reliably reproduce the same error and symptoms locally, and that allowed me to narrow the problem down to a few likely root causes. That said, I’ve included a few tips at the end of this post that might help enough to get you connected, sometimes, until Funcom either does exactly that or else implements a tolerable long-term workaround (such as the one I’m now using on my servers, detailed below).Īfter a lot of snooping into official server logs (available for public capture with 0 effort when official servers shutdown or startup, which is probably an oversight) I was able to identify this error as a connection timeout - not helpful in its own right. There is a limit to what can be done without rewriting major parts of the engine. This engine is just not designed to handle games of Conan’s scale and complexity with assets of such significant quantity and fidelity - particularly not on a multiplayer scale. My fix is also just a workaround for an engine limitation a “proper” fix, realistically, isn’t practical within the limitations of the UE framework. This is 100% up to Funcom to implement on the official servers, and for private server admins to implement on their servers. Note to players: we have no ability to implement this fix from our clients. I have found a functional server-side workaround for the “Lost connection to server” loop that many, many, MANY players are experiencing when attempting to join official (and unofficial) servers.
0 kommentar(er)
