freudenjmp

Thanks, has been fixed by providing a real solution in the tl;dr.

Thanks, very valuable feedback.

I do not know the exact answer of how long it takes to get into the `game` loop and it is depending on your system also. To know for sure, you can type

  status

into the CS2 ingame console. If it shows this, you know you are ready to go:

  [EngineServiceManager] @ Current  :  game

I've put the solution to tl;dr now. Thanks!

Thank you!

Yes, correct for CS2 as of time of writing. Not true for CS:GO or CS:S where it could happen any time of the day.

Given that Valve doesn't reply to simple requests like this to ask if it is in-scope, I can't know that. Though I agree with your conclusion. Makes sense!

Thanks for your feedback!

1. Yes, only when the game launches. I think the naming of the loop is related to single player games like Portal, where this way of naming makes much more sense because you have frictionless changing of levels there.

2. You are right that is a hole in the explanation and I do not know the answer, but it is definitely a fix for the problem. Likely the details of my conclusion are incomplete but at this point I don't feel like digging deeper because it's not necessary at the moment.

I think this was the result of me putting so much effort into my first article and at the moment of release I didn't want to "throw it away" with a single sentence solution. In hindsight this way of thinking was wrong and that I could have done better and I agree it's like a bad joke. Fixed!

Thank you, very true. I edited a better tl;dr.

What surprise crashing are you referencing to? Crashes can be investigated in theory but Valve sends crash reports to their servers instead of storing them on disk. It's harder to analysis if you didn't catch a crash live with a debugger attached. And that is hard because of their Anti-Cheat (VAC) though not impossible (disable VAC).

Thanks!

Thank you, valuable advice.

Thank you for your comment. I agree there is some hole in the details of my explanation/conclusion attempt, but I am not sure if your attempt to explain it is correct either. I am not saying yours wrong or something, but players have had this issue in CS:GO unrelated to the maintenance window. In CS2 however we only observed it in the maintenance windows.

So maybe in the end the bugs in CS:GO and CS2 are of different nature, but I will not be able to ever proof this as CS:GO has been replaced by CS2.

Sad, but thanks! :-)

Thank you very much. Indeed this is the technically correct flow, which was not so important for the explanation of the issue. I understand I should have mentioned it though to make it more clear. Much appreciated!