

Division 2 on Stadia runs really well, after about one hour the game degrades into 20 - 30 fps. Quitting and reloading the game fixes the issue for another few hours. Also going into Ubisoft Connect and back to the game fixes the issue.
It was documented here https://forums.ubisoft.com/showthread.php/2303751-Ubisoft-Connect-causing-performance-degradation-on-all-Stadia-Ubisoft-games?s=774b0cbc02c9edf996c0bcaeebf27883: (https://forums.ubisoft.com/showthread.php/2303751-Ubisoft-Connect-causing-performance-degradation-on-all-Stadia-Ubisoft-games?s=774b0cbc02c9edf996c0bcaeebf27883) and it's still not fixed. Any updates on this?
https://support.google.com/stadia/answer/9595943
This has nothing to do with graphics settings on Stadia.
The game runs buttery smooth when freshly started. After about 20 minutes, you will notice it's not that responsive anymore. After an hour it's unplayable. Going into menu, loading Ubisoft connect and closing it, fixes that for some time. You will notice when the issue occurs, the Ubisoft connect takes time to react to any key press.
This feels like some memory buffer filling up and loading Ubisoft connect or performing logout/login fixes that.
Apparently, this issue is on Stadia for all Ubisoft games and just Ubisoft games.
Is everything clear now? Will this be fixed? According to Stadia this is a known server side issue and it has to be fixed by the game developer.
@ubi-wheelyduck so is this a well described bug already? When should we expect a fix?
Division 2 on Stadia runs really well, after about one hour the game degrades into 20 - 30 fps. Quitting and reloading the game fixes the issue for another few hours. Also going into Ubisoft Connect and back to the game fixes the issue.
It was documented here https://forums.ubisoft.com/showthread.php/2303751-Ubisoft-Connect-causing-performance-degradation-on-all-Stadia-Ubisoft-games?s=774b0cbc02c9edf996c0bcaeebf27883: (https://forums.ubisoft.com/showthread.php/2303751-Ubisoft-Connect-causing-performance-degradation-on-all-Stadia-Ubisoft-games?s=774b0cbc02c9edf996c0bcaeebf27883) and it's still not fixed. Any updates on this?