• AutoTL;DRB
    link
    fedilink
    English
    38 months ago

    This is the best summary I could come up with:


    If you read my scoop last week, I bet you’ve been wondering — how well could a Snapdragon chip actually run Windows games?

    With medium-weight games like Control and Baldur’s Gate 3, it looks like the target might be: 30 frames per second at 1080p screen resolution, medium settings, possibly with AMD’s FSR 1.0 spatial upscaling enabled.

    That’s what Qualcomm has apparently been showing influencers, according to numerous videos from YouTubers, TikTokers, and “Snapdragon Insiders,” many of which were uploaded over the past week after they flew down to Qualcomm’s San Diego headquarters for the company’s “eXperience Day.”

    While some of the videos feel a little promotional — one influencer talks about how he’s seeing “Elden Ring playing really nicely at about 30 frames per second” while actually showing Baldur’s Gate 3 running at a mere 21-24fps — it’s admittedly pretty neat to see games like these running on Arm silicon at all.

    Enobong Etteh, aka BooredAtWork, has the video with the most uninterrupted gameplay footage; he apparently got to try Control, Baldur’s Gate 3, and Redout 2 at Mobile World Congress in Barcelona this February.

    In early scenes from Control that don’t demand as much horsepower, we’re seeing frame rates that dip as low as 26fps in a firefight or between 30fps and 40fps just running around.


    The original article contains 500 words, the summary contains 218 words. Saved 56%. I’m a bot and I’m open source!

  • @romp_2_door
    link
    18 months ago

    30 frames per second at 1080p

    honestly that’s pathetic for a “2024 flagship”

    I’m not impressed

    • @fuckwit_mcbumcrumble
      link
      English
      88 months ago

      Considering it’s emulating the code, not directly running it that’s not bad.

      My M1 MBP gets about 80% CPU usage trying to run an old ass version of world of warcraft in a VM. GPU usage is high, but it definitely is choking on the CPU side of things more than GPU, and I assume this is going to be the same bottleneck.