<?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>icg837 Tracker</title>
    <link>https://community.stadia.com/ysfdd67284/tracker</link>
    <description>icg837 Tracker</description>
    <pubDate>Mon, 16 Jan 2023 06:41:26 GMT</pubDate>
    <dc:date>2023-01-16T06:41:26Z</dc:date>
    <item>
      <title>Re: Calling GNU/Linux users.</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Calling-GNU-Linux-users/m-p/27642#M1775</link>
      <description>&lt;P&gt;Hello. I'll post my experience so far with this trouble.&lt;/P&gt;&lt;P&gt;I'm using Arch Linux right now. Before I was using Manjaro, Ubuntu and other Linux distributions. On every distro, using or Chromium or Google Chrome or Brave, installing vaapi or video-intel or whatever package (or even with no install), and enabling hardware acceleration in every browser with whatever video render package I could install, I was unable to use Stadia at 1080p. For the record, I'm using a Mac Mini, and this is not a problem because I could play Stadia with Microsoft Edge at 1080p smoothly, but for other reasons I couldn't use Windows as I wanted.&lt;/P&gt;&lt;P&gt;And this is not a problem of Linux, besides this problem being present on every Linux distro I used. I say that because I'm using Chromium OS right now, which is based on Linux, and I can use Stadia at 1080p smoothly, installing no obsucre packages at all and doing nothing but execute Chromium browser and ready to go.&lt;/P&gt;&lt;P&gt;I don't know who is to blame or who has the ultimate responsibility, but it's a pain reboot to Chromium OS and afterwards reboot to my Linux distro, and so on.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Aug 2020 19:28:47 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Calling-GNU-Linux-users/m-p/27642#M1775</guid>
      <dc:creator>icg837</dc:creator>
      <dc:date>2020-08-03T19:28:47Z</dc:date>
    </item>
    <item>
      <title>Windows at 1080, Linux at 720?</title>
      <link>https://community.stadia.com/t5/Stadia-General/Windows-at-1080-Linux-at-720/m-p/25368#M11827</link>
      <description>&lt;P&gt;Hello.&lt;/P&gt;&lt;P&gt;I've found this issue recenlty, when I was trying Windows 10 on my Mac Mini 2016. For the record, I wiped out MacOS completely in favour of Linux two years ago.&lt;/P&gt;&lt;P&gt;The point is, it doesn't matter which browser I'm using (Google Chrome/Chromium/Brave...), Linux (currently Debian) only can play Stadia at 720 with ethernet connection and 100mb up/down. 1080 is totally unplayable. I've tried every tip over the Internet, and nothing worked.&lt;/P&gt;&lt;P&gt;So, as I said, I was trying Windows 10, and I was curious, so I've installed the new Edge version, and tried Stadia on it. And to my surprise, I was able to play Stadia at 1080 with absolutely no issues. Great detail and fully playable and enjoyable. The same with other Chromium based browsers.&lt;/P&gt;&lt;P&gt;So, my question. Why is it possible that I can play Stadia at 1080 on Windows, and I can't do the same on Linux, using the same machine? Any tips or something?&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jun 2020 09:48:09 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-General/Windows-at-1080-Linux-at-720/m-p/25368#M11827</guid>
      <dc:creator>icg837</dc:creator>
      <dc:date>2020-06-23T09:48:09Z</dc:date>
    </item>
  </channel>
</rss>

