News for hackers. Stuff that matters.
Re:A decade-old Steam bug by freudenjmp on Friday January 12, 2024 @10:37PM (#38977129)
Hello HN,

this is my first detailed blog post about one of the most annoying bugs I have ever come across in my life.

Hope you like it and I'd love to get feedback :)

Re:A decade-old Steam bug by asynchronous on Friday January 12, 2024 @11:43PM (#38977396)
Great write up, amazingly thorough and interesting to read. We will watch your career with great interest
Re:A decade-old Steam bug by freudenjmp on Monday January 15, 2024 @02:10PM (#39004779)
Thank you!
Re:A decade-old Steam bug by yreg on Saturday January 13, 2024 @01:28AM (#38977789)
> I'd love to get feedback

You start the article with a tl;dr for people who came from google searching for a solution for the issue. How considerate!

But then you proceed to tell them what not to do and hide the actionable advice in a single sentence within a kilometer long article :)

My suggestion would be to add the workaround to the tl;dr.

Re:A decade-old Steam bug by Dalewyn on Saturday January 13, 2024 @01:32AM (#38977801)
>a kilometer long article

About 25 Page Downs in computational units, or CTRL+F in freedom units.

Re:A decade-old Steam bug by idbehold on Saturday January 13, 2024 @07:20AM (#38979307)
Seriously, it's like a cruel joke. TL;DR - don't do this, instead read the entire article!
Re:A decade-old Steam bug by freudenjmp on Monday January 15, 2024 @02:05PM (#39004715)
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!
Re:A decade-old Steam bug by freudenjmp on Monday January 15, 2024 @02:04PM (#39004691)
Thank you, very true. I edited a better tl;dr.
Re:A decade-old Steam bug by rkunde on Saturday January 13, 2024 @01:36AM (#38977815)
Great write up, but it left me with a few questions:

* Is levelloadloop only executed when the game launches, not when joining a server and loading the map? * If the issues is that the loop is shut down before the steam auth process is started, why would the maintenance-related slowness matter?

Re:A decade-old Steam bug by freudenjmp on Monday January 15, 2024 @02:07PM (#39004746)
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.

Re:A decade-old Steam bug by wokwokwok on Saturday January 13, 2024 @02:21AM (#38977969)
Great write up!

My only comment here is that the trail in the article and the conclusion don't quite make sense (well, they do, but you've kind of glossed over it slightly):

> The way Counter-Strike is started: the blame factor is 90%

But also:

> We could confirm that players world wide are facing the issue outside of Esportal and thought it indeed is caused by some maintenance in the middle of the night in Washington.

Those can't both be true.

If the blame is 90% about the way counter strike is started, then the issue wouldn't be distributed over the maint window.

Rather, it seems like this is the key part that should be highlighted in the summary:

> So the last thing that happens before the game loop is started is that the Steam ID validation is initiated.

> When the initialization of levelload is incomplete (speak: CS2 has not been fully loaded/initialized), the Steam3 validation is never initiated because it is the last thing that loop wants to do.

Which is to say, that when the `steam3` server is as slow as balls during a maint window, it makes this take longer, which means you're more likely to interrupt the loop by starting a game.

So when you say:

> The way Counter-Strike is started: the blame factor is 90%

It's true.... but maybe it's also true to say:

> State of the moon: blame factor is 3% <--- isn't quite right, since this is basically the maint window?

Maybe the advice should also be: 'and give is an extra couple of minutes during 13-17 PM CET, because Value does maint in that window'

...if I understood that correctly. :)

Either way, this has happened to me, but this 'just wait a while and let it finish loading' solution is by far the most useful sensible advice about it I've ever heard. Fantastic stuff.

Re:A decade-old Steam bug by freudenjmp on Monday January 15, 2024 @01:59PM (#39004637)
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! :-)

Re:A decade-old Steam bug by gortok on Saturday January 13, 2024 @08:40AM (#38979769)
In some paragraphs you put “a hat on a hat”. That is, you pile on the snark on top of an already meme-y paragraph and it feels like “too much” of something that works better subtly.

As others have stated, get to the point sooner.

Re:A decade-old Steam bug by freudenjmp on Monday January 15, 2024 @02:01PM (#39004665)
Thanks!