Deathloop (1252330)

[OctarineSourcerer]

Compatibility Report

• Name of the game with compatibility issues: Deathloop
• Steam AppID of the game: 1252330

System Information

• GPU: GTX 2070S
• Driver/LLVM version: nvidia 470.63.01-7
• Kernel version: 5.14.2-arch1-2
• Link to full system information report as gist here
• Proton version: Proton Experimental (date 2021-09-14). Also would not launch with other proton versions used.

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.

Log:
steam-1252330.log

Symptoms

Hit play, no window appears. "Stop" button remains as "Stop" indefinitely.

Reproduction

Run game

[frozen-sea]

Just adding in another report, so you have more to work with. Symptoms are the same as OP.

System Information

• GPU: GTX 1080 Ti

• Driver/LLVM version: nvidia 470.57.02

• Kernel version: 5.13.16-xanmod1

• Link to full system information report as gist here

• Proton version: Proton Experimental (experimental-6.3-20210913)

Log:
steam-1252330.log

[Mr-Crabman]

Same symptoms as OP; the Deathloop.exe starts but there is no window, it just lingers at 1.2 GB RAM usage and does nothing:

System Information

• GPU: AMD Radeon RX 5600 XT

• Driver/LLVM version: 4.6 (Compatibility Profile) Mesa 21.0.3

• Kernel version: 5.11.0-34-generic

• Link to full system information report as gist here

• Proton version: Proton Experimental (experimental-6.3-20210913). Also tried 6.3-9c.

Logs:
steam-1252330.log (Experimental)
Pastebin of 6.3-9c log: https://pastebin.com/qxVridHE

[BenFradella]

Same here:

System Information

• GPU: RX 6900 XT
• Driver/LLVM version: mesa 21.2.1-1
• Kernel version: 5.14.3-arch1-1
• Link to full system information report as Gist:
• Proton version: Tried with experimantal-6.3-20210913 and 6.3-6

Logs:

• experimental: https://gist.github.com/BenFradella/08184cfb79234b012714f25e36e608cc
• 6.3-6: https://gist.github.com/BenFradella/ad14932da5a2cdbd70f764aa18ac4264

[AkharmLeOugre]

No window displayed has well and after one minute waiting i have this error message:

---------------------------------------------------------------------------
_DEATHLOOP ERROR

DEATHLOOP using VoldEngine 1.708.0.34 Sep 8
2021 10:47:07

Error 0xc000001D (Illegal Instruction) occurred in
thread 'DEATHLOOP' at instruction location
0x0000000141FDE2E1.

Callstack (BB575E3C)

0. 0x0000000141FDE2E1
+0x1FDE2E1

1. 0x0000000141FC90B8
+0x1FC90B8

2. 0x0000000141FCB26B
+0x1FCB26B

3, 0x0000000141FCB15B
+0x1FCB15B
4. 0x0000000140C10596

+0xC10596
5. 0x0000000140B97C69
+0xB97C69

6. 0x0000000140838487

+0xB38487

7, 0x0000000140838A80)
+0XB38A80

8. 0x0000000140B09C26

+0xB09C26

9. 0x000000007B62C8F9

+0x2C8F9
10. 0x000000007BC59873

+0x59873

Deathloop.exe

Deathloop.exe

Deathloop.exe

Deathloop.exe

Deathloop.exe

Deathloop.exe

Deathloop.exe

Deathloop.exe

Deathloop.exe

kernel32.dll

ntdll.dll

OS: Microsoft Windows 10 Build 17763
MEM: 1168.313 MB (used) 1221.766 MB (peak)
GPU: unknown
GPU drivers: unknown.

A full report and a crash dump were written to C:
users\steamuser\AppData\Local\Arkane Studios
(Deathloopbase\1.708.0.34120210915_133531)

For additional support please visit http://
help.bethesda.net/
-----------------------------------------------------------------------

System information:

OS: Pop!_OS 21.04
KERNEL: 5.11.0-7620-generic
CPU: Intel Core i7 940 @ 2.93GHz
GPU: NVIDIA NVIDIA GeForce GTX 1660
GPU DRIVER: NVIDIA 470.57.02
RAM: 8 GB

[kisak-valve]

Hello @AkharmLeOugre, looking around a little bit, apparently the current version of the game on Steam needs cpu support for AVX (unconfirmed) which your CPU does not support. That doesn't help troubleshoot the earlier feedback, just a note that you have an additional snafu with the game.

