Compatibility Report

What exactly doesn't work with bundled gnutls, and how to reproduce this? Installed version is around 2.12 I think, and it is a bit old at this point.

For reference, see :

https://github.com/ValveSoftware/steam-runtime/issues/101

ok i try the game and working good, a minor issue with the steam controller but i can play the game with 30 fps and more, but you need make

cd .steam/bin32/steam-runtime/i386/usr/lib/i386-linux-gnu/
rm libgnutls.so.26
ln -s /usr/lib/i386-linux-gnu/libgnutls.so.30.14.10 libgnutls.so.26

and install steam in other path, i can play with more than hour and all good, with gtx 970, nvidia 410, and beta 3.16-3

With the 3.16-8 beta, AC: Unity / uPlay seems to work out-of-the-box. uPlay behaves and loads/launches properly, and Unity has pretty decent performance with no graphic/audio glitches.

Two relatively minor issues remain:

• sometimes crashes to desktop on first load of the main opening screen.
• using a Steam Controller causes the camera to spin in circles

Once a controller is connected the axis appear to get a large X and Y deflection. Instead of being centered, the view looks up and spins in one direction. This applies to both DS4 and Steam Controllers. The 0,0 point for controller input is being incorrectly set.
Using Proton 4.2-1.

Once the right trigger is held down the spinning stops, so this is an axis mapping issue.

Once a controller is connected the axis appear to get a large X and Y deflection. Instead of being centered, the view looks up and spins in one direction. This applies to both DS4 and Steam Controllers. The 0,0 point for controller input is being incorrectly set. [...] Once the right trigger is held down the spinning stops, so this is an axis mapping issue. -- @howels

I can reproduce this on Proton 4.2-2. Game is apparently working perfectly except for the controller support which means that I can't play it on the couch via Steam Link. :(

I found a workaround for the controller issue: Use a Steam Controller or enable configuration support for Xbox/etc., then edit the right trigger and swap the values for "Trigger Right Start" and "Trigger Right End" to invert the axis. Voilà, the camera does not spin anymore. It's playable, but not perfect because sometimes button presses are not properly registered during fights and I need to press LB + LT instead of just LT to sneak.

@holzhaus I need to get time to test. If any Dev can look at this it seems 99.9% playable now with only this controller issue remaining.

Working perfectly in Proton 4.2-5.

No remaining gameplay bugs (general Uplay overlay issue remains AFAIK but I always disable the overlay).

Suggest that AC: Unity is now whitelisted.

The game working good in the 4.2-7 and steam controller where before crash, but crash later of minutes playing before of start a mission, i have pending the log

I'm having some trouble with AC unity, I have a copy from uplay that I am trying to get running by adding it to the steam library as a non-steam game. It works in Lutris apart from the issue with the controller spinning that was already mentioned here. I was hoping that running it through steam's proton would circumvent that problem.

However running Uplay.exe from the steam library gives me:

GameAction [AppID 0, ActionID 10] : LaunchApp changed task to SiteLicenseSeatCheckout with ""
GameAction [AppID 0, ActionID 10] : LaunchApp changed task to CreatingProcess with ""
GameAction [AppID 0, ActionID 10] : LaunchApp waiting for user response to CreatingProcess ""
GameAction [AppID 0, ActionID 10] : LaunchApp continues with user response "CreatingProcess"
Game update: AppID 0 "Uplay.exe", ProcID 24908, IP 0.0.0.0:0
GameAction [AppID 0, ActionID 10] : LaunchApp changed task to Completed with ""
ERROR: ld.so: object '/home/andrew/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
/bin/sh: -c: line 0: syntax error near unexpected token `('
/bin/sh: -c: line 0: `'/home/andrew/.local/share/Steam/steamapps/common/Proton 3.16 Beta'/proton waitforexitandrun "/home/andrew/Games/assassins-creed-unity/drive_c/Program" Files (x86)/Ubisoft/Ubisoft Game Launcher/Uplay.exe'
>>> Adding process 24909 for game ID 33554432

And running ACU.exe gives me:

GameAction [AppID 0, ActionID 13] : LaunchApp changed task to SiteLicenseSeatCheckout with ""
GameAction [AppID 0, ActionID 13] : LaunchApp changed task to CreatingProcess with ""
GameAction [AppID 0, ActionID 13] : LaunchApp waiting for user response to CreatingProcess ""
GameAction [AppID 0, ActionID 13] : LaunchApp continues with user response "CreatingProcess"
Game update: AppID 0 "ACU.exe", ProcID 24922, IP 0.0.0.0:0
GameAction [AppID 0, ActionID 13] : LaunchApp changed task to Completed with ""
ERROR: ld.so: object '/home/andrew/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/andrew/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/andrew/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/andrew/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
>>> Adding process 24923 for game ID 33554432
Proton: Missing or invalid openvrpaths.vrpath file! [Errno 2] No such file or directory: '/home/andrew/.config/openvr/openvrpaths.vrpath'
ERROR: ld.so: object '/home/andrew/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
>>> Adding process 24924 for game ID 33554432

Apart from the preparing to launch dialogue window, that is shown very briefly, nothing happens.
The LD_PRELOAD errors aren't causing this because I get that for every game, I have added and executed other exe's successfully.

[EDIT] Log file: http://dpaste.com/30QJMBS
[EDIT2] Fixed the target variable which apparently does not set correctly if there are spaces in the path, which unfortunately windows does a lot :( new log: http://dpaste.com/0BZ131M
Now I get a dialogue box saying that ACU can't find "Ubisoft Game Launcher" when running ACU.exe, running Uplay.exe still gives me nothing, not even a log.

[EDIT3] Never mind, fixed it, apparently when there are whitespaces in the path you not only need to fix the "Target:" variable but also clear the "Set Launch Options" box because that is where the remainder of the path goes :/

this is my crash for assassin creed unity in game, i only can play 2 minutes before crash https://gist.github.com/jomarocas/4db22c2e360ae045f73291c01423e484

Hi in the latest proton 5.0.4 i try to play the game erase the compat data and no working previous version 5.01 i can play this game

The game crashes at the splash screen. Similarly, Black Flag ( https://github.com/ValveSoftware/Proton/issues/1733 ) freezes at the splash screen. with the same error. This happens with both with DXVK and without. The only error in the log is:

ERROR: Could Not Get Primary Adapter Handle

I also tried all AMD vulkan drivers:

• vulkan-amdgpu-pro 20.30_1109583-1
• amdvlk 2020.Q3.6-1
• vulkan-radeon 20.1.8-1

But all return the same error as above.

Kernel version: 5.8.10-arch1-1
Proton version: 5.0.9-6
DXVK version: 1.7.1-1
CPU/GPU: AMD Ryzen 5 4500U

I have troubles with AC:U activation. Steam launches Uplay, it asks me to login and then shows me "enter the activation code" screen, which I obviously don't have and here I'm stuck.

Steam support denied refudn and redirected me to ubi support, then ubi said they don't support proton and redirected me back to steam and at the end steam support redirected me here.

IIRC the activation code is available in the steam overlay. That said I worked fine for me without manual activation.

@Holzhaus welp, no overlay, cuz game isn't launched and required manual activation

@Holzhaus welp, no overlay, cuz game isn't launched and required manual activation

https://support.ubisoft.com/en-US/Article/000076555

@Holzhaus unfortunetaly there is no "CD keys" under "manage".

It seems like some recent update broke the game. With DXVK, it hangs after a few seconds, using both radv and amdvlk. File integrity is good, and it works mostly using WineD3D, but there seem to be some graphical issues when SSAO is enabled.
I've put the dxvk logs here and the proton log here

Do someone also experience LOD problems? Textures looks very bad and it do not load the graphics properly. Some areas looking like N64 graphics. Bought and running through steam.
Running the game with Proton 8.0-5 and gamemode and mangohud.
The game in general runs smooth with 1440px x 144Hz (32GB RAM @ 6000 MHz, Ryzen 9 7950X3D and Radeon RX 6950 XT - game and OS - LM 21.2 with Cinnamon, Kernel 6.5.0-21 and kisak Mesa 24.0.2 - are stored on nvme).
I did put TearFree and VariableRefresh options true in amdgpu.conf which seems to work (like my Xorg.0.log is telling me).

Stuck at splash screen

I am unable to play this game, the Ubisoft Connect launcher shows up, asks for my password, syncs the save files, and I'm met with this splash screen, I left it there for an hour once and nothing changed so I don't think it is loading anything.

Screenshot

And it's stuck there indefinitely.

Proton logs

steam-289650.log

Steam Runtime Diagnostics

https://gist.github.com/yoyossef/8936e0a165a9a49c1544d83b76a47d0d

Hello @kisak-valve I've updated the report to include the Steam Runtime Diagnostics gist.

@kisak-valve Downgrading Proton back to 8.0-5 fixes it, the game launches under that version, once every two launches (both time the splash screen bug is out, but only once every two launches the game window shows up after the splash disappears). So not perfect but it works.

Currently with Proton Experimental and the default configuration there seems to be a bug where setting the game to borderless windowed makes it appear like this.

This is my system information (AMD CPU, GPU, Fedora Linux 42, KDE 6.4.5)

steam.txt

and the proton log

steam-289650.log

If you require any additional information please ask.

Coop is not playable on proton experimental, it gives a ubisoft connection error