Compatibility Report

I tried trick from Uncharted 4: WINEDLLOVERRIDES="amd_ags_x64.dll=b" %command%, it helps with driver version error, but after splash screen - C2D.
Amd RX6700XT, Arch Linux, Linux 6.3.8, Mesa 23.1.2, ProtonGE-8_4
steam-2383670.log

Can it be affected by #6859? I will try today with proton 7 and report here
Still C2D

I have the same problem, it won't let me go because of outdated drivers. korsilyn, I also tried what you sent and it didn't help, it caused my system to freeze and steam shut down due to exceeding the RAM limit. I'm curious who will be able to solve it because there is zero hope that this game will work. I run the game in the fedora system, the GPU I use is AMD RX570, the drivers are original open source, I do not use drivers from the AMD website

Same here. WINEDLLOVERRIDES="amd_ags_x64.dll=b" %command% helps with driver version error ether, but game crashes imidiate after window opens.

AMD RX5700xt, Ubuntu 22.04, Linux 6.0.9, Mesa 23.1.2, GE-Proton8-4
UPD: GPU is external. GPU box - Razer Core X Chroma. Full "Launch options" line: "PROTON_LOG=1 DXVK_FILTER_DEVICE_NAME=AMD WINEDLLOVERRIDES="amd_ags_x64.dll=b" %command%"
steam-2379390.log

Starts and plays on my end. I'm on Nvidia. There is an extreme amount of lag that isn't present with Windows, though. Consistent with Rainbow Six Siege on Vulkan, but DX11 isn't offered in Extraction as a backup option. BattlEye doesn't seem to be kicking (on Steam at least, does on Ubisoft Connect except for solo incursions) but my testing was brief.

That should hopefully work OOTB on AMD now on the current Proton Experimental [bleeding-edge] branch. Not sure that it is the case across all possible configuration and Mesa versions, but seems fine on RX6800M / Mesa 23.1.5 and Deck.

Apologies to necro this, but this seems to have been changed after an update. Based upon personal experience and ProtonDB's records, this was altered within the last 2 years, and has become a universal incompatibility with NVidia products... I'm rather new to linux, so I'm still learning, but I cannot find any logs from it through lutris OR steam outside of the launcher logs, which don't actually detail anything.

Regardless, details to the error go as such. The game can install and boot to Ubisoft Connect flawlessly, launching the game's little pre-render flag before closing that and opening the main game. Upon the main game's launch, the main game will play through the entire introductory cutscene as long as it is minimized, but as soon as it is no longer minimized, it will crash without a warning and before displaying the first visual. I cannot detail to you how I have been able to launch the game in a minimized state, I just know that I have been able to somehow and can reproduce it with minor difficulty. As mentioned before, I have not been able to find a log for this crash anywhere outside of the launcher logs, which simply detail that the game with the process id has been disconnected as soon as it enters a non-minimized state.

My computers specifications stand as such.

OS: Linux Mint 22.3

KERNEL: 7.0.0-30-generic

CPU: Intel Core i7-7700K @ 4.20GHz

GPU: NVIDIA GeForce RTX 2070 SUPER

GPU DRIVER: NVIDIA 595.91.07

RAM: 64 GB

OK, here's the proton log, I apologise, I had no idea how to find this originally
steam-2383670.log

and the Gist link to my runtime diagnostics
https://gist.github.com/AnomalousHendo/3db409eb08904a1dfbafc6bc83487a07

Thank you and sorry for the necro again.

can do, as to why it's the demo at the moment, I have the whole game on Ubisoft connect and am just trying to launch the demo to see how it'll consider it as I owned it on Ubisoft connect before it was on steam, though from how it's been behaving, it does seem to be trying to go through the whole game ubisoft side... regardless, a fix I can apply to steam, I can figure a way to apply to ubisoft connect at a later point.

Unfortunately still a crash off rip, Log here

steam-2383670.log

@kisak-valve In both logs the game appears to be dying due to

warn:seh:handle_syscall_fault backtrace: --- Exception 0xc0000005 at 0x7c0bfff40b1d: /mnt/F0F00E15F00DE2A8/Steam games/steamapps/common/Proton - Experimental/files/lib/wine/x86_64-unix/win32u.so + 0x140b1d.
warn:seh:dwarf_virtual_unwind backtrace: 0x7c0bfff40b1d: /mnt/F0F00E15F00DE2A8/Steam games/steamapps/common/Proton - Experimental/files/lib/wine/x86_64-unix/win32u.so + 0x140b1d.
warn:seh:dwarf_virtual_unwind backtrace: 0x7c0bffd63ac1: /mnt/F0F00E15F00DE2A8/Steam games/steamapps/common/Proton - Experimental/files/lib/wine/x86_64-unix/winevulkan.so + 0x31ac1.
warn:seh:dump_syscall_fault backtrace: __wine_unix_call_dispatcher.
warn:seh:dump_syscall_fault backtrace: returning to user mode ip=00006ffffd76a969 ret=c0000005
err:vulkan:vkAcquireNextImageKHR Exception 0xc0000005 in Unix call.

I suspect it's something for Wine people to look at, a segfault in win32u.so is probably not something expected to happen…

Ok, so, is there a place I can report this to the wine lads?
Additionally, I also might have an alternate solution for lutris on reddit, though I haven't had the chance to trial it yet.
Regardless, if I can get a fix for both lutris and steam, I'd call that a win

so, someone else I've been talking to for help fixing this is telling me this is an X11 problem and that it's not present on wayland... might this feasibly be the case?

Perhaps xwayland could help, yes. Or winewayland driver from one of downstream Proton forks. WSI stuff is somewhat sensitive to this.

I think the log with exact location of the crash should be good enough of a start, it's now just a matter of time until someone takes a look at it. We could then reassess if dxvk-nvapi needs any fixes for this game, though I doubt it does.

Gotcha gotcha, so it's just a waiting game for the time being?

As said, I don't know where to actually report this, is this something you lads have handed in? or do I need to hand it in? and if I were to, would it be to the wine gitlabs?