Assassins Creed Origins (582160)

[thaleslimao]

Under the games when clicking on play brings me the UPLAY login screen.

When adding my credentials always returns me error and I can not connect,

If anyone can simulate this scenario to see where exactly the error is, thank you.

Kubuntu 18.04

[kisak-valve]

Hello @thaleslimao, please copy your system information from steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

Most likely the same issue as other uplay games.

[thaleslimao]

@kisak-valve

https://gist.github.com/thaleslimao/cb1bb26a44c3d1bfa16ad6da9415cdcc

[lieff]

Does game works without uplay login?

[Alexmitter]

@thaleslimao It is known that Proton does not contain a certain patch that is included in the current wine-staging, it fixes this Uplay bug.

@lieff No, Uplay also don't allow offline use of Uplay until you are logged in once.

[Alexmitter]

@kisak-valve is there any plan to include the Wine Patches in question to make Uplay login possible?

[jacobsandersen]

Is there a current workaround (force use of wine patches?)

[Alexmitter]

@simpleauthority For this, you would need to apply the patches to the source code and compile it yourself.

[Alexmitter]

Today Proton 3.16 got released. Uplay now let you log in but fails at the "initialize" part were it once again tells you that it is unable to connect to Ubisoft Servers.
@kisak-valve are there any patches of 3.16 not included?

[d10sfan]

@Alexmitter You may need to do this to get it to fully work: #162 and then once that's done, uplay may ask you to install steam. If you let it (and in a different directory), the rest should work as expected.

[Alexmitter]

@d10sfan yes i can confirm those symlinks do help.

[ghost]

Symlink a recent libgnutls version solves the problem initializing Uplay, but when launching Origin is trying to find a Steam installation in Windows.

I have tried to bypass it by deleting Steam folder already exists under Program Files directory and installing the one Uplay trying to install.

After this Uplay can continue, download savedata on cloud and initialize the game. I can see the AC Origin process in processes tree using 6-10% CPU during 10 sec, so it seems is trying to load, but after these seconds, the process is killed.

[dreamer]

@hsanchezv to work around Uplay looking for Steam - just pass some new directory to Windows Steam installer, DO NOT launch Steam automatically (just let Uplay put files in there) and it's enough - game will work. It's kind of stupid, that we're wasting ~400 MiB to download Windows Steam inside Windows Uplay inside Linux Steam, but at least it doesn't need to be started.

[tryton-vanmeer]

It would be interesting to know how Uplay checks if Steam is installed. Then it could be integrated into proton, thus removing this work around and lead to less confusion to users.

If Uplay was checking the Windows registry, I'm sure Proton could add a registry entry to the default prefix.

[Dexter9313]

I have a better workaround which costs no disk space : I launch the game once so that Steam Play creates the prefix, Uplay updates and all that then I close everything (closing Steam is not necessary) and I symlink an already existing Steam Wine installation I have installed with Lutris within the game's prefix. (Something along :
rm -rf $STEAM_LIB/compatdata/xxxxx/pfx/drive_c/$PROGRAMFILES/Steam
ln -s $HOME/.wine/drive_c/$PROGRAMFILES/Steam $STEAM_LIB/compatdata/xxxxx/pfx/drive_c/$PROGRAMFILES/Steam
)
I launch the game again and Steam doesn't complain being installed in a non-empty directory (you effectively just reinstall your Steam Wine, register keys will be created in the game's prefix and Uplay will be happy and Steam seems to not care to reinstall on top of itself).

[ghost]

I have seen Uplay log and I think that is the error:

[1025/202256.590:ERROR:network_change_notifier_win.cc(157)] WSALookupServiceBegin failed with: 8
[1025/202256.890:ERROR:viz_main_impl.cc(201)] Exiting GPU process due to errors during initialization
[1025/202257.151:ERROR:viz_main_impl.cc(201)] Exiting GPU process due to errors during initialization
[1025/202257.163:ERROR:browser_gpu_channel_host_factory.cc(119)] Failed to launch GPU process.
[1025/202257.164:ERROR:gpu_process_transport_factory.cc(1026)] Lost UI shared context.

