Skip to content

Regression: Co-op randomly kicks to menu with "no steam logon" error #471

@vrad-exe

Description

@vrad-exe

Since around November 2023, co-op players will frequently be kicked with the error "No Steam logon" (which will consequently cause their partner to also disconnect and the game to end, losing any progress in the level). This most commonly occurs in splitscreen mode, but can apparently happen in online co-op as well, as supported by results from both me and others in the replies. In both cases, this is despite being fully signed into steam, connected to the internet, and signed into friends and chat (although for splitscreen/local servers this should not happen in offline mode either as that worked fine before).

To reproduce the issue, simply start a local splitscreen game by using either the button that appears in the co-op dialog when a controller is connected or the ss_map command, then wait. The time it takes before disconnecting varies, but will usually happen after a few minutes. I personally feel like it happens more quickly when another map was previously loaded during the same session, but that might just be my imagination.

Interestingly, this doesn't seem to be tied to any specific game build. The earliest mentions of this issue that I could find date to around November 2023, but the last Portal 2 update at that point was over six months earlier in April. Furthermore, this issue occurs in the demo_viewer build that is available through the Steam betas tab, which is even older, dating to around 2020 - it would be strange for it to take over 3 years for anyone to notice, and personally I can confidently say that I never had this issue occur until around the same time others started reporting it (I frequently play splitscreen).

This seems to point to the issue being caused by a change in Steam, rather than the game itself, though as far as I can tell only Portal 2 seems to have been affected by this - I did find some L4D2 players complaining about a similar problem, but it seems to date much farther back, so I'm not sure if it's related. As usual, I don't expect anyone who actually works on the game to look at this issue tracker anytime soon, but I figured it's a good idea to formally report it. I will likely also try contacting steam support about this at some point, especially since the problem doesn't even seem to be caused by Portal 2 itself.

Enabling sv_lan 1 before starting a splitscreen co-op game seems to stop this from happening (or I've just gotten really lucky)...although this can crash the game.

I can confirm that this happens on Windows (10) and Linux (Steam Deck, native build).

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions