<?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: Control input problem in Stadia on Chrome</title>
    <link>https://community.stadia.com/t5/Stadia-on-Chrome/Control-input-problem/m-p/30554#M1986</link>
    <description>&lt;P&gt;Yes, Chrome is alway up to date. Currently running&amp;nbsp;&lt;SPAN&gt;85.0.4183.121. I found that reddit thread after a few seconds, but I have spent hours on this.&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;Incognito mode made not difference. Just tried everything again before writing this.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Remember, everything runs perfect when there is no input. That tells me this is no performance problem. Feels like the sent input data cloggs the upstream line.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I appreciate the effort tho. Seems I am the only one with this issue.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 23 Sep 2020 17:32:25 GMT</pubDate>
    <dc:creator>Hagster</dc:creator>
    <dc:date>2020-09-23T17:32:25Z</dc:date>
    <item>
      <title>Control input problem</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Control-input-problem/m-p/30317#M1972</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I use Stadia for a few months and it has never worked on Chrome. I already spent hours searching but noone seems to have the same problem as me.&lt;/P&gt;&lt;P&gt;System:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;PC from 2014, was fairly strong at the time, still runs all games decently&lt;/LI&gt;&lt;LI&gt;Win 8&lt;/LI&gt;&lt;LI&gt;Completely fresh Chrome -&amp;gt; Installed -&amp;gt; Started Stadia&lt;/LI&gt;&lt;LI&gt;50 mbit/s fibre optics staight to house, Ethernet cable to PC&lt;/LI&gt;&lt;LI&gt;Everything runs perfect on Chromecast or Phone&lt;/LI&gt;&lt;LI&gt;Overall -&amp;gt; Perfect conditions for Stadia&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Problem:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;When there is no control input everything runs buttery smooth and looks great. That means there is no performance or settings issue.&lt;/LI&gt;&lt;LI&gt;Whenever I press a Button, move Mouse, the input is super delayed (!3-4 Seconds!) The picture becomes very pixelated. Entire seconds are dropped and skipped.&lt;/LI&gt;&lt;LI&gt;Same on Controller &amp;amp; Mouse/Keyboard. Not difference.&lt;/LI&gt;&lt;LI&gt;It feels like control inputs send too much data and the upstream is completely overwhelmed&lt;/LI&gt;&lt;LI&gt;When I stop inputs everything goes back to normal&lt;/LI&gt;&lt;LI&gt;Happens on every game&lt;/LI&gt;&lt;LI&gt;I have tried every chrome fix you can find online (deact. mouse acceleration, compatability mode, reset flags, force VP9, canary, ....)&lt;/LI&gt;&lt;LI&gt;Google support had no clue what to do&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;I am a bit frustrated because games are no fun with controllers (Its so slow and clumsy!!) and Stadia does not let me use a mouse on a mobile device. Would be perfect with Samsung Dex.&lt;/P&gt;&lt;P&gt;New computer is not an option because this was probably the last PC I ever bought. Until there is mouse support for the App I will probaby bury Stadia for now.&lt;/P&gt;&lt;P&gt;Regards!&lt;/P&gt;</description>
      <pubDate>Tue, 22 Sep 2020 08:48:44 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Control-input-problem/m-p/30317#M1972</guid>
      <dc:creator>Hagster</dc:creator>
      <dc:date>2020-09-22T08:48:44Z</dc:date>
    </item>
    <item>
      <title>Re: Control input problem</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Control-input-problem/m-p/30399#M1977</link>
      <description>&lt;P&gt;You mentioned you have tried almost all fixes already, just to confirm, you did also try to &lt;A href="https://support.google.com/chrome/answer/95414?co=GENIE.Platform%3DAndroid&amp;amp;oco=1" target="_self"&gt;update the Chrome Browser to have the recent version&lt;/A&gt;, right? Which version exactly is installed at the moment for you?&lt;/P&gt;&lt;P&gt;Not sure as well if you have tried to also disable the hardware acceleration and try again or to just disable and then enable it again to see if this might help you. More details you can find &lt;A href="https://www.reddit.com/r/Stadia/comments/e87agy/input_lag_fix_on_google_chrome/" target="_self"&gt;here on reddit&lt;/A&gt;. They are mentioning there as well that "disable pointer lock options" helped too, so this might be something worth to try as well.&lt;/P&gt;&lt;P&gt;Just interesting to try too: Can you try running the &lt;A href="https://support.google.com/chrome/answer/95464?hl=en" target="_self"&gt;incognito-mode of Chrome&lt;/A&gt; and try again if it's running better there?&lt;/P&gt;</description>
      <pubDate>Tue, 22 Sep 2020 20:36:45 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Control-input-problem/m-p/30399#M1977</guid>
      <dc:creator>Chufu</dc:creator>
      <dc:date>2020-09-22T20:36:45Z</dc:date>
    </item>
    <item>
      <title>Re: Control input problem</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Control-input-problem/m-p/30554#M1986</link>
      <description>&lt;P&gt;Yes, Chrome is alway up to date. Currently running&amp;nbsp;&lt;SPAN&gt;85.0.4183.121. I found that reddit thread after a few seconds, but I have spent hours on this.&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;Incognito mode made not difference. Just tried everything again before writing this.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Remember, everything runs perfect when there is no input. That tells me this is no performance problem. Feels like the sent input data cloggs the upstream line.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I appreciate the effort tho. Seems I am the only one with this issue.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 23 Sep 2020 17:32:25 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Control-input-problem/m-p/30554#M1986</guid>
      <dc:creator>Hagster</dc:creator>
      <dc:date>2020-09-23T17:32:25Z</dc:date>
    </item>
    <item>
      <title>Re: Control input problem</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Control-input-problem/m-p/30695#M1993</link>
      <description>&lt;P&gt;Your system might not be able to decode the video stream fast enough. This can add a very high latency on your system itself (not related to network latency).&lt;/P&gt;&lt;P&gt;Ideally, hardware (GPU) acceleration will give the best results, but if your GPU is not able (or not enabled to do that) the the system will resort to software (CPU) acceleration, and that's pretty intensive, and yes, is possible that a 2014 CPU might not be able to do it properly, especially at high resolutions.&lt;/P&gt;&lt;P&gt;Start small, go to your Stadia settings &amp;gt; Performance and set it to 720p, see if it works better. Additionally, add (for example) the &lt;STRONG&gt;StadiaEnhanced&lt;/STRONG&gt; extension and force the stream to H264.&amp;nbsp; At 720p + H264 the stream will&amp;nbsp; look rather bad, but is the least intensive setting for your system, and it can give an indication as what your system is capable.&lt;/P&gt;&lt;P&gt;If you want to check the actual video decoding latency, you can open &lt;STRONG&gt;chrome://webrtc-internals/&lt;/STRONG&gt;&amp;nbsp;(while the game is running) in another tab or window, &amp;gt; select the latest entry, and from the Stats Tables select&amp;nbsp;&lt;STRONG&gt;RTCInboundRTPVideoStream_****.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;You can find there useful information that can help you understand your issues, info such as:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;codec&lt;/STRONG&gt;: H264 or VP9&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;STRONG&gt;decoderImplementation&lt;/STRONG&gt;: ffmpeg/libvpx or ExternalDecoder (GPU)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;STRONG&gt;totalDecodeTime/framesDecoded_in_ms&lt;/STRONG&gt;: on my system&amp;nbsp;this takes for example 2.5 ms. You want this value to be as low as possible.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;There is a lot more there, but these should be sufficient.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Alternatively, to have a better view of the decoding times you can open (from the same Stats Tables)&amp;nbsp;&lt;STRONG&gt;Stats graphs for RTCInboundRTPVideoStream_***&amp;nbsp;&lt;/STRONG&gt;and check again&amp;nbsp;&lt;SPAN&gt;&lt;STRONG&gt;totalDecodeTime/framesDecoded_in_ms&lt;/STRONG&gt;, but this time in graph form, very useful too see how fast and stable is the video decoding process.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 25 Sep 2020 00:28:42 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Control-input-problem/m-p/30695#M1993</guid>
      <dc:creator>Dubigrasu</dc:creator>
      <dc:date>2020-09-25T00:28:42Z</dc:date>
    </item>
    <item>
      <title>Re: Control input problem</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Control-input-problem/m-p/67437#M4148</link>
      <description>&lt;P&gt;I have had this issue since day one, I've determined it to be an input delay between key presses. If you press 2 or more buttons one after another too fast, tafter the first button doesn't get registered at all. This mostly effects FPS games where your quickly pressing A,W,S,D to move, and often pressing AW, AS, SD,WD combinations to move diagonally, or quickly changing directions. Destany 2, Borderlands, Cyberpunk, Watchdogs, and any other FPS game I have played all have this issue, and forces me to use the controller which I can't stand.&lt;/P&gt;&lt;P&gt;For the record I'm on a 1Gbs fiber internet, and playing on a gaming PC, so I know it's not my connection speed or the "decoding" causing the lag. Picture quality has always been perfect with no input latency. Chrome is up to date as well. I believe it's something with the keyboard input software directly.&lt;/P&gt;</description>
      <pubDate>Sat, 04 Sep 2021 08:21:31 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Control-input-problem/m-p/67437#M4148</guid>
      <dc:creator>Evident</dc:creator>
      <dc:date>2021-09-04T08:21:31Z</dc:date>
    </item>
    <item>
      <title>Re: Control input problem</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Control-input-problem/m-p/67832#M4164</link>
      <description>&lt;P&gt;Same Problem here on the latest Version of Google Chrome.&lt;BR /&gt;I tried really everything, i have no idea.&lt;BR /&gt;Fun fact: In MS Edge there is no delay and no connection problem.&lt;/P&gt;</description>
      <pubDate>Sun, 12 Sep 2021 16:44:03 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Control-input-problem/m-p/67832#M4164</guid>
      <dc:creator>вᴏϻϻỉ</dc:creator>
      <dc:date>2021-09-12T16:44:03Z</dc:date>
    </item>
  </channel>
</rss>