I still investigating.

[arno01]

I've managed to re-compile the Proton from official source repo (along with the Wine, FAudio, lsteamclient, vrclient, dxvk) in my Ubuntu:Bionic docker container. I haven't changed anything, except that I did not use Steam Runtime when compiled the Proton. Then, I used GCC/G++ v8 instead of v5 as in the docs, libgnutls v30 instead of v26. And I've also gotten additional libs opencl.dll.so, winegstreamer.dll.so, wineoss.drv.so under lib64/wine (for some reason these aren't in the Proton 3.16 Beta). Otherwise, I've got nothing missing from my build. DXVK v0.90-206-g3b3ccc8.

The UPC.exe (Uplay) is now finally working (I can login there and see games in the Uplay UI). Unfortunately ACOrigins.exe is just running for ~10 seconds and quits. Nothing interesting is in the logs at a quick glance. (PROTON_LOGS=1 %command%). Additionally I've seen in the debug logs it was trying to load msmpeg2adec.dll, msmpeg2vdec.dll, sqmapi.dll so I've taken those from my Windows 7 and registered them, they got loaded with no issues, but that did not help the game to start.

Digging deeper, it appears like the game has the DENUVO DRM protection which is probably preventing the game from running in Proton/Wine. I am not 100% sure if it is because of that and whether this can be worked around.

$ grep DENUVO /home/user/.local/share/Steam/steamapps/common/Assassins\ Creed\ Origins/Support/License/lic_en-US.txt

3.1 THE PRODUCT IS PROTECTED BY DIGITAL RIGHTS MANAGEMENT SOFTWARE (“DRM SOFTWARE”) AND DENUVO ANTI-TAMPER PROTECTION TECHNOLOGY (“ANTI-TAMPER TECHNOLOGY”).

I am going to try rebasing my Proton over the latest wine-staging 4.0-rc4 and DXVK v0.94 and see if things get better. Will post in case if I find it starts the ACOrigins.exe.

[lox-enterprises]

@arno01 I don't have Origins, but I wonder what the differences are in DRM between all the AC games. Apparently, Unity works, and Odyssey does not show this issue, so where does Origins fit in? Also, could it perhaps be a 'simple' connection issue, where it fails to check the game with the server?

[arno01]

@1202software I haven't been digging into any DRM module, so no clue whether it is a culprit. Just speculating.

Meanwhile I have built Proton with wine-4.0-rc4 (plus wine-staging 4.0-rc4 patches except: xaudio2_7-CreateFX-FXEcho, xaudio2_7-WMA_support as they were drastically breaking some of xaudio2 commits that I have incorporated ValveSoftware/wine@967f095438, ValveSoftware/wine@ce7cacbbf7, ValveSoftware/wine@0d66671809, ValveSoftware/wine@478f3c4a2c)

Plus these Valve patches to make Wine work with Steam and enable Liberation fonts so Uplay window won't go transparent/black (with the xaudio2 patches along as FAudio is what we want, IIRC by looking at ValveSoftware/wine#2 , FNA-XNA/FAudio#46):

