search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.49k stars 1.07k forks source link

Assassin's Creed Odyssey (812140) #1757

Open matty-r opened 6 years ago

matty-r commented 6 years ago

Compatibility Report

System Information

I confirm:

Log File

(Too Large to paste here) Log File

Symptoms

Uplay will launch and update, after update Uplay will report "Connection Lost, A ubisoft service is currently unavailable. You can try again later or switch to offline mode". Offline mode will not work as it's required to login atleast once before offline mode is allowed.

Reproduction

Start the Game without any additional launch options.

shadywack commented 4 years ago

please @Dimitrov1295 read i find before post any new github, exist information in https://www.protondb.com/app/812140 or simple do this

first launch of uplay for driver support, erase folder compatdata and first time launch disable all messages from uplay, first launch of the game disable steam key with ctrl+alt+tab, later you can make this

WINEPREFIX=(Steam-folder)/steamapps/compatdata/812140/pfx/ winecf

Later enable virtual desktop and you put you monitor resolution, later edit with gedit in my case the following file

gedit (Steam-folder)/steamapps/compatdata/812140/pfx/drive_c/users/steamuser/My Documents/Assassin's Creed Odyssey/ACOdyssey.ini

FullscreenWidth=1920 FullscreenHeight=1080

*winecfg winecf doesn't exist

nonchip commented 4 years ago

