Detroit: Become Human (1222140)

[rkfg]

Compatibility Report

• Name of the game with compatibility issues: Detroit: Become Human
• Steam AppID of the game: 1222140

System Information

• GPU: GTX 1070
• Driver/LLVM version: nvidia 440.82
• Kernel version: 5.7.4
• Link to full system information report as Gist: https://gist.github.com/rkfg/184cc2c1786e18b020b42df850e33aa5
• Proton version: 5.0-9

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.

Symptoms

The game works mostly fine and I played 4 hours so far with no crashes or glitches, except it seemingly crashed on the first launch right after installation, no idea why. The compatibility tool wasn't forced in the properties, after I did that it worked.

My issue is frame time spikes (=FPS drops) that are probably caused by CPU load. They're not very annoying but noticeable. They don't present on Windows as can be seen in this video comparison (not mine): https://www.youtube.com/watch?v=iH81xrJLTdM (notice the frame time spikes on the Wine frame time graph)

There's an area in chapter 3 where it's easy to reproduce this slowdown, the CPU usage jumps almost to 100% (all or most of the cores are used) and the game stutters for a bit. It does not look like shader compilation because they're precompiled on first run and this happens in the same area, not on entering some new area. It can be reproduced many times as well. I don't know much about Wine internals but there was an issue with the demo although the FPS was consistently very low, not like it is now.

Reproduction

Here's my video of the said stutter: https://youtu.be/LC2xYzX1Ktc
In this alley when you turn around near the crossroad, FPS drops and CPU usage spikes. After some time it goes back to normal until you walk away and return to this place.

[Leopard1907]

I don't have an AMD gpu but as a note for others , this game doesn't work with RADV. Use Vulkan driver of AMD's gpu-pro package.

[kisak-valve]

Hello @Leopard1907, second hand, that information is invalid and/or outdated. If someone has an issue with a current release of mesa/radv and an AMD gpu, they should report it to the mesa devs.

[rkfg]

For the record, I finished the game without crashes/glitches so apart from those occasional slowdowns and stutter it's fully playable from start to finish.

[mashedkeyboard]

Sorry to cause issues, but Detroit doesn't work for me at all. The demo worked fine, so I bought the full game, but that's completely non-functional for me. I get a black screen, but nothing else ever comes up :(

The Proton log, and my system information, is available in this gist. If anyone can give any advice, suggestions or other help, it would be greatly appreciated!

[rkfg]

@mashedkeyboard what's this: Options: {'forcelgadd'}? Do you have something in your launch parameters? If so, try to remove it.

[mashedkeyboard]

@rkfg I didn't set it - looks like it's large address awareness for Wine, and is default: f96c8d6

[rkfg]

Okay, interesting. Can you try with Proton-GE? Also your VRAM is kinda low, maybe it was enough for the demo but not for the full game.

[mashedkeyboard]

I've tried with 5.8-GE-2-MF, but I'll try the pre-release and see if that helps. I'm also trying moving it to another drive, to see if perhaps that's the issue.

I'd be very surprised if the VRAM was the issue; my GPU works fine with VR, and the demo ran at or near a solid 60fps, so it would be strange to have a problem with this. I've never had a VRAM issue with any game I've played before.

[rkfg]

You can also try to simply delete the game prefix and let it recreate it. I had an issue with a game not starting because I had no internet when I installed it and it couldn't setup DirectX because of that. Also try to verify the files just in case.

[mashedkeyboard]

Some combination of 5.9-GE-2-MF, moving the drive, and recreating the prefix, seems to have worked! I suspect it was a prefix initialisation issue, like you say - thanks very much :)

[mathew2214]

AMD Navi10 with Mesa 20.1.2
running the game with proton always causes a complete GPU hang.

[Leopard1907]

@mathew2214 ACO or LLVM or same result on both?

[mathew2214]

@Leopard1907 ACO hangs my system. LLVM causes the game to hang on compiling shaders 0%. i can kill the game's process while it is stuck at 0% and it has no adverse effects on the rest of my system.
here is my system info:
https://gist.github.com/mathew2214/9c768f049702a3e7888f5d962bbe44e1