This game had pretty mixed performance at launch, with most cutscenes running at 2-4 fps. Non-combat sections could get up to 60fps, but other areas would dip below 30fps.
I didn’t hear much about this game after launch, so I wasnt expecting it to get much support and polish. Glad that it seems to be getting better
That’s fair. I’m surprised you’re still having crashes on stable though, it might be worth updating to pre-release and see if that fixes it.
There were several plugins that broke awhile back with Steam client changes, I know at least SteamGridDB, MagicBlack, Brightness Bar all broke, and I think one about managing airpods broke too. I know SteamGridDB is working again, but I haven’t gotten around to reinstalling the other ones yet. The SteamGridDB fix specifically required a decky update and not an update to the plugin to fix, so hopefully the other plugins are all fixed on the pre-release build of decky as well.
If you’re on steamOS beta/steam client beta, you have to also be on the pre release version of decky (you can select this when running the decky installer).
Even then, new updates to the deck/client can break decky and extensions. Decky will usually be updated to fix any broken updates within a day or so, but plugins can be broken much longer before they get an update. You’ll often find that you have to uninstall a specific plugin for a couple weeks.
Anyways if you want decky to work pretty smoothly, I’d suggest sticking to stable. If you don’t mind some troubleshooting and brief down periods, you can make it work on beta. I’d recommend getting on the Steam Deck Homebrew discord server so that whenever something breaks you can easily find out why and what you need to do about it.
I play mine enough that I never turn it off. I usually play multiple short sessions throughout the day, so having instant suspend/resume from the middle of the game is much more important to me than the minor battery drain.
I’d only turn it off if I didn’t expect to play it for a few days, but even then I would probably just stick it on my dock in sleep mode, and trust pass-through charging to keep the battery healthy.
Yes, the frame is the one most likely to not fit. If it’s an issue we’ll deal with it then.
Sure, that’s perfectly acceptable for this community
Unfortunately it depends on the app and where you view it. The app I use (Thunder) shows Steam Hardware at the top of the community and in the community list, but shows “steamdeck” in small texts under posts still.
Sorry, I don’t actually know about the frame. I should have clarified I was talking primarily about the Machine.
I can definitely get that for Steam Frame, but I feel like docked Steam Deck and Steam Machine are basically the same experience, just with different performance levels.
It’s also easily user replaceable, it comes with the same smaller size m.2 as the steam deck, but will work with full size m.2 cards as well.
They have keyboards like that, but other than analog triggers I don’t know of any controllers with that feature.
But I noticed in the video that he mentions running a second command in the terminal and potentially having to change the Neptune number (the video was made for 65, but the deck is on 611 now) on that second command to reflect the current version number.
You might want to check the GitHub itself, specifically this issue.
It has the commands to run to fix kernel mismatch errors during install
That’s the default mode, you have to manually toggle a setting before it will do it on battery.
The steamOS UI uses a decent bit of power by itself, but that power drain goes away completely once you’re in game (you can get much better power life in low power games like Stardew than you can on the steam library screen for example).
I’m guessing this turns off the UI while downloading, which should drop power usage a fair bit. However downloading itself can be quite power consuming, so there’s definitely going to be some drain still.
I’ve had it act like it forgot the WiFi password, but I think it was just a connection issue. I think I just backed out without entering anything and tried reconnecting, and it reconnected fine with the stored password.
Hell yeah
Edit:trying it out now, seems to work really well. There are two settings for it, both under Settings>Power.
One enables it at all (and is turned on by default once updated), the other enables it on battery power specifically.
With it enabled, pressing the power button to sleep mid download will pop up a dialog window asking if you want to download with the screen off, or sleep. The initially selected option is download before sleep (so pressing A without intentionally changing your selection will choose this option). If you don’t press any buttons for 10 seconds it will just go directly to sleep instead.
I absolutely love Metroid Dread, sorry to hear you’re not enjoying it much.
I just finished Trails in the Sky 1st Chapter yesterday, so I haven’t fully settled into what to play next. I think I’ll go through my installed games and try to finish some games I was enjoying but never finished all the way, like Ys 9 and 1000xResist.
Mostly Trails in the Sky First Chapter. It is possible that I just reached more demanding parts of the game, although the power usage have really changed.
Anyways it’s hard to say for sure, just wanted to see if anyone else had noticed something similar.
Yeah, I have my microSD set to btrfs format, but it breaks auto mount every SteamOS update. I know there are ways to set it to automatically fix this, but I’ve been using a lazier option of just having a shell script to fix the fstab (file that tells the computer what to mount and where) that I run once after every steamOS update.
It’s not a perfect solution, but it makes fixing it easy enough that I haven’t looked into a permanent fix.
A similar setup would probably work for your external drive, basically after I had the microSD setup how I wanted it, I just copied it’s fstab configuration line. The shell script just adds that line to the bottom of the fstab file when I run it, and then after a quick reboot all my games are back and everything works again.