Update UPlay dependency to Ubisoft Connect

[ChaosBlades]

Currently all Ubisoft games come with the UPlayInstaller.exe dependency that automatically installs upon first launch of the game. Please update this installer to Ubisoft Connect for the following reasons.

• UPlay has an annoying bug where it will forever be stuck on "Looking for Patches" that Ubisoft Connect does not have.
• Ubisoft Connect will automatically detect your Steam Account and automatically log you in. The current installer forces you to log in on every single different Ubisoft game you install then it updates to Ubisoft Connect.

I have tested this by deleting the compatdata folder for games. Then replacing the UPlayInstaller.exe located in the games data directory with the UbisoftConnectInstaller.exe renamed to UPlayInstaller.exe. Every game I have tried installed all the dependancies including Ubisoft Connect and launched the game without any errors. Without getting stuck on "Looking for Patches" and without the need to sign into UPlay.

[ChaosBlades]

Watch Dogs 1 uses a version of UPlay so old it fails in a different way. I get this error.. After using the method described above the game installs Ubisoft Connect correctly and at this point updates my now old installer that I downloaded to the latest version, detects my previous sign in and launches the game without issue.

Overall these third party DRM launchers like Ubisoft Connect and EA Origin should have automatically updating dependencies that install upon fist launch instead of shipping with a certain version then relying on legacy support in order to get the DRM launcher up to date.

[thaewrapt]

I think some of the games (I've got only one of them so far, a reboot of Flashback) using Ubisoft launchers just got updated recently to use a new depot, an Ubisoft Connect one. While this eliminated the issue w/ updating/replacing launchers, the "Looking for patch" loop issue is still here for both 6.3-8 and current Experimental. I'm in fact recalling some upstream patch included in 6.22 addressing that issue (and it's definitely included in current Proton-GE, which behaves normally for Ubisoft Connect for that game).

[thaewrapt]

Patch notes for aforementioned game update: https://steamcommunity.com/games/245730/announcements/detail/3148575800209543740

Also, I was wrong about the Wine upstream fixes for Ubisoft Connect, I've seen it on Proton-GE-6.21 release notes, stating this:

-Fsync has been disabled on all Uplay titles -- it causes Uplay to hang on "Looking for patches" when initiationg a new prefix. Esync works fine.

I'll probably retest Flashback (245730) with FSync disabled.

[thaewrapt]

Ok, can confirm that running the game with PROTON_NO_FSYNC=1 %command% eliminated the "Looking for patches" issue with 6.3-8.

[FreddieOliveira]

Currently neither of the alternatives work anymore, at least for me. UPlayInstaller.exe dependency was already updated to UbisoftConnectInstaller.exe as requested by @ChaosBlades, but it is getting stuck into the "Looking for patches" anyway:

And running the game with PROTON_NO_FSYNC=1 %command% as suggested by @thaewrapt doesn't make any difference.

[thefrana]

This is an issue for me as well. I tried all versions of Steam Proton. None of them worked. Any workaround?

[qwertychouskie]

To get past the "Looking for patches" error I had to disable both Fsync and Esync. After the update I re-enabled them.

[FreddieOliveira]

Apparently, Proton's latest version fixed the "Looking for patches" issue. I simply installed steam on my Ubuntu, enabled Proton experimental in the config and launched the same game that was giving me the problem back then (Assassins Creed Chronicles: India) and everything worked smoothly out of the box. No need of PROTON_NO_FSYNC=1 %command% or disabling Fsync and Esync.

[netborg-afps]

Have tried a while to get Assassin's Creed Origins working until I finally found the instructions of the OP, which was a quick workaround to get the game finally running on Linux. (UPlay just didn't work)

I also checked how it would behave on Windows, and it certainly used UbisoftConnect and the UbisoftConnectInstaller.exe is present in the game's root folder. Not sure if it used UPlay as an intermediate step, I could recheck.