I'm on 5.9-GE-5-ST and can confirm it fixes most of the issues brought up in this thread, but i'm experiencing another issue (with both "official" proton and the GE version): random freezing (completely, doesn't render any more frames, handle any input, or play any SFX, though the background music sometimes keeps playing) every about half to 2 hours or so, usually right before i do something important, really annoying. only thing i can do is kill the exe, manually close uplay, and restart the game from steam.

currently trying to get some useful debug info on it and will edit this post if i figure anything out EDIT: after 2 hours it did it again, this time with debugging, log file is attached: steam-812140.log I've also noticed the following popping up in dmesg most of the time it freezes/crashes (and never seen that before, sounds like a segfault in video ram or something like that):

NVRM: Xid (PCI:0000:08:00): 31, pid=12170, Ch 0000004e, intr 10000000. MMU Fault: ENGINE GRAPHICS GPCCLIENT_T1_4 faulted @ 0x0_00000000. Fault is of type FAULT_PDE ACCESS_TYPE_READ

(didn't confirm exactly, but that PID looks to be in the range the game could've been in at that time)

DMGPage commented 4 years ago

Just for information, but Proton 5.9 GE8 ST did not work for me. Yes, first time it launched fine with correct resolution, but crashed after first cut scenes, and then started to behave strange. Game did not launch at all and sometimes changed my desktop resolution to wrong size. Sometimes freeze completely. Only Proton 5.9 with virtual desktop helps to launch game without issues. But sometimes sound is still missing in cut scenes.

haraldkrischner commented 4 years ago

As I just bought a new monitor with UWQHD = 3440x1440 at 144Hz this game is a great experience. When I change the settings in a running game it works just fine. But when saved at these settings and I want to start the game it crashes my whole gnome session when the health warnings get displayed at startup. I'd love to add more log information if one could give me a hint where to find it. A quick glance at AC Origins showed the same behaviour.

Tested with Proton 5.13-1

hakzsam commented 4 years ago

For RADV users: Do you still have issues with that game and Mesa 20.2.x ?

nikspyratos commented 4 years ago

Proton 5.13 gives "Unable to detect uplay" errors for Origins and Odyssey for me. Switching back to 5.0-9 now gets me as far as the game launching overlay, but disappears immediately after. Not sure if this is also related to the recent uplay update where it is also now called Ubisoft Connect?

I'm on Mint 20. Gist is here

kakra commented 4 years ago

I also can no longer start AC:Odyssey... It used to run with Proton 5.9-GE versions, and I didn't play it in a while so I'm unable to pinpoint what is causing the problem. I switched to 5.13 today before starting the game. Interestingly, switching back to 5.9-GE doesn't help so there's probably some other issue. It seems to crash with an exception, maybe similar to @nikolaos-spyratos issue?

I'm not sure if the update to Ubisoft Connect is the problem here. I tried AC:Origins instead and it does run with 5.13.

steam-812140.log

Steam system info: https://gist.github.com/kakra/97e58ca288767401a70b35613d9e0e7e

nikspyratos commented 4 years ago

@kakra I ruled out the ubi connect update I think. Similarly to my GTA V comment I switched to 5.9-GE, but the game will only launch at all if I use PROTON_USE_WINED3D=1 in the launch options. Which of course breaks all the graphics (everything is black except some world geometry, character model doesn't load). The behaviour visually is the same for both 5.9-GE and 5.13: Ubisoft Connect does its thing, game launch overlay starts, dies, have to close game via steam. Difference being the log with 5.13 is massive at 35MB.

5.9-GE log Partial 5.13 log - Full one times out on upload.

System info:

At this point considering people are having issues across many Proton versions no matter what they do, I'm assuming this is more due to the recent runtime update (Soldier) and the containerisation. But that's delving into things I now nothing of so can't really comment further.

Vash63 commented 4 years ago

For people having issues with Ubi, have you tried deleting the pfx directory? I generally have to delete that whenever switching Proton versions (either up or down) for Ubisoft games. I haven't tested Odyssey in a while though as I deleted it when I completed the game to save disk space, but I did have this issue when toggling between 5.0 and the 4.x branches with Uplay.

nikspyratos commented 4 years ago

@Vash63 Anecdotally, I've done that several times, doesn't help in this case for me at least. I reinstalled the game completely too. That's why after this and other workaround attempts I think this is more related to the runtime update.

EDIT: Seeing from the last post on this the new issues will be tracked in the steam runtime repo.

viggy96 commented 3 years ago

I can no longer start the game. The game window doesn't open, it just gets stuck on the splash screen. When I click on the button in the dock, the game's window is completely black. I've tried with both Proton 5.13, and with GloriousEggroll 5.21. I've also verified file integrity, and reinstalled the game twice. I used to be able to run the game just fine with both Proton 5.13 and GloriousEggroll.

steam-812140.log

kisak-valve commented 3 years ago

Hello @viggy96, looks like a vkBasalt issue. From the log:

vkBasalt err:   failed to load shader file: 
vkBasalt err:   Does the filepath exist and does it not include spaces?

There might be a Steam Linux Runtime - Soldier issue happening since Vulkan layer support recently got wired into it. Please open a new issue report in the steam-runtime issue tracker focusing on vkbasalt's behavior.

viggy96 commented 3 years ago

@kisak-valve You're right it was a vkBasalt issue. I disabled it, and the game works just fine. Sorry for wasting your time. I learned today that vkBasalt is very annoying, haha.

pklampros commented 3 years ago

@nikolaos-spyratos I had exactly the same problems as you describe. However 5.13-2 finally works perfectly, and the only thing I had to do was to move Proton to reside in my home directory (uninstall, reinstall) and not the additional NTFS drive where I store my games library.

hakzsam commented 3 years ago

Do you still experiment issues with RADV?

kisak-valve commented 3 years ago

Tracking note: Mesa / RADV labels dropped due to lack of driver-specific feedback.

viggy96 commented 3 years ago

Is anyone else having issues with Ubisoft Connect not remembering the Ubisoft account login? I'm having to login every time I want to play the game.

vadi2 commented 3 years ago

Yes, same for me as of recently.

kakra commented 3 years ago

Maybe related: I do not see the issue of having to login over and over again (I was seeing that back in Proton 5.0 or earlier) but when Ubisoft Connect tries to auto update itself, it just sits there and does nothing but running the spinner animation. If I run the Uplay launcher manually by using protontricks to install Uplay, it will complain about the launcher being newer than what it tries to install, then launches the Uplay launcher which then updates itself just fine. After this, Ubisoft Connect will no longer try to update itself for some days and games launch just fine.

steam-812140.log

lox-enterprises commented 3 years ago

Is anyone else having issues with Ubisoft Connect not remembering the Ubisoft account login? I'm having to login every time I want to play the game.

Yes, same here, since the last time Ubisoft Connect updated itself. I've tried deleting the pfx folder in order to let everything be rebuilt, but that didn't solve it.

kakra commented 3 years ago

I can now confirm that the launcher no longer remembers my login but it remembers the two-factor validation and won't ask for it again. The last change I did to my system and Steam that I remember was updating the Steam runtime and soldier runtime to beta. Proton Experimental wasn't updated in the meanwhile as far as I can tell. This behavior has changed since my last comment.

sebastiencaty commented 3 years ago

Proton 6.3-2 works well, but Proton Experimental (experimental-6.3-20210423) always end with :

image

Re-installed from a clean pfx did not help. Downgrading back to 6.3-2 works.

Update: It decided to work, guess it's a ubi thing

viggy96 commented 3 years ago

One thing I've noticed is that fsync/esync prevents UPlay from updating. So I temporarily disable fsync/esync using the flags (PROTON_NO_FSYNC=1, PROTON_NO_ESYNC=1), launch the game, exit, then remove those flags.

kakra commented 3 years ago

Maybe the uplay launcher needs the same esync/fsync hack in the wine code as the game exe itself?

kisak-valve commented 3 years ago

Assassins creed odyssey

Issue transferred from https://github.com/ValveSoftware/Proton/issues/4998. @killown posted on 2021-07-23T13:05:19:

Compatibility Report

System Information

I confirm:

<Proton log omitted by moderator, please see #4998>

Symptoms

uplay not launching

Reproduction

hit play button or try proton run with compatdata and wineprefix vars wont work in both cases

@killown commented on 2021-07-23T13:07:30:

Game was working for weeks until this happened randomly, same setup, no updates, assassins creed origins working well, that means the uplay from AC origins is working, I tried to remove the compatdata from AC odyssey and start a fresh one and still the same issue no matter what version of proton is used.

matty-r commented 3 years ago

Tried initially using Proton Experimental - would show the Uplay launching and was stuck on "Looking for Patches", killed the process and switched to Proton 5.13-6. This got me passed the previous point and brought me to a login screen for Ubisoft Connect, killed the process and switched back to Proton Experimental, this go through to the game without having to login to Ubisoft and the game ran well.

Opening Steam Overlay with Proton Experimental would lock up the game and requires killing the process.

class101 commented 3 years ago

One thing I've noticed is that fsync/esync prevents Ubisoft Connect from updating. So I temporarily disable fsync/esync using the flags (PROTON_NO_FSYNC=1, PROTON_NO_ESYNC=1), launch the game, exit, then remove those flags.

@viggy96

I don't know how you figured out that but thanks a lot.

I received an update immediately after testing this on a fsync enabled kernel-5.13.13-zen1-1-zen and Arch Linux

Other than that, I'm trying to figure out if anybody got a freeze while playing the game ? From time to time, the game just freezes, sometimes the sound still works but nothing is responsive, no error entries in the proton log too.

I'm currently testing to catch up an error in DXVK set to debug but no luck to reproduce yet, will update if I find anything better.

Maybe it was connected to the Uplay not updating as @viggy96 reported. Unsure yet.

Edit: Could be nvidia driver related, using the 470.63.01 version and DXVK_LOG_LEVEL=debug, I get the following entry at the end of the log file

debug: Compiling graphics pipeline...
debug:   vs  : VS_75e30600a7b972faa31dab7baad3b6840839ae2a
debug:   vs  : VS_75e30600a7b972faa31dab7baad3b6840839ae2a
debug:   fs  : FS_7aa347856f32c52978fe8f404070b1fa8e9030c5
debug:   attr 0 : location 0, binding 0, format VK_FORMAT_R32_UINT, offset 0
debug:   fs  : FS_0a01b66c3f0db3fc5d374d86c7cb2f042fa0c1cc
debug:   attr 0 : location 0, binding 0, format VK_FORMAT_R32_UINT, offset 0
debug:   binding 0 : binding 0, stride 4, rate 1, divisor 1
debug:   binding 0 : binding 0, stride 4, rate 1, divisor 1
debug: DxvkGraphicsPipeline: Finished in 10 ms
debug: DxvkGraphicsPipeline: Finished in 13 ms
debug: DxvkGraphicsPipeline: Finished in 10 ms
debug: DxvkGraphicsPipeline: Finished in 11 ms
err:   DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST
err:   DxvkDevice: waitForIdle: Operation failed
err:   DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST
err:   DxvkDevice: waitForIdle: Operation failed
err:   DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST
err:   DxvkDevice: waitForIdle: Operation failed
err:   DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST
err:   DxvkDevice: waitForIdle: Operation failed
err:   DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST
err:   DxvkDevice: waitForIdle: Operation failed
err:   DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST
err:   DxvkDevice: waitForIdle: Operation failed
err:   DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST
err:   DxvkDevice: waitForIdle: Operation failed
err:   DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST
err:   DxvkDevice: waitForIdle: Operation failed
err:   DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST
err:   DxvkDevice: waitForIdle: Operation failed
err:   DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST
err:   DxvkDevice: waitForIdle: Operation failed
err:   DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST
err:   DxvkDevice: waitForIdle: Operation failed
err:   DxvkSubmissionQueue: Command submission failed: VK_ERROR_DEVICE_LOST

Edit2: Testing know with fsync disabled, no crash yet, finger crossed, nope still crashing

kakra commented 3 years ago

I don't know how you figured out that but thanks a lot.

In my tests, it usually didn't help the update problem. I found that starting uplay just often enough will eventually make it get past the update check and start the download. With fsync off, it's just more likely to get past that point but it may still get stuck. So there's probably some other problem hiding somewhere else. What really helps is using protontricks to launch the uplay installer from there (and it will run with fsync because fsync defaults to on since some Proton version): it will try to update uplay, then complain about a newer version already installed and asks if I want to restart uplay, confirm yes, and it will run the installed uplay launcher which then updates just fine. So it's probably more likely that a delayed launch of uplay has a higher chance of passing the update check. So the culprit is probably somewhere in the early boot phase of wine. With fsync disabled, internal wine boot may just do some things slow enough for uplay to launch at a different time and get around some race condition.

class101 commented 3 years ago

I initially thought it was just about fsync but forgot I was also disabling esync in order to always replace it for fsync.

So I'm unsure yet if, for the uplay update issue, only fsync is to disable, or fsync + esync

About the freeze issue, I read on ProtonDB that someone worked around by also disabling fsync + esync, so it is possible both issues are connected, I'm actually trying that and will update nope it still freezes :(

Edit: I think it is connected to this issue https://github.com/doitsujin/dxvk/issues/1799 will report there instead

bojanivanovic commented 2 years ago

Hi, seems like 6.3.8 has a regression tied to Odyssey. It's the issue that's described in https://github.com/ValveSoftware/Proton/issues/1757#issuecomment-910227623 (except that I'm on AMD). The game runs well until, about 10min in, assets start failing to load and then the game just freezes with the "loading" icon bottom left. There's still sound and I can control the camera, but that's about it. It worked fine in 6.3.7, never once crashed.

Not sure which logs/info to provide here but I'll post whatever needed.

kisak-valve commented 2 years ago

Hello @bojanivanovic, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, 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.

bojanivanovic commented 2 years ago

Thx @kisak-valve. Here's the game's log:

steam-812140.log

and here's system info:

https://gist.github.com/bojanivanovic/7319818039e58292e5549d328620d254

alasky17 commented 2 years ago

@bojanivanovic Could you try dropping in the dxvk version from 6.3-7 to see if that is the source of the regression? You can download the tar from here: https://github.com/doitsujin/dxvk/releases/tag/v1.9.2 and drop the x32 files into ~/.steam/steam/steamapps/common/Proton\ 6.3/dist/lib/wine/dxvk/. and the x64 files into dist/lib64/wine/dxvk.

To restore the version of dxvk that shipped with 6.3-8, you can just delete the whole dist folder and it will recreate itself.

bojanivanovic commented 2 years ago

@alasky17 same issue with that DXVK ver.

Edit: so after trying with those files and it crashing, I deleted the dist dir, restarted Steam and reran the game and now it seems it's working. I guess it might have been an issue with one of the updates or a corrupt file in dist. Thanks so much for your help @alasky17 and @kisak-valve. Will post if it does continue to break, but I've played about 15min of it now and it didn't crash (used to crash withing the first few min every time before).

alasky17 commented 2 years ago

@bojanivanovic Yay!! I'm glad you figured it out - thank you for updating us :)

rcrit commented 2 years ago

Big (8.4GB) update today, Dec 14, seems to have broken audio. The seizure warning video is now gone (probably not related, but unexpected). Audio plays during the Ubisoft and AMD videos but once the AC: Odyssey screen is displayed sound is gone. Within the game there are some sounds, like breathing/grunting and the occasional environmental sound. Some dialog has audio but not very much.

rcrit commented 2 years ago

Another 3.3GB download later and things are back to normal. I guess it was an issue with the game patch.

hasezoey commented 2 years ago

This game worked fine on the first day, but then didnt want to start anymore over SSHFS (BTRFS in the server-side)

Issue encountered: Game crashes on splashscreen and intro sequences and does not get to the title-screen when using SSHFS (on manjaro), but it worked once

Proton Versions tried:

Also tried with options:

System: Manjaro Linux 21.2.1 with KDE Plasma Wayland and Pipewire sshfs versions:

SSHFS version 3.7.2
FUSE library version 3.10.5
using FUSE kernel interface version 7.31
fusermount3 version: 3.10.5

kernel: 5.15.12-1-MANJARO

Proton Log with Proton Experimental

Workaround for now is to move it to a local BTRFS drive and start it from there

ptkato commented 2 years ago

I managed to book 200+ hours in the game, and I noticed a strange behaviour: the game always freezes (requiring to manually kill it) when something overlays it; things like the steam overlay, or a notification popup from a desktop environment freeze the game instantly, however the game's background music keeps playing just fine.

kakra commented 2 years ago

Since one of the more recent Proton Experimental updates, AC:O does no longer boot, it just hangs there. An interesting observation: If I force the re-installation of the uplay launcher via protontricks (which will be refused because a newer version is already installed), it just works. Other Uplay titles seem to be affected as well.

steam-812140.log

kisak-valve commented 2 years ago

Assassins Creed Odyssey(812140): FPS problem

Issue transferred from https://github.com/ValveSoftware/Proton/issues/5780. @k3ssl0sh4y posted on 2022-04-22T12:56:20:

Compatibility Report

System Information

I confirm:

steam-812140.log

Symptoms

I run the game and it drops to 90-1 FPS. This is an instant drop to 1 and back to 90. I can run the game on low, medium and high, but the frames are inconsistent. The image below shows the problem image

Reproduction

it's during the game

kakra commented 2 years ago

I run the game and it drops to 90-1 FPS.

This may be an issue with adaptive quality and auto vsync. I've seen similar problems when I enabled those. Somehow, Proton does not like how the game is switching render modes with adaptive vsync (it usually works in other games just fine but this engine seems special as it also switches anti aliasing during adaptive adjustments which may be the problem here).

k3ssl0sh4y commented 2 years ago

Thanks for answer @kakra. I disabled those options and i set "PROTON_NO_FSYNC=1, PROTON_NO_ESYNC=1" in options to launch, but the problem persists.

kakra commented 2 years ago

and i set "PROTON_NO_FSYNC=1, PROTON_NO_ESYNC=1" in options to launch

If you actually used a comma, don't use that, options are set space-delimited: PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1 %command% - otherwise it might not work as intended.

k3ssl0sh4y commented 2 years ago

I can reach a maximum of 370fps, but instant drop to 1-5 fps and very inconsistent ... i go to use Proton-7.0rc6-GE-1 for now.

ElricleNecro commented 2 years ago

I cannot launch the game anymore. It crash (uplay actually) with

info:  Game: upc.exe
info:  DXVK: v1.10.1
info:  Built-in extension providers:
info:    Win32 WSI
info:    OpenVR
info:    OpenXR
info:  Enabled instance extensions:
info:    VK_KHR_get_surface_capabilities2
info:    VK_KHR_surface
info:    VK_KHR_win32_surface
2880.155:0150:0154:err:vulkan:__wine_create_vk_instance_with_callback Failed to create instance, res=-1
2880.163:0150:0154:trace:seh:raise (22)
terminate called after throwing an instance of 'dxvk::DxvkError'

Here are the complete logs: steam-812140.log

I've already played this game on another computer, and it was working. Other game usng Vulkan (Dota 2, Red Dead Redemption 2, Cyberpunk 2077, ...) are working, so I don't this this is a problem with the vulkan installation.

System Information

kisak-valve commented 2 years ago

Hello @ElricleNecro, 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.

ElricleNecro commented 2 years ago

Hello @ElricleNecro, 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.

I've added the report!

kisak-valve commented 2 years ago

Thanks, looking at your system information, it looks like the 32 bit Vulkan render path is broken. Can you check if you have the lib32-amdvlk package installed and if removing it has an effect? We've seen this driver break other video drivers when there isn't an AMD video card installed.

ElricleNecro commented 2 years ago

Thanks, looking at your system information, it looks like the 32 bit Vulkan render path is broken. Can you check if you have the lib32-amdvlk package installed and if removing it has an effect? We've seen this driver break other video drivers when there isn't an AMD video card installed.

Thanks, that's fixed it !