<?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 Your mouse is not currently captured by the game in Stadia on Chrome</title>
    <link>https://community.stadia.com/t5/Stadia-on-Chrome/Your-mouse-is-not-currently-captured-by-the-game/m-p/75728#M4742</link>
    <description>&lt;P&gt;This is one of those errors that crops up, goes away, and crops up again.&amp;nbsp;&lt;/P&gt;&lt;P&gt;The biggest problem with this type of error is that it never fully goes away AND can be aggressive at times which, for me, makes Stadia unusable.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;U&gt;Recreating the problem:&lt;/U&gt;&lt;/P&gt;&lt;P&gt;Earlier in Stadia's life, you could minimize your window, maximize the same window and you would receive the error of, "Your mouse is not currently captured by the game".&amp;nbsp;Additionally, you could multi-task (Windows: Atl-tab) to another window, do some work there, then alt-tab back to the Stadia window and immediately receive the error. This would happen in any game where the mouse was necessary to game play.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;U&gt;Possible previous solutions which may/may not have worked to a varying level:&lt;/U&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Press a keyboard key (likely ensuring focus was given to the Chrome window, then try your mouse - it would work)&lt;/LI&gt;&lt;LI&gt;Min/Max the window again and hope that the listener for the mouse would pick it up&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;Alt-Tab multiple times in/out of the Chrome window in hopes it would recognize the mouse as well&amp;nbsp;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;I suspect this error is dependent on the version of Chrome you are using. Some, were just SOLID and this error NEVER happened; didn't matter what you did to try and foul it. Keyboard and Mouse were ALWAYS picked up. Then, a new version of Chrome would deploy and you're right back to this error. Interestingly, I've never once had the window not recognize the keyboard. Never a hesitation or missed keypress. Mouse? I've got a 40% chance of it not seeing the mouse when I come back to the Chrome window.&lt;/P&gt;&lt;P&gt;Can we get a definitive response on what method is employed to attach the mouse to the Chrome instance and when that method is initiated?&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 28 Jan 2022 19:02:01 GMT</pubDate>
    <dc:creator>mes0</dc:creator>
    <dc:date>2022-01-28T19:02:01Z</dc:date>
    <item>
      <title>Your mouse is not currently captured by the game</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Your-mouse-is-not-currently-captured-by-the-game/m-p/75728#M4742</link>
      <description>&lt;P&gt;This is one of those errors that crops up, goes away, and crops up again.&amp;nbsp;&lt;/P&gt;&lt;P&gt;The biggest problem with this type of error is that it never fully goes away AND can be aggressive at times which, for me, makes Stadia unusable.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;U&gt;Recreating the problem:&lt;/U&gt;&lt;/P&gt;&lt;P&gt;Earlier in Stadia's life, you could minimize your window, maximize the same window and you would receive the error of, "Your mouse is not currently captured by the game".&amp;nbsp;Additionally, you could multi-task (Windows: Atl-tab) to another window, do some work there, then alt-tab back to the Stadia window and immediately receive the error. This would happen in any game where the mouse was necessary to game play.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;U&gt;Possible previous solutions which may/may not have worked to a varying level:&lt;/U&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Press a keyboard key (likely ensuring focus was given to the Chrome window, then try your mouse - it would work)&lt;/LI&gt;&lt;LI&gt;Min/Max the window again and hope that the listener for the mouse would pick it up&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;Alt-Tab multiple times in/out of the Chrome window in hopes it would recognize the mouse as well&amp;nbsp;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;I suspect this error is dependent on the version of Chrome you are using. Some, were just SOLID and this error NEVER happened; didn't matter what you did to try and foul it. Keyboard and Mouse were ALWAYS picked up. Then, a new version of Chrome would deploy and you're right back to this error. Interestingly, I've never once had the window not recognize the keyboard. Never a hesitation or missed keypress. Mouse? I've got a 40% chance of it not seeing the mouse when I come back to the Chrome window.&lt;/P&gt;&lt;P&gt;Can we get a definitive response on what method is employed to attach the mouse to the Chrome instance and when that method is initiated?&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 28 Jan 2022 19:02:01 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Your-mouse-is-not-currently-captured-by-the-game/m-p/75728#M4742</guid>
      <dc:creator>mes0</dc:creator>
      <dc:date>2022-01-28T19:02:01Z</dc:date>
    </item>
  </channel>
</rss>

