You have to run it for thousands of hours, while not playing games, to make it happen.

  • Poopfeast420@kbin.social
    link
    fedilink
    arrow-up
    1
    ·
    8 months ago

    needs to do now is to create a more realistic test. Using static elements for maybe 6 hours at a time every day

    That’s kinda useless. You might as well just wait for the user reports at that point.

    These unrealistic torture tests accelerate the potential burn-in, and it’s still useful to gauge how long it could really take.

      • Poopfeast420@kbin.social
        link
        fedilink
        arrow-up
        1
        ·
        8 months ago

        You’ll definitely have users gaming on the thing for 8+ hours every day, so I don’t see much value in that. Like I said, you might as well just wait for users to report their experiences.

        • helenslunch@feddit.nl
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          8 months ago

          You’ll definitely have users gaming on the thing for 8+ hours every day

          Yes, that’s exactly my point. Definitely some but not many.

          Like I said, you might as well just wait for users to report their experiences.

          Report them to whom, exactly? Not everyone is going to hop onto the internet to publicly report their issues. How are you going to account for the conditions? What if there’s nothing to report?

          • Poopfeast420@kbin.social
            link
            fedilink
            arrow-up
            0
            ·
            8 months ago

            Not everyone is going to hop onto the internet to publicly report their issues.

            But enough people are. People are talking about every small thing they did, what happened, whatever.

            Also, with all the different plugins or stats available on this thing to track everything, you can probably create a pretty detailed breakdown of what someone did with their Steam Deck.