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
Proton version: All versions up to 8.0-2 (for now)
I confirm:
that I haven't found an existing compatibility report for this game.
that I have checked whether there are updates for my system available.
Note:
For all of the following logs I have used nothing else but the parameter "PROTON_LOG=1 %command%".
My Linux distro of choice is OpenSUSE Tumbleweed, this distro has AppArmor constantly enabled in the background, this is noteworthy when doing debugging.
This log is with Proton 8.0-2, it fails immediately after having done the initialization of Ubisoft Connect, it can't even create the window of the game. You have to stop the process manually from within the Steam app by pressing "STOP" as after failure it will remain open in the background forever. steam-298110 8.0-2.log
This log is done with GE-Proton8-6, I am aware this is not the place to report Proton GE issues but I am using it only to report what happens once you pass the Ubisoft connect phase and actually manage to create a window. In this case as said the window gets fully created but it crashes a few seconds in during the very first loading screen, not even allowing me to enter into the main menu.
In this case as-well the process will hang forever and the only way to make it stop is by stopping it from withing the Steam app. steam-298110 GE-Proton8-6.log
Many reports on the game's ProtonDB page suggest switching to a Proton version equal or inferior to 6.3 as that's the patch that broke the game into the current situation it's in. Unfortunately the behavior is virtually identical to the one of 8.0-2 as it can't pass from the Ubisoft connect launcher properly and it crashes before creating the game window. steam-298110 6.3-8.log
Currently for me it's impossible to play this game in any way shape or form, if I can be useful for any ulterior testing let me know and I will provide all the help I can!
Thank you in advance! :)
The text was updated successfully, but these errors were encountered:
Hello @Plarpoon, we're using one issue report per unofficially supported game title, so I've gone ahead and transferred this issue report to #2143 (comment).
Compatibility Report
System Information
I confirm:
Note:
This log is with Proton 8.0-2, it fails immediately after having done the initialization of Ubisoft Connect, it can't even create the window of the game. You have to stop the process manually from within the Steam app by pressing "STOP" as after failure it will remain open in the background forever.
steam-298110 8.0-2.log
This log is done with GE-Proton8-6, I am aware this is not the place to report Proton GE issues but I am using it only to report what happens once you pass the Ubisoft connect phase and actually manage to create a window. In this case as said the window gets fully created but it crashes a few seconds in during the very first loading screen, not even allowing me to enter into the main menu.
In this case as-well the process will hang forever and the only way to make it stop is by stopping it from withing the Steam app.
steam-298110 GE-Proton8-6.log
Many reports on the game's ProtonDB page suggest switching to a Proton version equal or inferior to 6.3 as that's the patch that broke the game into the current situation it's in. Unfortunately the behavior is virtually identical to the one of 8.0-2 as it can't pass from the Ubisoft connect launcher properly and it crashes before creating the game window.
steam-298110 6.3-8.log
I have also added a log with proton experimental (timestamped) but it behaves exactly like Proton 8.0-2.
steam-298110 Proton Experimental 21 Jul 2023.log
Currently for me it's impossible to play this game in any way shape or form, if I can be useful for any ulterior testing let me know and I will provide all the help I can!
Thank you in advance! :)
The text was updated successfully, but these errors were encountered: