search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
23.88k stars 1.04k forks source link

Detroit: Become Human (1222140) #4003

Open rkfg opened 4 years ago

rkfg commented 4 years ago

Compatibility Report

System Information

I confirm:

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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

mashedkeyboard commented 4 years ago

@rkfg I didn't set it - looks like it's large address awareness for Wine, and is default: https://github.com/ValveSoftware/Proton/commit/f96c8d6e6a10725fa50e12a03238e76a817cf5f2

rkfg commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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

Leopard1907 commented 4 years ago

@mathew2214 ACO or LLVM or same result on both?

mathew2214 commented 4 years ago

@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

kisak-valve commented 4 years ago

Detroit: Become Human stuttering an PS4 controller issues

Issue transferred from https://github.com/ValveSoftware/Proton/issues/4035. @Johnnii360 posted on 2020-07-01T07:49:36:

Compatibility Report

System Information

I confirm:

steam-1222140.log

Symptoms

The game is mostly working very well but stutters especially in open areas. Another issue is by the PS4 controller. In the drawing scene with Markus the interactions fail. It is a interaction for right thumb stick shown but it doesn't work.

Reproduction

I've already tried to loose the FPS lock and set it manually to 4 (no limit) in the config file but it doesn't work. Set the game to 30 FPS lock tempers the issue a bit but it's still present. Regarding to the PS4 controller issue the failed interaction could triggered by mouse.

Appendix

5.11-GE-2-MF is a hint glitchy in Detroit. 5.11-GE-1-MF works a bit better.

minionprocyk commented 4 years ago

i can confirm, AMD 5700xt, got the game to launch the very first time (lots of stutters). 2nd launch and beyond have always hung with the process taking a lot of cpu. Tried LLVM and ACO.

ragasubekti commented 4 years ago

Okay the problem is when using RADV the gpu will hung up and just throw me back to login screen. Using AMDVLK is working fine on the first chapter.

Johnnii360 commented 4 years ago

Detroit: Become Human stutter issue still there.

rkfg commented 4 years ago

I wonder if it's Linux-specific at all. If anyone with Windows can check and compare I'd be grateful!

Johnnii360 commented 4 years ago

Here another log. Maybe you find something. :) steam-1222140.log

I wonder if it's Linux-specific at all. If anyone with Windows can check and compare I'd be grateful!

@rkfg I heard that the game run better with Lutris (Epic Games Store Version) without any stutter etc.

rkfg commented 4 years ago

@Johnnii360 very interesting, I don't use EGS so would be great to confirm or disprove this as well!

Johnnii360 commented 4 years ago

I forgot to say that the clothes and hairs - especially from Hank - flicker sometimes (physic based objects).

jamoflaw commented 4 years ago

Played through all the way on linux. Works perfectly in game for me. Only minor issue i had was that the game doesn't close correctly on quit, other than that it ran perfectly - and is also an absolutely epic game

felisucoibi commented 4 years ago

Some people say you have to delete a file after each restart https://www.protondb.com/app/1222140 ~/.steam/steam/steamapps/common/Detroit Become Human/ShaderCache/VkPipelineCache.bin

Leopard1907 commented 4 years ago

https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6478

There is a pending fix for Detroit Become Human hang issues on Radv.

NikoBellicRU commented 3 years ago

I tried playing this game a while ago and the game would freeze every 1-2sec, now you can move but it has huge frame drops that really makes it unplayable ( especially at the park after the first mission ), tried it on w10 and works fine 30fps lock so i don't know what the problem is but i guess i have to play this one on windows :/ steam-1222140.log

Also it only worked with proton GE for me.

kisak-valve commented 3 years ago

Detroit Become Human no launch

Issue transferred from https://github.com/ValveSoftware/Proton/issues/4525. @richterman posted on 2021-01-03T00:41:00:

