Live data from Hacker News

A decade-old Steam bug

blog.freudenjmp.com

11–20 of 55 posts

Re: A decade-old Steam bug

#11

I feel that drawing weapons has gotten slower in CS2. I wish they dropped the 'pull back on the charging handle' every time you draw the gun. (and I miss my custom sprays from CS: Source). But apart from that, even though I've played CS since 1.4 I have never ever had the bug mentioned above.

If I understand the blog post correctly, this bug only happens when you play CS2 during Washington nighttime.

Re: A decade-old Steam bug

#13
post #6

[flagged]

It's not decades old. They just revamped it a couple of years ago. That makes it merely a years-long bug

Impressively there's no ancient interface panel with butt ugly OG Olive Drab hiding deep in there somewhere.

squints at a windows XP dialog in Windows 11

Re: A decade-old Steam bug

#14
> 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

#15
post #14

> 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.

>a kilometer long article

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

Re: A decade-old Steam bug

#16
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

#19
I believe the flow in the diagram is what Steam calls Session Tickets and is a bit more nuanced. The game client requests session tickets from Steam's server, then it provides the game server with a ticket proving they are a given Steam ID. The game server then has to go online to Steam's web API and verify it to ensure it has not been used multiple times or tampered with. It sounds like the CS2 client is not handling a delayed response for obtaining a session ticket.

The flow is detailed here[0]. The flow the article diagram suggests would be a bit concerning since an attacker could race a victim Steam ID to join a server, etc.

[0] https://partner.steamgames.com/doc/features/auth#3

Re: A decade-old Steam bug

#20
It sounds like the solution is to keep the game open for awhile before going into multiplayer? You say "until you see the game console or wait 5-10 seconds after you saw the intro video." How long is that specifically?

I don't play CS:GO but I've seen the "No user logon" error when playing other games online, specifically Portal 2 and It Takes Two.

> I'd love to get feedback

Please put the solution in the tl;dr. The write-up is interesting for some folk, including many on HN (and myself) but the average person looking up this error could not care less about the intricacies of the code or network calls that cause the error, they just want to fix it.

(added in edit) The "You can skip to No user logon if you don’t care about the history." link that doesn't jump to the answer would be extra frustrating for someone who is just looking for the solution. From a pc there is a table of contents and the fact that there is a "Solution" section is great, but a phone user does not see that.

Post reply on HN