user@proton:~/proton/wine$ git log HEAD...wine-4.0-rc4 --pretty='%C(blue)[%ai] %<(8)%C(green)%h %<(70,trunc)%s %<(15,trunc)by %an %ar'       
[2018-12-18 11:44:49 -0500] a2c8f63fed xaudio2: Rewrite I/O for new FACTFileIOCallbacks support               by Ethan Lee       13 days ago
[2018-12-17 17:35:11 -0500] 8221ad992a xaudio2: Unwrap XAudio2 pointers, ReadFile needs OVERLAPPED, unwrap_.. by Ethan Lee       2 weeks ago
[2018-12-17 09:54:30 -0500] c4f43b9744 xaudio2: XACT CLSID fixes                                              by Ethan Lee       2 weeks ago
[2018-12-10 12:48:41 -0600] 6cf2333bd8 xaudio2: Set PulseAudio application name property in the environment   by Andrew Eikum    3 weeks ago
[2018-12-06 11:26:50 -0600] f0045124b8 xaudio2: Consistently prefer native on 32-bit                          by Andrew Eikum    4 weeks ago
[2018-11-27 12:04:24 -0600] 6e83192c22 xaudio2: Wait for engine thread to be ready                            by Andrew Eikum    5 weeks ago
[2018-11-16 15:41:22 -0500] cae84b0a3c [xaudio2] Add support for xactengine3                                  by Ethan Lee       6 weeks ago
[2018-11-16 15:39:10 -0500] 23569e587e [xaudio2] Rewrite to use FAudio                                        by Ethan Lee       6 weeks ago
[2018-03-19 11:34:35 -0500] 6f36b4a13c kernel32: Don't force-load Steam.dll                                   by Andrew Eikum    10 months ago
[2018-01-19 14:01:07 -0600] 8251e80e29 HACK: advapi32: Use steamuser as Wine username                         by Andrew Eikum    12 months ago
[2017-12-28 09:43:36 -0600] 1ee8861593 kernel32: Support steamclient64                                        by Andrew Eikum    1 year ago
[2017-12-27 13:31:59 -0600] 751ebb13d9 loader: Set up Steam stuff in the registry                             by Andrew Eikum    1 year ago
[2017-06-13 12:35:56 -0500] 35345f0566 HACK: kernel32: Put Steam program files dir into PATH                  by Andrew Eikum    1 year, 7 months ago
[2017-06-09 10:31:27 -0500] 2ac8a7a5af HACK: kernel32: Return steamclient instead of lsteamclient during Ge.. by Andrew Eikum    1 year, 7 months ago
[2017-06-05 14:41:28 -0500] 438186eca7 HACK: kernel32: Load hard-coded Steam.dll path if relative load fails  by Andrew Eikum    1 year, 7 months ago
[2017-05-11 10:50:08 -0500] 6184c9c256 HACK: kernel32: Swap requests for steamclient.dll with lsteamclient    by Andrew Eikum    1 year, 8 months ago
[2017-04-27 13:25:04 -0500] d7df85e2bc HACK kernel32: Substitute the current pid for the Steam client pid     by Andrew Eikum    1 year, 8 months ago
[2018-10-23 16:18:20 +0300] d6762eac0b wine.inf: Add font registry entries.                                   by Nikolay Sivov   10 weeks ago
[2018-12-31 19:23:45 +0100] 539c4d18cc apply wine-staging 4.0-rc4 patches (-2)                                by Andrey Arapov   34 minutes ago

So not much of a progress with the game... ;-/
Here is the maps for ACOrigins.exe running for ~10 seconds:
https://0.nixaid.com/?3d13a180a2b8d990#WWxatWE8+WoNPgAKKzNhwYx3ySgjiGDxIorx3/3FvzQ=

Update 1

The good point is that with Proton based off wine-stg-4.0-rc4 I can finally set 240Hz screen refresh rate in Call of Duty 4: Modern Warfare

And the game picks own screen resolution now (I can see it when I do Alt-Tab). I am not sure whether this is something new that comes with >= wine-3.16 or maybe it is something that should have been dropped by the Valve patches from proton_3.16 branch? In the default Proton 3.16 when any game is running it feels like it isn't running in its own resolution, but rather uses the current user's screen resolution. So in-game one can see (and set) max. of 60Hz whilst the game is actually running 120Hz/240Hz (of course only if the user sets such in his Xorg [xrandr] / nvidia-settings / .. and the monitor supports such, obviously).

Upd2 [31/Dec/2018]: played Broadcast map (CoD4 MW), got ~60-80 fps outside (in the street), up to 140 fps inside (in the building) on my GTX 1060 6GB; 16GB RAM; i7 2600 @3.40GHz.

Upd3 [1/Jan/2019]: actually the performance is much better with the Proton built off the bare proton_3.16 branch, most likely this is because I haven't merged all the Valve's patches as some of them improve the performance. If anyone is wondering, here is my build env. for building Proton in Docker https://git.nixaid.com/arno/proton/

[Arucard1983]