Game will nonly launch to do it's built in shader cache, yes this game has a built in shader cache, does it after steam's shader cache. After the game does it, it will no longer launch. Here's the log. My os is arch, latest as of pacman -Syu. My hardware is, amd 3800x, 5700xt, and i'm using amdgpu with mesa. I also belive i may have llvm installed as well(not sure, been 6 months since i built this computer). I tried all versions of proton and it still won't launch. Please let me know if you need more information, I tried my best to be blunt, but his is also my first time writing a report. steam-1222140.log

kakra commented 3 years ago

I've tried this game with Proton 5.13 Experimental (experimental-5.13-20210126):

Since the game seems to lose input events also in keyboard mode, it's currently unplayable for me.

NikoBellicRU commented 3 years ago

Today i tested this again with the new proton 6.3 / experimental and my problem is still the same, huge stutters/jumps and framedrops making the game unplayable on proton.

Tried disabling Esync/Fsync, deleting the shader file on the game folder, disabling some cores as some user reported on protondb but none of this helped.

Proton: https://www.youtube.com/watch?v=eI2vkJA7M_0

Windows: https://www.youtube.com/watch?v=iTevwxK7U-8

Sys info: https://gist.github.com/NikoBellicRU/6079f881a76ac9a3b75950e87e85aa6f

AwesamLinux commented 3 years ago

System Information

Compatibility Report

I'm getting good performance with recent Proton versions (everything maxed at 1440p game rarely drops below 60fps)

Now only remaining a couple of minor issues for me:

For example the site gamepad-tester.com reports "Axis 4" 1.00000 or -1.00000 when pushed all the way up or down on the right analogue stick, that seems correct.

This is with a 8BitDo Pro 2 controller (set to X-Input mode)

steam-1222140.log

minionprocyk commented 3 years ago

hi @AwesamLinux Ive played this on linux and windows. And I can vouch that the issue of the steam controller not going all the way I also had on windows. Indeed it becomes frustrating enough I switched to an xbox controller to get past certain scenes.

Good catch on the hair issue though.

hakzsam commented 3 years ago

@AwesamLinux The hair issue should be fixed by https://gitlab.freedesktop.org/mesa/mesa/-/commit/729ebe4b17f0905f87f41c0ffe004e042f3c55f6

AwesamLinux commented 3 years ago

@hakzsam I can confirm, I'm no longer seeing any graphical issues.

GPU: RX 5700 GPU Driver: 21.2.0-devel (git-fda4eaf 2021-05-29 focal-oibaf-ppa) Kernel version: 5.8.0-53-generic Distro version: Mint 20.1 (64bit) (Cinnamon) Proton version: Proton Experimental

kisak-valve commented 3 years ago

Tracking note: Dropping the mesa and RADV labels because the fix mentioned a couple comments ago has been backported to mesa 21.1.2.

DomiStyle commented 2 years ago

Did anybody experience graphic corruption in this game like in the picture below?

detroit

It only happens in this game and it only affects my screen, screen recordings are not affected. Seems to mostly happen when the screen is jumping in cutscenes or when the camera is moved quickly.

Proton log: steam-1222140.log Steam system info: https://gist.github.com/DomiStyle/a0054e9380c85c49dadc94085b92fd2b

I tried with Proton 6.3-6 and Experimental but same result.

Johnnii360 commented 2 years ago

@DomiStyle Did you just try a version from Glorious Eggroll?

DomiStyle commented 2 years ago

@Johnnii360 Just tried with Proton-6.16-GE-1 but same issue.

Johnnii360 commented 2 years ago

@Johnnii360 Just tried with Proton-6.16-GE-1 but same issue.

Hmm... How's your Monitor connected to your graphics card? If you are use a Display Port connection disconnect the power cable and wait 5 Minutes to drain the residual current. Then reconnect again and try.

This issue look like a GPU or VRAM failure to me but if it's only on this game it's maybe a compatibility issue or bug.

DomiStyle commented 2 years ago

Loose connection or GPU failure was the first thing I was thinking as well but since it's only this game I'm not sure that's the case. Resident Evil Village works flawlessly at the same time.

I will try switching between X11/Wayland and disabling/enabling Freesync, maybe that helps.

Johnnii360 commented 2 years ago

