Proton
Proton copied to clipboard
ValveSoftware
Deathloop (1252330)
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:
- [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.
Log: steam-1252330.log
Symptoms
Hit play, no window appears. "Stop" button remains as "Stop" indefinitely.
Reproduction
Run game
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
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
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-20210913and6.3-6
Logs:
- experimental: https://gist.github.com/BenFradella/08184cfb79234b012714f25e36e608cc
- 6.3-6: https://gist.github.com/BenFradella/ad14932da5a2cdbd70f764aa18ac4264
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
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.
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
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 ?
With latest Proton Experimental 6.3-20210916 the Deathloop started working.
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. :(
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.
Got excited since someone got it running. This is what im getting with proton experimental now after the update
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
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.
@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
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
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
OK, so what is the game doing during those 5-10 minutes? compiling shaders?
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.
Small Proton Experimental update: the game should now be playable with Nvidia GPUs.
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
Got it running with experimental, played through the first level fine. Leaving the first area the game crashed with this error.
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.
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
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.
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 https://github.com/ValveSoftware/Proton/issues/5156#issuecomment-924253392, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4CXQRT7QBXHJZHAE5DPJ3UDDFVNANCNFSM5D66F2XQ .
Replying to https://github.com/ValveSoftware/Proton/issues/5156#issuecomment-924361846
Main. Haven't switched over to the beta.
If you're currently stuck I would try the beta. In the Steam software select Betas and enter the code: juliannashotme You'll be on the [open_beta] release. I don't believe it had an update today so mine seems to be working the same as it was before.
If you're currently stuck I would try the beta. In the Steam software select Betas and enter the code: juliannashotme You'll be on the [open_beta] release. I don't believe it had an update today so mine seems to be working the same as it was before.
Thanks, I'll try it out.
Same problem as op: Hit play, no window appears. "Stop" button remains as "Stop" indefinitely. Tested with Beta Code juliannashotme and without.
GPU: RX 5700XT
Driver/LLVM version: xorg-x11-drv-amdgpu.x86_64 21.0.0-1.fc34
Kernel version: 5.13.16-200.fc34.x86_64
Link to full system information report as gist here
Proton version: Proton Experimental (date 2021-09-21).
