Unknown Steam error occurs when connecting to a server

[Andrew Theel]

An unknown Steam error is preventing you from connecting to this server. If the problem persists please contact Valve for support.

The bug to my knowledge isn't 100% replicable and occurs randomly when connected to a server that changed levels.

So I haven't a clue exactly what is causing this problem, but I have several ideas on where to begin to debug it.

MattUK reports using old system files for RO prevents this error, but he has no servers in his browser. Narrowing down the problem to an exact file could help in knowing what exactly is going on. This isn't so easy as it's not 100% replicable and will take a lot of time and trial and error.

My current debug idea is to setup a new console for DH 6.0 (currently DH uses ROConsole that extends ExtendedConsole). In ExtendedConsole, in function ConnectFailure on line 250 it has a hack that retries connection to the server 5 times and if fails outputs the error we see regarding this bug. So we should setup new console class that overrides this function and we can output some debug info to understand the issue. Do have DH use a different console we have to change it in the DarkestHour.ini and later default.ini.

Also there are some classes that reference the console class and those may need changed, but I doubt it.

[Andrew Theel]

I tried implementing a debug mode for this and ever since I can not get it to reoccur. It may not happen unless more than one person is connected to the server.

[Andrew Theel]

So apparently just defining a console class in the default.ini fixes this error/bug. We gotta decide weather to use an extended DH console (for currently no reason) or to use the RO one, but just define it in the default.ini

I'm going to have MattUK confirm this fix for his 5.1 servers.

[Andrew Theel]

in default.ini in DH/System add [Engine.Engine] Console=ROInterface.ROConsole

[Andrew Theel]

Upon further testing, we revealed that wasn't a sure fix. I'm still not sure exactly messing around with that was doing. With testing two clients with the same values, it'd still happen on one. Tested many different things, nothing making any sense. So I tried a new approach and to actually fix the problem with code. So far I'm pretty confident I fixed it, mainly because I saw the error in the server console, but because of the added retry I added the client reconnected seamlessly. Only way we should see that error again is if the retry fails 5 times.

[Andrew Theel]

I'll hold off on moving this to fixed until we get more testing involved.

[Andrew Theel]

I'm pretty sure this was solved, was fixed in.. 3cb3bbf

However players with 5.1 config/ini files will still have it!!! But that is a different issue.