You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 18, 2022. It is now read-only.
I use the extension to force 4K resolution, which is otherwise unavailable since my system lacks support for VP9 hardware decoding. This usually(*) works fine initially, and I can see that the network monitor confirms that VP9 and 3840x2160 is used. But if I exit the game using the Stadia button (or I'm thrown out automatically due to inactivity) and then re-enter the game using the same tab as before, the resolution is no longer forced to 4K but drops to 1920x1080 (using H.264). If I close the Stadia tab and open a new one using the extension ("Launch Stadia"), the resolution override again works fine (once).
(*) The lack of forcing the second time is 100% reproducible, and I've seen it many, many times. In rare cases the 4K forcing doesn't work the first time either, but that's really rare and might be some unrelated phenomenon (like Google having capacity problems temporarily).
The text was updated successfully, but these errors were encountered:
rwestman
changed the title
Force resolution doesn't work after restarting a game, unless I also close/reopen the Stadia tab
Forced resolution stops working after restarting a game, unless I also close/reopen the Stadia tab
Jul 7, 2020
I use the extension to force 4K resolution, which is otherwise unavailable since my system lacks support for VP9 hardware decoding. This usually(*) works fine initially, and I can see that the network monitor confirms that VP9 and 3840x2160 is used. But if I exit the game using the Stadia button (or I'm thrown out automatically due to inactivity) and then re-enter the game using the same tab as before, the resolution is no longer forced to 4K but drops to 1920x1080 (using H.264). If I close the Stadia tab and open a new one using the extension ("Launch Stadia"), the resolution override again works fine (once).
(*) The lack of forcing the second time is 100% reproducible, and I've seen it many, many times. In rare cases the 4K forcing doesn't work the first time either, but that's really rare and might be some unrelated phenomenon (like Google having capacity problems temporarily).
The text was updated successfully, but these errors were encountered: