<?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>topic Re: Intolerable Input lag in Stadia on Chrome</title>
    <link>https://community.stadia.com/t5/Stadia-on-Chrome/Intolerable-Input-lag/m-p/13749#M705</link>
    <description>Mad Dog, I did this with no change. Point 3 has no baring though since I use controller.</description>
    <pubDate>Fri, 24 Jan 2020 20:20:23 GMT</pubDate>
    <dc:creator>kevlo16</dc:creator>
    <dc:date>2020-01-24T20:20:23Z</dc:date>
    <item>
      <title>Intolerable Input lag</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Intolerable-Input-lag/m-p/13732#M701</link>
      <description>A friend gave me his buddy pass (whatever it's called) and I've been trying to use it for lightweight activities but the input lag is HORRENDOUS. Game: Destiny 2 Computer: Surface Pro 6 (4gb ram, i5 CPU, Windows 10 Pro, connected to docking station with dual 24" monitors (HD, not 4k, not HDR) Input: MS Elite v2 Controller Internet: Verizon Fios Gigabit over wifi (with Orbi mesh network (AC3000)), typical speed tests where I sit are between 130Mbps and 200Mbps, 7-12ms ping) Stadia Video Settings:Data usage set to "Limited" (720p resolution), HDR turned off The thing is, most of the time the game will perform without issue if I'm using m &amp;amp; K (but I'm simply not capable of gaming on M &amp;amp; K, controller is the ONLY option for me). I've tried using different USB cords, and also tried using the controller wireless, all the same. I borrowed a friends laptop, Dell i7, 32gb ram, Windows 10 Pro and I'm able to play just fine on that setup (with the controller or M &amp;amp; K), The Dell is obviously much more powerful than my surface pro, but isn't the whole point of Stadia that it's all in the cloud and not operating on your specific machine? The convenience of Stadia makes me want to solve this, but with this lag it is literally UNPLAYABLE, (1-3 seconds from input to action is not something one can tolerate). I've been on with Stadia support and despite solid, honest effort they were not able to help. Has anyone here had this issue and been able to solve it?</description>
      <pubDate>Fri, 24 Jan 2020 15:46:28 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Intolerable-Input-lag/m-p/13732#M701</guid>
      <dc:creator>kevlo16</dc:creator>
      <dc:date>2020-01-24T15:46:28Z</dc:date>
    </item>
    <item>
      <title>Re: Intolerable Input lag</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Intolerable-Input-lag/m-p/13735#M702</link>
      <description>&lt;P&gt;&lt;SPAN&gt;30hz will give you that input lag ... Stadia only works at 60hz or 50hz via home application&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 24 Jan 2020 16:19:11 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Intolerable-Input-lag/m-p/13735#M702</guid>
      <dc:creator>Whito</dc:creator>
      <dc:date>2020-01-24T16:19:11Z</dc:date>
    </item>
    <item>
      <title>Re: Intolerable Input lag</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Intolerable-Input-lag/m-p/13739#M703</link>
      <description>&lt;P&gt;&lt;a href="https://community.stadia.com/t5/user/viewprofilepage/user-id/15414"&gt;@kevlo16&lt;/a&gt;&amp;nbsp;:&lt;/P&gt;&lt;P&gt;A few things to check and see if they improve the situation for you:&lt;/P&gt;&lt;P&gt;1. Reset Chrome flags - go to the URL chrome://flags , select "Reset all to default", restart Chrome and try again.&lt;/P&gt;&lt;P&gt;2. Run Chrome and use an Incognito window and see if that helps, disable any extensions that might have been added.&lt;/P&gt;&lt;P&gt;3. Reduce refresh rate on mouse pointer (usually a feature on some mouse drivers).&lt;/P&gt;&lt;P&gt;4. Access Chrome flags and enable the feature "Enables pointer lock options".&lt;/P&gt;&lt;P&gt;5. On Windows 8 run Chrome in Windows 7 compatibility mode.&amp;nbsp;&lt;/P&gt;&lt;P&gt;6.&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;Black screen on Chrome, try: Chrome flags and set Hardware accelerated video decode to Disabled.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 24 Jan 2020 17:00:06 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Intolerable-Input-lag/m-p/13739#M703</guid>
      <dc:creator>Mad_Dog_Bravo</dc:creator>
      <dc:date>2020-01-24T17:00:06Z</dc:date>
    </item>
    <item>
      <title>Re: Intolerable Input lag</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Intolerable-Input-lag/m-p/13749#M705</link>
      <description>Mad Dog, I did this with no change. Point 3 has no baring though since I use controller.</description>
      <pubDate>Fri, 24 Jan 2020 20:20:23 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Intolerable-Input-lag/m-p/13749#M705</guid>
      <dc:creator>kevlo16</dc:creator>
      <dc:date>2020-01-24T20:20:23Z</dc:date>
    </item>
    <item>
      <title>Re: Intolerable Input lag</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Intolerable-Input-lag/m-p/13755#M706</link>
      <description>&lt;P&gt;&lt;a href="https://community.stadia.com/t5/user/viewprofilepage/user-id/15414"&gt;@kevlo16&lt;/a&gt;&amp;nbsp;: Thanks for trying, I'm not sure what to suggest after those options to be honest....&lt;/P&gt;</description>
      <pubDate>Fri, 24 Jan 2020 23:01:18 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Intolerable-Input-lag/m-p/13755#M706</guid>
      <dc:creator>Mad_Dog_Bravo</dc:creator>
      <dc:date>2020-01-24T23:01:18Z</dc:date>
    </item>
    <item>
      <title>Re: Intolerable Input lag</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Intolerable-Input-lag/m-p/13763#M707</link>
      <description>Try running stadia in google canary (dev browser - you can download it). Solved the problem for me.</description>
      <pubDate>Sat, 25 Jan 2020 09:46:58 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Intolerable-Input-lag/m-p/13763#M707</guid>
      <dc:creator>Nournoise</dc:creator>
      <dc:date>2020-01-25T09:46:58Z</dc:date>
    </item>
    <item>
      <title>Re: Intolerable Input lag</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Intolerable-Input-lag/m-p/13850#M710</link>
      <description>Hi on my system i reduced the input lag from unplayable to "it makes no fun" with activating ipv6 (on MS Webside you can find tools to restart ipv6)</description>
      <pubDate>Sun, 26 Jan 2020 17:19:17 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Intolerable-Input-lag/m-p/13850#M710</guid>
      <dc:creator>Willrock</dc:creator>
      <dc:date>2020-01-26T17:19:17Z</dc:date>
    </item>
  </channel>
</rss>

