this post was submitted on 14 Mar 2025
403 points (99.3% liked)

PC Gaming

10265 readers
341 users here now

For PC gaming news and discussion. PCGamingWiki

Rules:

  1. Be Respectful.
  2. No Spam or Porn.
  3. No Advertising.
  4. No Memes.
  5. No Tech Support.
  6. No questions about buying/building computers.
  7. No game suggestions, friend requests, surveys, or begging.
  8. No Let's Plays, streams, highlight reels/montages, random videos or shorts.
  9. No off-topic posts/comments, within reason.
  10. Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 14 points 2 days ago (1 children)

Not to undercut it, but the steam deck shows triple the actual game time for some of my games, as it probably counted the time the device was asleep with a game running, due to some glitch.

[–] [email protected] 18 points 2 days ago (1 children)

This should fix itself once it reconnects to the internet.
My time went from >100h after closing it back to a sane number.

[–] [email protected] 4 points 2 days ago (1 children)

So, it usually does. But I went to check again. It had me for 63 hours of Baldur's Gate 3 which I remembered was very off. I launched the game to check the in-game count : 19 hours. I exited the game, and lo and behold, Steam now says 16.8 hours.

I give it a B+ for effort.

[–] [email protected] 1 points 2 days ago (1 children)

Yeah if I remember right I needed to launch it once after this was so inflated and then it went back after syncing.
I mean it's okay as long as a sane number gets out.

[–] [email protected] 1 points 1 day ago (1 children)

It stayed at that high number for months though, despite periodically launching the game.

[–] [email protected] 1 points 1 day ago

Maybe a later fix that corrected it.