When proton 4.11.1 and 4.11.2 was released this game finally works. It is still necessary to disable Uplay Overlay to the game start (or it will stall with a black window).
Probably the VMProtect DRM now runs correctly with the last branch of Wine.
The funny thing is the Uplay Overlay works partially (the game don't stall at beginning) when it runs the Windows version of Steam using plain Wine or running with Lutris with some games of Assassin's Creed saga.

[Patola]

Fixed. Noticed in steam play my wife's configuration pointed to proton 4.2-9. Changed to 4.11-2 and it played correctly.

[oliwer]

Hi. I just tried to run AC Origins with Proton 5.0.4 and it fails to run. It was working fine with Proton 5.0.3. What happens is Uplay starts the game, a new window appears for less than a second and disappear, and then nothing. The ACOrigins.exe process remains alive, but it does nothing (0% cpu usage). I have to manually close Uplay to kill the process.

steam-582160.log.gz

[alasky17]

We have found a fix for this, which will be in the next Proton release. In the meantime, there is a new app branch for the Proton 5.0 app called "proton-5.0-3" which you can use to play the game. You can find it on the BETAS tab in the settings for the Proton 5.0 tool in your Steam client.

[vahidshirvani]

@smintman Thanks a lot for testing this. The fix should be now live in Proton Experimental [bleeding edge] branch (available to select in Proton Experimental properties, "Betas" tab): ValveSoftware/wine@872e73a

I didn't look at desktop mode warning, that is likely something unrelated to this in-game (or in-menu) freeze issue.

Want to confirm that your fix indeed works. Thanks a lot.

[gofman]

@smintman

Is there anything we can feedback to the Ubisoft support forum as to why this issue was happening, as I think it was also affecting windows 7 users?

I am not sure if it is the same issue on Win7, I don't have a Win7 machine to run my tests now. If anyone is curious attached is my test case (source code and that code compiled with MSVC for x64/Release, default options). Running that on Win7 and showing the output (or comparing that with Win10) may tell if that is the same issue.
test.zip

UPDATE: I actually attached wrong source code, here is the actual one: https://gist.github.com/gofman/3287a953bcab3a5c888a8d494461cb8a

[mercifulboss]

Replying to #928 (comment)

thank you, the fix seems to work. not sure what caused it but it seems to work on multiple game launches and playing for 10 mins. however, i discovered that trying to use steam overlay (to get rid of CD key appearing) will freeze the game again.

[kakra]

Many Ubisoft games seem to be unstable with the Steam overlay, so you may want to disable it for those games. Should get rid of the key notification, too.

[mercifulboss]

I understand it is likely better to get rid of steam overlay, but when I do I encounter another issue - steam stops recognizing my controller. This is only fixed by closing the game and then turning on steam overlay. So it leaves me with no choice unfortunately, which is why I was wondering if something can be done about the steam overlay?

[kakra]

Hmm, strange... The controller still works for me even with the overlay disabled. Then again, maybe you're using Steam Input, and that seems to require the Steam overlay enabled for some games (e.g., HZD) for the controller to work. So you could also try disabling Steam Input for this game, most SDL-supported controllers should still work then.

[mercifulboss]

Hmm, strange... The controller still works for me even with the overlay disabled. Then again, maybe you're using Steam Input, and that seems to require the Steam overlay enabled for some games (e.g., HZD) for the controller to work. So you could also try disabling Steam Input for this game, most SDL-supported controllers should still work then.

Not sure what Steam Input is but I have an Xbox controller that I use. KDE recognizes it when its connected but the game does not if the overlay is off.

[kakra]

Not sure what Steam Input is but I have an Xbox controller that I use.

That controller should work, I'm using the same (actually, as the xpadneo developer, I'm owning all models, and each one works). Steam Input is the controller mapping tool available from the overlay. To disable Steam Input, either go to the game properties and disable "Xbox controller support" per game, or go to Steam settings to disable it globally. Disabling support for the controller only affects controller support through Steam Input and the overlay, it does not disable the controller for games (usually, there are a few games that actually use Steam Input directly, and need both Steam Input and the overlay enabled, for those games you can still individually enable that support per game if disabled globally). If you see mapping problems with the buttons after disabling Steam Input, try stopping the Steam client, reconnect the controller and start Steam again. Maybe try disabling Steam Input globally in the client and enable per game if needed. An alternative driver may also work around those issues (xpadneo for Bluetooth, xone for the dongle).

