this post was submitted on 09 Nov 2023
222 points (97.0% liked)
Games
16745 readers
716 users here now
Video game news oriented community. No NanoUFO is not a bot :)
Posts.
- News oriented content (general reviews, previews or retrospectives allowed).
- Broad discussion posts (preferably not only about a specific game).
- No humor/memes etc..
- No affiliate links
- No advertising.
- No clickbait, editorialized, sensational titles. State the game in question in the title. No all caps.
- No self promotion.
- No duplicate posts, newer post will be deleted unless there is more discussion in one of the posts.
- No politics.
Comments.
- No personal attacks.
- Obey instance rules.
- No low effort comments(one or two words, emoji etc..)
- Please use spoiler tags for spoilers.
My goal is just to have a community where people can go and see what new game news is out for the day and comment on it.
Other communities:
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It would be pretty easy to add a trigger when it plugs in to check if you're above some battery threshold, and, if you have pending downloads, complete them with the screen off, with a "download then sleep" button on the download page that turns off the screen.
I'm fine with other priorities instead, because the actual pace of development is perfectly fine, but it could be done without a lot of downside.
I think psvita did it right. If you turn off the screen with download in progress, it'll continue the download, but will pause if it's not completed within about an hour so you won't get surprised with drained battery next time you turn it on. Windows "modern standby" however is notorious for draining laptop battery when you put your laptop to "sleep". Maybe valve can get it right unlike microsoft, and if they do, would be great if it could be ported to other linux laptop considering steam deck uses a laptop SoC.
Supposedly a big part of the issue is around specific low power states of the CPU either not existing or not being supported correctly. I don't really follow any of that that closely.
But you don't need any of that for a solution that would satisfy the vast majority of customers. Just doing the heavy lifting during "sleep" (to the user; the actual processor sleep state isn't important) only when plugged in would solve close to everything and kick the inconvenience from "most users" to "edge cases" with minimal side effects.