<?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 Stadia Controller Latency/Buffering over Wi-Fi in The Stadia Controller</title>
    <link>https://community.stadia.com/t5/The-Stadia-Controller/Stadia-Controller-Latency-Buffering-over-Wi-Fi/m-p/5327#M159</link>
    <description>Hi all, I'm having a really strange problem with my Stadia Controller and I want to see if anyone else has seen this. First, here are some details about my setup: - 1 Gbps upload and download internet with AT&amp;amp;T fiber - Chromecast Ultra wired directly into my home network - Excellent Wi-Fi coverage / speed for my Stadia controller (Ubiquiti gear tells me the controller is connected to the 5GHz band and chose the 433 Mbps MCS) - 4k TV in game mode I think that covers all my bases on the obvious suggestions to combat latency. The kind of latency I'm seeing is different. The best way to explain it is to show it: &lt;A href="https://www.youtube.com/watch?v=YfEU2a3TcqQ" target="_blank"&gt;https://www.youtube.com/watch?v=YfEU2a3TcqQ&lt;/A&gt;. The crux of it is that it seems like the controller falls behind in sending its inputs and eventually buffers up a huge multi-second delay. When the controller is idle, the first input has very little latency. This isn't normal, right? I've seen relatively few references online to people having an experience like mine. Unfortunately, this makes actually playing anything basically impossible. For what it is worth, this same controller wired into my laptop and playing in a Chrome browser works perfectly. That's great, but I bought it primarily to be a console-like experience on my bedroom TV. I'd appreciate it if anyone else can confirm they see this. Thanks!</description>
    <pubDate>Sun, 24 Nov 2019 15:57:07 GMT</pubDate>
    <dc:creator>drchris</dc:creator>
    <dc:date>2019-11-24T15:57:07Z</dc:date>
    <item>
      <title>Stadia Controller Latency/Buffering over Wi-Fi</title>
      <link>https://community.stadia.com/t5/The-Stadia-Controller/Stadia-Controller-Latency-Buffering-over-Wi-Fi/m-p/5327#M159</link>
      <description>Hi all, I'm having a really strange problem with my Stadia Controller and I want to see if anyone else has seen this. First, here are some details about my setup: - 1 Gbps upload and download internet with AT&amp;amp;T fiber - Chromecast Ultra wired directly into my home network - Excellent Wi-Fi coverage / speed for my Stadia controller (Ubiquiti gear tells me the controller is connected to the 5GHz band and chose the 433 Mbps MCS) - 4k TV in game mode I think that covers all my bases on the obvious suggestions to combat latency. The kind of latency I'm seeing is different. The best way to explain it is to show it: &lt;A href="https://www.youtube.com/watch?v=YfEU2a3TcqQ" target="_blank"&gt;https://www.youtube.com/watch?v=YfEU2a3TcqQ&lt;/A&gt;. The crux of it is that it seems like the controller falls behind in sending its inputs and eventually buffers up a huge multi-second delay. When the controller is idle, the first input has very little latency. This isn't normal, right? I've seen relatively few references online to people having an experience like mine. Unfortunately, this makes actually playing anything basically impossible. For what it is worth, this same controller wired into my laptop and playing in a Chrome browser works perfectly. That's great, but I bought it primarily to be a console-like experience on my bedroom TV. I'd appreciate it if anyone else can confirm they see this. Thanks!</description>
      <pubDate>Sun, 24 Nov 2019 15:57:07 GMT</pubDate>
      <guid>https://community.stadia.com/t5/The-Stadia-Controller/Stadia-Controller-Latency-Buffering-over-Wi-Fi/m-p/5327#M159</guid>
      <dc:creator>drchris</dc:creator>
      <dc:date>2019-11-24T15:57:07Z</dc:date>
    </item>
    <item>
      <title>Re: Stadia Controller Latency/Buffering over Wi-Fi</title>
      <link>https://community.stadia.com/t5/The-Stadia-Controller/Stadia-Controller-Latency-Buffering-over-Wi-Fi/m-p/5840#M189</link>
      <description>If its any consolation, I'm in the same boat pretty much. * ATT Uverse 1Gbps up/down. (FTTH) (Configured for DMZ Plus/passhthrough) * Nest WIFI. Base router is in the same room as me, and confirmed that the controller binds to that AP. (Funny, I just dropped my old ubiquity gear for this.) * WPA3 enabled, and Game Preferred is enabled. (I've tried it with both on and off.) Nest wifi speed tests float around 649/150, while targeted speed tests with other tools normally float &amp;gt;700/&amp;gt;400 with ATT modem tests usually staying at the &amp;gt;800/&amp;gt;800 range. Not experiencing any screen artifacts, or notices of poor connection/disconnects. (Regardless of hardwired/wireless PC, or hardwired/wireless chromecast.) I plan to do some testing connected to my phone, it's just not been my priority as I plop down start playing and stop caring. &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.stadia.com/html/@86D5B654F5634F41B85D1B72D3D92E1F/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt; I've poked stadia on twitter about it, but consider it low priority for myself right now. If it's still an issue after a few more weeks then I'll start hitting up the support channel to see what I can tweak. Curious if you get any traction on a fix.</description>
      <pubDate>Mon, 25 Nov 2019 22:11:42 GMT</pubDate>
      <guid>https://community.stadia.com/t5/The-Stadia-Controller/Stadia-Controller-Latency-Buffering-over-Wi-Fi/m-p/5840#M189</guid>
      <dc:creator>RyudenPhoenix</dc:creator>
      <dc:date>2019-11-25T22:11:42Z</dc:date>
    </item>
    <item>
      <title>Re: Stadia Controller Latency/Buffering over Wi-Fi</title>
      <link>https://community.stadia.com/t5/The-Stadia-Controller/Stadia-Controller-Latency-Buffering-over-Wi-Fi/m-p/5843#M190</link>
      <description>Thanks for the comment. For what it's worth, counting myself I've now seen exactly 3 references to this problem (with the third being this reddit thread: &lt;A href="https://www.reddit.com/r/Stadia/comments/dzbk49/controller_input_lag/" target="_blank"&gt;https://www.reddit.com/r/Stadia/comments/dzbk49/controller_input_lag/&lt;/A&gt; ). All three people have AT&amp;amp;T fiber internet...</description>
      <pubDate>Mon, 25 Nov 2019 22:22:50 GMT</pubDate>
      <guid>https://community.stadia.com/t5/The-Stadia-Controller/Stadia-Controller-Latency-Buffering-over-Wi-Fi/m-p/5843#M190</guid>
      <dc:creator>drchris</dc:creator>
      <dc:date>2019-11-25T22:22:50Z</dc:date>
    </item>
    <item>
      <title>Re: Stadia Controller Latency/Buffering over Wi-Fi</title>
      <link>https://community.stadia.com/t5/The-Stadia-Controller/Stadia-Controller-Latency-Buffering-over-Wi-Fi/m-p/5858#M192</link>
      <description>Att being a common denominator? Say it ain't so... I've had issues in the past with optimal paths on Uverse... my luck that's probably related. (They really like my traffic going south 500 miles, only to wind up routing to a CNF 200 miles north of me for peering with other providers including google.)</description>
      <pubDate>Mon, 25 Nov 2019 23:10:42 GMT</pubDate>
      <guid>https://community.stadia.com/t5/The-Stadia-Controller/Stadia-Controller-Latency-Buffering-over-Wi-Fi/m-p/5858#M192</guid>
      <dc:creator>RyudenPhoenix</dc:creator>
      <dc:date>2019-11-25T23:10:42Z</dc:date>
    </item>
    <item>
      <title>Re: Stadia Controller Latency/Buffering over Wi-Fi</title>
      <link>https://community.stadia.com/t5/The-Stadia-Controller/Stadia-Controller-Latency-Buffering-over-Wi-Fi/m-p/5867#M193</link>
      <description>&lt;P&gt;I guess for more banter...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have IPv6 enabled, but it appears my PC &amp;lt;-&amp;gt; stadia while streaming is IPv4. That address I'm averaging 19.8ms response time.&lt;/P&gt;&lt;P&gt;I'll have to see about finding what the controller is talking to next... I would assume it is the same destination but I'm not where I can capture that.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Surprisingly, I'm talking to something at the end of that 500 mile stretch for my first path of ATT and not being re-routed up north. So, that's good. &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.stadia.com/html/@86D5B654F5634F41B85D1B72D3D92E1F/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 25 Nov 2019 23:36:40 GMT</pubDate>
      <guid>https://community.stadia.com/t5/The-Stadia-Controller/Stadia-Controller-Latency-Buffering-over-Wi-Fi/m-p/5867#M193</guid>
      <dc:creator>RyudenPhoenix</dc:creator>
      <dc:date>2019-11-25T23:36:40Z</dc:date>
    </item>
    <item>
      <title>Re: Stadia Controller Latency/Buffering over Wi-Fi</title>
      <link>https://community.stadia.com/t5/The-Stadia-Controller/Stadia-Controller-Latency-Buffering-over-Wi-Fi/m-p/7125#M260</link>
      <description>This is really annoying and as you said, renders the game unplayable. I have the same problem, although it's not as bad as yours. Everything is setup as it should, wired, game mode etc, but there is noticeable input lag on Chromecast. On laptop, wired, no issues.</description>
      <pubDate>Thu, 28 Nov 2019 15:31:06 GMT</pubDate>
      <guid>https://community.stadia.com/t5/The-Stadia-Controller/Stadia-Controller-Latency-Buffering-over-Wi-Fi/m-p/7125#M260</guid>
      <dc:creator>ZanzibearX</dc:creator>
      <dc:date>2019-11-28T15:31:06Z</dc:date>
    </item>
    <item>
      <title>Re: Stadia Controller Latency/Buffering over Wi-Fi</title>
      <link>https://community.stadia.com/t5/The-Stadia-Controller/Stadia-Controller-Latency-Buffering-over-Wi-Fi/m-p/9710#M443</link>
      <description>Closing the loop on this thread. TLDR; I think most everyone has gotten this working by reconnecting directly to their ATT Modem's wifi rather than using the dmz/passthrough to devices behind it. To add some more color, I've put mine in "true bypass mode" which removes the ATT modem from handling any traffic beyond satisfying the 802.1x cert challenge. This allows me to have my nest wifi -&amp;gt; ubiquity router -&amp;gt; ONT Internet Direct to GPON on house. (The att modem's ONT port sits off another port on my ubiquity to respond with the cert, but nothing is connected to it's LAN and it's WIFI is disabled.) In this config, my issues are also gone. That pretty much to me says it is an issue that surfaces when the ATT Modem is configured in passthrough, and the connectivity of the controller passes through the back-end device in that setup. So options: 1. Connect to the wifi on the uverse modem. 2. Setup the full bypass if you can. (bread crumb: &lt;A href="https://medium.com/@mrtcve/at-t-gigabit-fiber-modem-bypass-using-unifi-usg-updated-c628f7f458cf" target="_blank"&gt;https://medium.com/@mrtcve/at-t-gigabit-fiber-modem-bypass-using-unifi-usg-updated-c628f7f458cf&lt;/A&gt;) Good luck all! &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.stadia.com/html/@86D5B654F5634F41B85D1B72D3D92E1F/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt;</description>
      <pubDate>Thu, 12 Dec 2019 03:36:54 GMT</pubDate>
      <guid>https://community.stadia.com/t5/The-Stadia-Controller/Stadia-Controller-Latency-Buffering-over-Wi-Fi/m-p/9710#M443</guid>
      <dc:creator>RyudenPhoenix</dc:creator>
      <dc:date>2019-12-12T03:36:54Z</dc:date>
    </item>
  </channel>
</rss>