PS: I'm not sure why Steam Input seems to be depending on the overlay enabled (at least for some games), and vice-versa, Valve should probably fix that.

[mercifulboss]

Replying to #928 (comment)

I think I understand what you are saying. I will try to disable Steam Input for this game.

I was thinking maybe I have problems because I use xbox controller with xow? Its an app that lets me use my dongle with my controller.

[kakra]

I was thinking maybe I have problems because I use xbox controller with xow? Its an app that lets me use my dongle with my controller.

Yes, I know that project well. This is superseded by xone now, xow does not receive further development. You may want to join our Discord server (it's about xpadneo, xow, and xone, joining the developers of each project in one pool), there are people who can help you finding the correct settings.

[Tripp024]

Anyone else freezing at startup screen with the experimental build? Bleeding edge works fine but I thought the fix was now merged into experimental? Something else must be going on then.

[alasky17]

@smintman @vahidshirvani The fix is live in experimental-7.0-20220714b. Hopefully you aren't seeing the hang after the recent game update anymore?

@Tripp024 Could you get 2 logs (just add PROTON_LOG=1 %command% to the command line) -- 1)the freeze on experimental-7.0-20220714b and 2) the game not freezing and proceeding correctly on bleeding-edge

[Tripp024]

@alasky17 I found out it just happens randomly on the experimental build. It has nothing to do with bleeding edge. It froze once again before I turned on the logging, I tried booting it again a few times afterwards and then it worked fine. Maybe it was some temporary glitch with uplay or something. Logging is on now so when it happens again I'll post the log. Btw, the freeze happened on the warning screen and I'm using a Steam Deck.

[ChaosBlades]

This game does not support FreeSync correctly on linux. Not sure if this would be considered a problem with Proton or Linux itself. Have not noticed this issue on any other games. The FreeSync value (hz) will be half that of the FPS. If the fps is 120fps it will be 60hz and if it is 140fps it will be 70hz and so on. Every once in a while it will read correctly which makes for a very inconsistent experience.

[QushyQushy]

The game freezes on launch on a 7900X, 790XTX. Here's the Proton Log:

steam-582160.log

[kisak-valve]

Hello @QushyQushy, can you temporarily remove or disable mangohud, gamemode, and vkBasalt and see if that has an effect?

[QushyQushy]

Hello @QushyQushy, can you temporarily remove or disable mangohud, gamemode, and vkBasalt and see if that has an effect?

Perfect suggestion and I'm sorry for providing a Proton Log with all these enabled. Power of habbit. XD

vkBasalt seems to be the culprit. I will open an issue on vkBasalt's Github. :)

[abc123098123]

The game freezes on launch on a 7900X, 790XTX. Here's the Proton Log:

steam-582160.log

I am having exactly the same issue, on the same graphics card, but I am not using any command line arguments, on Proton Experimental. It perpetually stays in the splash screen warning.

steam-582160.log

EDIT: Ok, STEAM OVERLAY was the culprit. Turned it off, everything works now.

[dsyer]

I had the same problem yesterday but I had already switched the overlay off (many months ago - maybe it tried to switch it back on after a uplay update?). The only way I could fix it was to delete the game and re-install, and then I could switch the overlay off when it started for the first time. I don't know if that's what fixed it, but then the ubisoft connect app started cleanly and the game launched.

[kisak-valve]

Ubisoft Games not working because connection lost always.

Issue transferred from #7420.
@vuaieo posted on 2024-01-18T12:16:43:

Compatibility Report

• Name of the game with compatibility issues: ASSASINS CREED ORIGINS
• Steam AppID of the game: 582160

System Information

• GPU: 3080 ti
• Video driver version: 535.154.05
• Kernel version: 6.7.0-204.fsync.fc39.x86_64 (64-bit)
• Link to full system information report as Gist:
• Proton version: many different , from most recent ones to 5.x...

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.

steam-582160.log

Symptoms