[Archivist062]

apparently the current version of the game on Steam needs cpu support for AVX (unconfirmed) which your CPU does not support

The game runs on my windows machine with a no AVX CPU so AVX is unlikely to be required

[benoit2600]

Deathloop need Windows 10 Build 18363 to run https://imgur.com/a/85biV3i.

Based on @AkharmLeOugre report, proton simulate Windows 10 Build 17763. It might be the problem ?

[NTMan]

With latest Proton Experimental 6.3-20210916 the Deathloop started working.

steam-1252330.zip

[elijahsgh]

I got excited after NTMan's comment and tried to start it. It now does something. I get a splash screen with a mouse cursor that is a watch. That's as far as I get. :(

[J4nsen]

The proton changelog mentions that it is only playable with RADV

[elijahsgh]

I left it doing nothing for a few minutes and it's up and running. Controller doesn't work. Frame rate seems great so far.

[NotTheEnclave]

Got excited since someone got it running. This is what im getting with proton experimental now after the update

[KGOrphanides]

Running on Proton Experimental, I've made it as far as a splash screen, which then just sits there until I stop the game from the Steam client.

Pop!_OS 21.04, kernel 5.13.0-7614-generic
AMD Ryzen 5 3600X 6-Core Processor
AMD Radeon RX Vega 64 (VEGA10, DRM 3.41.0, 5.13.0-7614-generic, LLVM 12.0.0)
4.6 (Compatibility Profile) Mesa 21.2.1 (kisak-mesa)
32GB RAM

Full system spec: https://gist.github.com/KGOrphanides/d4f4ad960f75515a86301394561f7a9b
Screenshot: https://theos-cloud.eu/index.php/s/ops7TjNACFRrWqy
Giant chuffing log: https://theos-cloud.eu/index.php/s/6Yxf3JHMiTf5CrY

[elijahsgh]

Leave it running for 5-10 minutes, @KGOrphanides

The progress bar will fill and you may even get Not Responding, Force Quit? but just leave it running.

[KGOrphanides]

@elijahsgh is correct, it launches after six minutes (I timed it) and we are in business.

Runs perfectly at detected settings (mouse and keyboard, haven't tested with a controller) and I successfully played the first loop. The game complained that I was using too much VRAM, but this was apparently because it thought I had 6GB rather 8GB. (Can provide screenshots if it would be helpful.)

Further notes:

• alt-tabbing out and back can result in a black screen
• on one attempt it froze while connecting to Bethesda.net (I have rural internet backed up by 4G, so I'm going to assume networking issues here)
• to avoid potential v-sync issues I used only my primary 100Hz 3440x1440 display

[piv-pav]

Can confirm: the game stucks during the first start for about 5 minutes and then runs normally., but in my case I saw few artifacts when borders of the objects has visible square regions around them. Probably will need to play with graphics settings in order to address that.

Arch @ 5.14.3-zen1
AMD Ryzen 7 5800X
AMD Radeon RX 6700XT
RAM 32Gb

[frozen-sea]

Getting exactly the same Access Violation as @NotTheEnclave screenshotted, takes less than a minute to pop up. Specs in my previous post.

steam-1252330.log
CrashReport.txt
Minidump.zip

[SR-dude]

OK, so what is the game doing during those 5-10 minutes? compiling shaders?

[elijahsgh]

OK, so what is the game doing during those 5-10 minutes? compiling shaders?

... probably Denuvo. This game features an anti-Tamper that decrypts assets during loads. Who knows.

[ivyl]

Small Proton Experimental update: the game should now be playable with Nvidia GPUs.

[santisteban]

I saw few artifacts when borders of the objects has visible square regions around them.

In my case it was Temporal Post-processing Anti-Aliasing that was causing the issue, setting it to High or lower fixed it.

@piv-pav

[thoughtorgan]

Got it running with experimental, played through the first level fine. Leaving the first area the game crashed with this error.

[CarnageDevs]

Getting the same error as @thoughtorgan in the exact same scenario: after beating the first area/tutorial, the error shows up in the loading screen for the 2nd area, Updaam.

I'm on an NVIDIA RTX 2080Ti if it matters, and upon starting the game again after it crashed with the error, I get the same error except it happens at the very start of the game now (as soon as the menu shows up)

EDIT: Upon a subsequent reboot, the game loads into the menu fine now and loads the 2nd area fine. Will update if it crashes again at the next area's loading screen.

[archangel013]

I'm running into the same problem as @benoit2600. The game launches on latest Proton Experimental, but doesn't make it to the splash screen. After the Preparing to launch... window goes away, the Windows version error pops up, and then a black screen - there is no splash screen for me - until I force quit it. I've left it running for 15+ minutes. Here are my logs.

System information: https://gist.github.com/archangel013/40d630f837d6557d2f5548fdf2ed9df3
Proton log: steam-1252330.log

[eaglemmoomin]

The game was patched today. It appears from two attempts to start it up since the patch that potentially it may now be borked for Proton Experimental at least on NVidia. Doesn't appear to be loading any more. I've had crashes previously (including the void engine one loading into Updaam) but that was actually in game or loading into a 'new' area. Or I'm just unlucky. Anyone else tried to run it since it was patched?

Nope just unlucky it started up on the fourth go. Other three goes no additional memory was allocated and no load was placed on any cores for some reason when I started the game.

[elijahsgh]

Are you on open beta or main? I'll give it a try but I want to make sure which release you're on. Also I'm AMD/AMD.

…

On Tue, Sep 21, 2021 at 1:32 PM eaglemmoomin ***@***.***> wrote: The game was patched today. It appears from two attempts to start it up since the patch that potentially it may now be borked for Proton Experimental at least on NVidia. Doesn't appear to be loading any more. I've had crashes previously but that was actually in game or loading into a 'new' area. Or I'm just unlucky. Anyone else tried to run it since it was patched? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5156 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA4CXQRT7QBXHJZHAE5DPJ3UDDFVNANCNFSM5D66F2XQ> .

[eaglemmoomin]

Replying to #5156 (comment)

Main. Haven't switched over to the beta.

[hakzsam]

If reverting it doesn't fix the issue, please explain how to easily reproduce the issue in-game (graphics settings and such), thanks!

[alosarjos]

Just tested on today's update. Yeah, reverting 1762e6b5406bf6c0ebec84a21fa8eb62f812dd2b as @hakzsam says, fixes the shadows. Should we make an issue on the Mesa gitlab?

[Etaash-mathamsetty]

Just tested on today's update. Yeah, reverting 1762e6b5406bf6c0ebec84a21fa8eb62f812dd2b as @hakzsam says, fixes the shadows. Should we make an issue on the Mesa gitlab?

yeah that seems like something reasonable to do

[hakzsam]

This RADV regression should be fixed in main. Please re-test and confirm, thanks!

[p0ryae]

Latest Mesa git (latest commit too) and Latest proton experimental (bleeding-edge), and the issue still exists:

[p0ryae]

As a side-note, I'd like to mention that the game runs fantastic ever since the latest update on PC. The frame time is very much consistent and the engine runs the game more matured then before. Other then the current shadow bug, everything else is perfect for me.

[kisak-valve]

Hello @DashCruft, for reference sake, what commit hash for mesa and date on Proton experimental. Just writing "latest" becomes difficult to evaluate after a relatively short amount of time.

[p0ryae]

Hello @DashCruft, for reference sake, what commit hash for mesa and date on Proton experimental. Just writing "latest" becomes difficult to evaluate after a relatively short amount of time.

Sorry I should've known. The latest commit on my mesa compile is f9dbb65e7feac3e5d8558e21b2a6a2928f3682b9

[hakzsam]

Someone else said the opposite https://gitlab.freedesktop.org/mesa/mesa/-/issues/7305 ? I'm wondering...

[hakzsam]

@alosarjos Are you sure the issue is fixed for you then?

[alosarjos]

In my case I could easily see this issue on the beginning of the first level and now is gone

This screenshot is with commit e7e989f62e9 + This MR for testing: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/18499

[alosarjos]

@DashCruft On your latest screenshot I see Mangohud reporting commit dcc52618952, you sure you tested recompiling after the fix merge?

[p0ryae]

huhhh. This is odd. Git must've did the funny (or I have). Going to recompile again the main mesa repo.

[p0ryae]

I accidentally didn't choose the right mesa version to test the game on. I can fully confirm this issue is now completely resolved by the new merge that occurred in the mesa-git repo recently. (https://gitlab.freedesktop.org/mesa/mesa/-/issues/7305)

I also apologize for the confusion that occurred.

[alosarjos]

@DashCruft That merge still hasn't occurred. But I see you are now on commit e7e989f6 from main which is pretty recent.

TLDR: The 18499 MR has nothing to do with this.

[p0ryae]

Sorry again 💀 mentioned the wrong PR. My bad.

[hakzsam]

Great, thanks for confirming, happy gaming!

[zerkerX]

I'm getting the following dialog:

Or, in text form, "DEATHLOOP Requires Windows 10 or higher".

On two different Debian machines, one running Debian testing (towards 12/Bookworm) with Radeon 5700 XT and the other on Debian Stable (11/Bullseye) with NVidia GTX 1070. Same result for both experimental and Proton 7.0.5. Not sure what I'm doing differently when it seems to be running fine for others.

[p0ryae]

Use protontricks to set the windows version to 10 (Select default prefix, then select winecfg)

It seems like your proton has defaulted to windows 7.

[zerkerX]

Thanks for the hint, but deleting the compatdata folder for the game was enough so that it was re-created. I think it had defaulted to a Proton version that created a Windows 7 prefix, and kept the Windows version when I upgraded the prefix.

Hopefully this is useful to someone else in the future.

[juampiursic]

Trying to play this game it's being a nightmare. It uses up all of my VRAM, I have a 3070 and I know it's not a lot of VRAM but still, takes up the 8GB of VRAM the GPU has. No matter I set the game on low or ultra, on low it takes a little more time to fill up the 8GB but still, it does.

And loadings make the game crash, throwing this errors:

[LethalManBoob]

Trying to play this game it's being a nightmare. It uses up all of my VRAM, I have a 3070 and I know it's not a lot of VRAM but still, takes up the 8GB of VRAM the GPU has. No matter I set the game on low or ultra, on low it takes a little more time to fill up the 8GB but still, it does.

And loadings make the game crash, throwing this errors:

only thing i can think of is to set texture quality to low
the engine is borked

[juampiursic]

Trying to play this game it's being a nightmare. It uses up all of my VRAM, I have a 3070 and I know it's not a lot of VRAM but still, takes up the 8GB of VRAM the GPU has. No matter I set the game on low or ultra, on low it takes a little more time to fill up the 8GB but still, it does.
And loadings make the game crash, throwing this errors:

only thing i can think of is to set texture quality to low the engine is borked

It actually is. Game is all set to low.

[kode54]

Compatibility Report

System Information

• GPU: RX 6700-XT
• Video driver version: Mesa 23.2.1, -TkG 24.0.0_devel.181120.b5bcb658b4d (tested both)
• Kernel version: 6.6.2-273-tkg-eevdf
• Link to full system information report as Gist: https://gist.github.com/kode54/d8d7bd021d6904ae23aa3788a07dfc24
• Proton version: GE-Proton8-24, also tried Proton 7.0-6

Symptoms

Same alt+tab issue as everyone else, but I didn't come to report that. Primary issue is that when I'm running the game at "Fullscreen" 1920x1080 on my 3840x2160 monitor, the upscaled surface has tiling glitches. Running the game unscaled via Borderless Fullscreen (only fills top left quarter of desktop) or Windowed, there are no glitches.

Adding a video captured from the monitor. The glitch does not show up on unscaled mirrored outputs, as I was unable to capture it from a 1080p output with an HDMI capture device, and it did not appear in OBS screen capture.

https://f.losno.co/v/IMG_0492.mp4 (1080p60, AV1, 59MB)

[rowbawts]

Also having issues with alt-tab, whenever I come back to the game it's not a black screen but just completely unresponsive and I have to force quit.

Proton 8.0-5
Freedesktop SDK 23.08 (Flatpak runtime) (64 bit)
Kernel Name: Linux
Kernel Version: 6.7.4-200.fc39.x86_64
Driver: AMD AMD Radeon RX 6950 XT (radeonsi, navi21, LLVM 17.0.6, DRM 3.57, 6.7.4-200.fc39.x86_64)
Driver Version: 4.6 (Compatibility Profile) Mesa 23.3.4 (git-27405fd573)

[benjamimgois]

The problem i'm having with deathloop, is that the performance seems to degrade overtime. When you start the game it runs perfect fine, but after sometime have a huge loss the fps and frametimes