<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>OhMyGoose Tracker</title>
    <link>https://community.stadia.com/ysfdd67284/tracker</link>
    <description>OhMyGoose Tracker</description>
    <pubDate>Mon, 16 Jan 2023 09:14:51 GMT</pubDate>
    <dc:date>2023-01-16T09:14:51Z</dc:date>
    <item>
      <title>Re: Is 4K 60 FPS coming soon?</title>
      <link>https://community.stadia.com/t5/Stadia-General/Is-4K-60-FPS-coming-soon/m-p/5387#M2662</link>
      <description>Bungie has already confirmed that Destiny 2 is running at 1080p that is then upscale to 4K at medium settings. The Verge had an article on this. Same for Red Dead Redemption 2, which runs at 1440p and is upscaled. I think this is more of a developer issue, not Google’s. But, the problem is neither the developers not Google is being upfront about why getting native 4K/60 FPS is not possible. Google promised god-tier server specs, so we all expected 4K/60 FPS assuming our internet connections allowed. So is it a platform/hardware/infrastructure limitation that is hopefully temporary? Or are the devs just being lazy?</description>
      <pubDate>Sun, 24 Nov 2019 18:26:49 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-General/Is-4K-60-FPS-coming-soon/m-p/5387#M2662</guid>
      <dc:creator>OhMyGoose</dc:creator>
      <dc:date>2019-11-24T18:26:49Z</dc:date>
    </item>
  </channel>
</rss>