Ah yes, Freesync can maybe a issue. But you are using a Display with over 120Hz, so why you are use Freesync? :) Freesync is like Vsync to avoid tearing and when you play with or over 120Hz you really don't need Vsync or Freesync.

DomiStyle commented 2 years ago

So it seems to happen with both X11 and Wayland also with Freesync disabled and enabled.

Freesync is like Vsync to avoid tearing and when you play with or over 120Hz you really don't need Vsync or Freesync.

Freesync also helps with frame rate fluctuations and frame rates which are not divisible by the display frame rate, which is quite common on high refresh rates.

NikoBellicRU commented 2 years ago

Replying to https://github.com/ValveSoftware/Proton/issues/4003#issuecomment-813446260

Retested the game again today and i still have horrible performance with any proton version i use.

Oschowa commented 2 years ago

I can't reproduce the issues mentioned in https://github.com/ValveSoftware/Proton/issues/4003#issuecomment-924736819 on a 6700XT with Proton Experimental and latest Mesa, also using freesync on x11. Performance seems fine as well. Does this still happen for you @DomiStyle? Still, I'd rather suspect some display issues and not a RADV/Mesa bug.

DomiStyle commented 2 years ago

@Oschowa Just downloaded the game to test it again and it seems like the issue is gone now.

NikoBellicRU commented 2 years ago

I can't reproduce the issues mentioned in #4003 (comment) on a 6700XT with Proton Experimental and latest Mesa, also using freesync on x11. Performance seems fine as well. Does this still happen for you @DomiStyle? Still, I'd rather suspect some display issues and not a RADV/Mesa bug.

I really cannot understand this, i just upgraded to a 2700x and yet the problem remains the same what differs from my specs?

I tried everything at this point like other distros with clean install, flatpak / not flatpak, gamemode, manualy changing cpu governor, kernels like tkg / liquorix / xanmod and different schedulers, disable my cpu / ram overclock settings in bios but nothing change and it is just in this game so i don't get it . . .

Bitwolfies commented 2 years ago

In the cases of games like these, is it helpful at all to run in game shader compilation when running with proton? Aren't those shaders completely ignored for the ones VKD3D will generate?

rkfg commented 2 years ago

They'd be completely ignored because this game doesn't even use D3D, it uses Vulkan natively so no API emulation needed. And it compiles its own shaders on first start by itself.

LunaCodeDemon commented 2 years ago

For me the game seems to freeze whenever a mission is completed, i can only view the last part of the chapter and because it's entirely frozen only an xkill command was able to close the game. The missions run pretty smooth, except for the times the game randomly overloads all cpu threads for a half second.

Stat info:

I would be happy if the game wouldn't freeze everytime i complete a mission.

Bonus Info: Typically I have 4gig zram swap but for this game I have to set the zram to 16gig, because the game tends sometimes to eat up 23 gig of ram making my system feel like a zip-bomb went off. (if the game doesn't get it's initial ton of ram for shader precache it just crashes)

BearsPunch commented 1 year ago

with my 7900 XTX RADV (23.1 git) has about 60-70% of performace if compare to AMDVLK (2023.Q1). Also interesting thing that my previus 3070 TI has about 1.5x - 2x better performance in this game, but 3070 TI is about 2x as weak compare to 7900 XTX

kisak-valve commented 1 year ago

Hello @BearsPunch, https://gitlab.freedesktop.org/mesa/mesa/-/issues/8032 seems relevant.

BearsPunch commented 1 year ago

Hello @BearsPunch, https://gitlab.freedesktop.org/mesa/mesa/-/issues/8032 seems relevant.

yes. I don't have so bad situation as man in gitlab has. In the same room with ultra settings and 1440p I have more than 100 FPS. But It jumps bw 100- 170 fps. But worst situation when start second chapter. When girl look at you I have 30-40 fps, when my 3070 TI had 90 fps. With AMDVLK have about 50-60 fps, but it still not good for so powerfull gpu. Tested on Windows - similar situation. Better than Linux (AMDVLK) but still not good as 3070 TI was.