hi if i launch the assasins creed origins game then the ubisoft launcher starts and trying to connect to their service or so but it always fails, and cant run on offline mode because need at least 1 time need to be online in order to use offline mode, so i stuck in the loop and cant play ubisoft games anymore on steam. please help T_T
tryed many different proton and GE proton versions but nothing helps , its always the same.

here are the screenshots of the messages:

i remmber last year or so it worked "fine" so something musst have happen...

well if install the ubisoft launcher as a game and start it then the launcher works ok and i think i could play some games but because the assasins creed origin i got on steam its bound to steam acc and so clicking on download opens the launcher and its still same problem... = so cant play : (

Reproduction

just start the assasins creed origin game 🖖

[ShalokShalom]

Replying to #928 (comment)

I can confirm this on the Steam Deck, as I have seen it happening to someone on social media.

[Patola]

Just to make it clear, the game is working great for me, no issues whatsover, Proton-8.0-4, https://gist.github.com/Patola/5b0f3d30bfdbf276b183d32f997c8500 (Archlinux, Ryzen 7 7800X3D, RX 7900 XTX). So this does not affect everyone. I can try on my nvidia laptop to see if the problem is the GPU.

[ShalokShalom]

Just to make it clear, the game is working great for me, no issues whatsover, Proton-8.0-4, https://gist.github.com/Patola/5b0f3d30bfdbf276b183d32f997c8500 (Archlinux, Ryzen 7 7800X3D, RX 7900 XTX). So this does not affect everyone. I can try on my nvidia laptop to see if the problem is the GPU.

No, as this is confirmed to happen on the AMD GPU in the Steam Deck as well.

[kakra]

Ubisoft Games not working because connection lost always.

@vuaieo Try sudo sysctl -w net.ipv4.tcp_mtu_probing=1 before starting the game and report, if that helps.

[vuaieo]

@kakra ok did this command in terminal but it didnt helped, its still same

[kakra]

@kakra ok did this command in terminal but it didnt helped, its still same

Rename your prefix (it's the folder 582160 in $HOME/.steam/steam/steamapps/compatdata), e.g. name it 582160.bak. Apply my sysctl fix, and then start the game. It should reinstall a current version of Ubisoft Connect. Maybe something is broken in your prefix. You will loose your graphics and game settings. If that works, you can try copying over the folder pfx/driver_c/users/steamuser from the backup prefix to the new prefix, this should bring your game settings back.

If it still doesn't work, restore your prefix backup folder (rename 582160 to 582160.failed, then rename 582160.bak to 582160), and retry with PROTON_NO_FSYNC=1 %command% as launch options in your game properties. If this helps, you may see #2922. Sometimes, this is only needed to fix updating the launcher, and after that it will work with fsync again. MTU probing may still be needed because without, services of Ubisoft sometimes cannot be reached. Windows defaults to MTU probing on.

[migg0naut]

I had the same issue @vuaieo was having (and it seems that many on protondb have the same problem) and sadly non of the solutions @kakra was proposing were working for me either.

However, after i used protontricks to install ubisoft connect for the game, it started and i was able to play through the intro with no issues so far
I hope this helps others too.

[kisak-valve]

Assassin’s Creed Origins - Black Screen

Issue transferred from #7872.
@CreeperofDoom posted on 2024-07-04T17:17:11:

Compatibility Report

• Name of the game with compatibility issues: Assassin’s Creed Origins
• Steam AppID of the game: 582160

System Information

• Steam Deck OLED - Steam OS 3.6.8
• Proton version: Experimental

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.

Symptoms

2 Days ago i opened Assassin’s Creed Origins on my Steam Deck OLED and it only shows a Black Screen, The Sound of the game still plays and the controller still functions, its just the screen thats pitch black.
I tried: Verifying the game files, Reinstalling the game from Steam, Clearing the Proton Compatibility Data (which deletes all game data and the Third Party Launcher requiring it to reinstall)
I also tried connecting it to a dock onto a TV, i tried forcing resolutions and it didn’t work. I also tried switching to Proton 9 and 8 and that didn’t work. i tried the Community Made GE-Proton and i get the same issue. I have no idea what causes it