Aliens: Fireteam Elite (1549970)

[NTMan]

Compatibility Report

• Name of the game with compatibility issues: Aliens: Fireteam Elite
• Steam AppID of the game: 1549970

System Information

• GPU: Radeon 6900XT
• Driver/LLVM version: Mesa 20.3.0/13.0.0-rc1
• Kernel version: 5.14-rc6
• Link to full system information report: Gist
• Proton version: experimental-6.3-20210823

I confirm:

• [x] that I haven't found an existing compatibility report for this game.
• [x] that I have checked whether there are updates for my system available.

steam-1549970.log

Symptoms

The game crashes after splash screen:

Reproduction

Always.

[kisak-valve]

Hello @NTMan, there's a decent chance you're seeing the same video driver issue here as https://github.com/ValveSoftware/Proton/issues/4811#issuecomment-903467721 with /usr/include/c++/11/array:188: std::array<_Tp, _Nm>::value_type& std::array<_Tp, _Nm>::operator[](std::array<_Tp, _Nm>::size_type) [with _Tp = aco::{anonymous}::Idx; long unsigned int _Nm = 512; std::array<_Tp, _Nm>::reference = aco::{anonymous}::Idx&; std::array<_Tp, _Nm>::size_type = long unsigned int]: Assertion '__n < this->size()' failed. in your log. You might be able to avoid the assertion by using a non-debug build of mesa, but that would just hide the issue at best, not fix it.

As a side note, please stop claiming that a random git build of mesa ~is an unreleased point release (mesa 20.3.0 does not exist yet)~ EDIT: 20.3.0 is factually wrong, but so is my claim that it's unreleased. It's additional misleading noise that you just as well could directly say what git commit you're using.

[NTMan]

EDIT: 20.3.0 is factually wrong, but so is my claim that it's unreleased. It's additional misleading noise that you just as well could directly say what git commit you're using.

I always make mesa version clickable, so that you can easily understand from which commit the mesa was built if you click on version number.

Also I bisected the issue and fill mesa bugreport: https://gitlab.freedesktop.org/mesa/mesa/-/issues/5289

[toter200]

There are 3 reports on protondb stating that the game works flawless. For me running the game through proton with no additional parameters does not work. I tried: running on wayland running on xorg with older proton verisons (5.13 and later) running with 6.3, expermental and GloriousEggrolls proton versions results in the game being stuck before the splashscreen apears, it doesnt crash nor load or start loading steam-1549970.log

running the game with wined3d, the game loads in and works although with a lot of graphical glitches and very poor performance (15-30 fps)

GPU: 5700XT Kernel version: 5.13.11 Mesa version: 21.1.6

[kisak-valve]

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

[toter200]

Oh sorry i forgot gist

[kisak-valve]

Thanks, the lack of DXVK references in the Proton log like @NTMan's log made me suspect that there was a non-functional render path, but your system looks healthy in the linked gist.

If the game is using the CPU while it is not rendering, then it might be worthwhile to let it run for a while and see if it just needs some time to start up.

[toter200]

Interesting, i booted up the game to check the cpu load without wined3d and the game just worked. I ran around a bit to check for any artifacts but all was fine with 80 - 150 fps. I had gamemoderun as a command as well. After removing gamemode the game went back to being stuck, re-enableing it didnt fix it While being stuck the cpu is not really idling but no core went above 50% load. Memoryusage stays the same as well. I left the game running for like 25 minutes and nothing happened

[abienz]

Hi I have a separate issue with this game (and Steam) and I'm not sure this is the right place to put it, but here goes...

I've had the game since launch and it's been running very well for me on my System.

However, sometimes a large patch (about 1.5GB) is released and the game will get stuck in the installing phase after the patch has downloaded.

During this time my CPU goes through the roof, and my system becomes unresponsive, if I can get System Monitor to open I can see that the Steam process is the one with the CPU spike, if I shutdown/reboot my machine, I get caught in a terminal screen showing that the system is waiting for threads to close before shutdown.

I have tried the following:

• Changing download location
• Clearing download cache
• Verifying integrity of files
• Renaming game folder, 'uninstalling' the game through steam, renaming the game folder back to its original state, and installing again.

Nothing works, except genuinely uninstalling the game and reinstalling it, but this is waste of bandwidth, time and I also lose my game progress as Steam Cloud doesn't seem to reload my saves properly and instead overwrites them, but that's another issue.

Any ideas how I can resolve this issue?

[kisak-valve]

Tracking note: Dropping the Mesa / RADV labels because the error highlighted at https://github.com/ValveSoftware/Proton/issues/5114#issuecomment-904761403 should have been resolved by https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/12725.

[Corben78]

System Information

• GPU: RTX 3070
• Driver/LLVM version: nvidia 495.44
• Kernel version: 5.4.0-91-generic
• Link to full system information report as Gist
• Proton version: 6.3-8c

I confirm:

• [x] that I have found an existing compatibility report for this game.
• [x] that I have checked whether there are updates for my system available.

steam-1549970.zip (unzipped 114,3 MB)

Symptoms

When hosting a coop multiplayer session the game often crashes to desktop when a level loads. Didn't happen so far when joining a session and not hosting the session.

Reproduction

Invite 2 friends to the game, choose a level to play, join the queue, start the mission. Observe the game to just close in many cases.