this post was submitted on 23 Sep 2023
31 points (100.0% liked)

Steam Deck

14803 readers
118 users here now

A place to discuss and support all things Steam Deck.

Replacement for r/steamdeck_linux.

As Lemmy doesn't have flairs yet, you can use these prefixes to indicate what type of post you have made, eg:
[Flair] My post title

The following is a list of suggested flairs:
[Discussion] - General discussion.
[Help] - A request for help or support.
[News] - News about the deck.
[PSA] - Sharing important information.
[Game] - News / info about a game on the deck.
[Update] - An update to a previous post.
[Meta] - Discussion about this community.

Some more Steam Deck specific flairs:
[Boot Screen] - Custom boot screens/videos.
[Selling] - If you are selling your deck.

These are not enforced, but they are encouraged.

Rules:

Link to our Matrix Space

founded 3 years ago
MODERATORS
Moxvallix@sopuli.xyz
codus@leby.dev
timi@lemmy.world
RolAIDS05@lemmy.world
Fubarberry@sopuli.xyz
RolAIDS05@sopuli.xyz
31
[PSA] If you had switched to the main update channel to get 3.5 early, I would recommend changing back one of the less bleeding edge update channels. (sopuli.xyz)
submitted 1 year ago* (last edited 1 year ago) by Fubarberry@sopuli.xyz to c/steamdeck@sopuli.xyz
12 comments fedilink hide all child comments
 

SteamOS 3.6 is live on the "main" update channel, and it is very buggy. (Note: the most bleeding edge update channel is called main. 3.6 is only live on the "main" channel, not any of the stable or beta channels).

I had switched to main to get 3.5 early, and 3.5 had spent so much time in the main channel that it's been very stable for the last few months. However 3.6 has been rough, game mode would crash and restart everytime a decky plugin did something, and it broke my desktop mode completely. I've downgraded to beta-candidate (which is still 3.5) and things are much better.

I know that staying off the most bleeding edge update channels if you want a stable experience is common sense, but I think a lot of people got impatient for 3.5 and may have been lulled into a false sense of security by how stable the 3.5 main update builds were recently.

top 12 comments
sorted by: hot top controversial new old
[–] bjoern_tantau@swg-empire.de 8 points 1 year ago* (last edited 1 year ago)

And I even feel like 3.5 isn't entirely as stable as it should be. Got some random crashes. Although it's not nearly as bad as it was a few months ago. So I will stay on beta for now.

Edit: Went back to stable yesterday because of too many crashes. Funnily enough it crashed on my first attempt to downgrade. The second attempt worked, though.

[–] CleoTheWizard@beehaw.org 2 points 1 year ago

Side note but I was using the stable build but was forced to push up to the beta build because of a stupid bug where using remote play from a desktop would cause controllers to send double inputs for some reason. I tested multiple controllers and even a keyboard, all duplicated inputs.

It blew my mind that a hot fix wasn’t sent out. That’s a pretty big feature to break in a stable branch. I know it wasn’t everyone’s problem but still. I’m not sure what’s going on with the software stuff right now.

[–] Cappurnikus@lemmy.world 1 points 1 year ago (1 children)

I heard it's not working well with external displays. That's a no-go for me until external displays are working.

[–] Fubarberry@sopuli.xyz 1 points 1 year ago (1 children)

What kind of issues have you heard about? Also are you talking about 3.5 or 3.6?

[–] Cappurnikus@lemmy.world 1 points 1 year ago (1 children)

I heard external displays aren't working on 3.5

[–] Fubarberry@sopuli.xyz 2 points 1 year ago* (last edited 1 year ago)

I've been on 3.5 for awhile, and they're working fine for me. I did have an issue where occasionally my TV would reset (go black for a second and then come back on), that I hadn't noticed before on previous SteamOS versions, but searching online makes it seem like that's a problem with Vizio TVs and 4k/HDR, not a SteamOS issue. I was able to duplicate the issue using a 4k Chromecast on the TV, and disabling HDR and capping the resolution below 4k completely fixed the issue when using the Deck with the TV.