Open RodoMa92 opened 5 years ago
For me, the game works if I disable the compositor (KDE). But when editing the graphics settings, it crashes and does not save the settings.
For me, the game works if I disable the compositor (KDE). But when editing the graphics settings, it crashes and does not save the settings.
Tried the same trick, no luck here. Still a crash on a black screen.
Game starts on vega 56 and rx580 after several tries but there are problems with lighting: all environments are really dark, had to adjust gamma in-game settings to max. Tried dxvk 1.0.3 and 1.1.1 with radv and amdvlk with mesa-git
.
Changing graphics settings causes game to crash but you can adjust them manually in drive_c/users/steamuser/Application\ Data/Sega/YakuzaKiwami2/graphics.ini
Occasionally crashes will show d3d11.dll
in the backtrace, so might be dxvk
related. Log with d3d11
in the backtrace:
steam-927380_d3d11.log
Crashes on startup should hopefully be fixed in DXVK as of doitsujin/dxvk@8784ed673bd1e45125af8ab05412776402767bd5.
can confirm that gamma issues and crashes (on settings change included) are fixed with the current dxvk master. thanks @doitsujin
Same here, everything runs perfectly fine with the latest master from @doitsujin. All the crashes are gone; even if the gamma still looks like a little too dark for me, however it's an easy fix from the settings. Thanks again for your time.
Yakuza Kiwami 2 GPU usage
Issue transferred from https://github.com/ValveSoftware/Proton/issues/3121. @Alpha-180 posted on 2019-10-03T21:19:44:
The game has low GPU usage when you are in game however in the menus the GPU usage spikes up normally. To test this I uncapped the frame rate and on both the main menu and when you pause the game the GPU can hit 100% load and is not being limited by the CPU. However once the menus go away and you are just in game GPU load drops dramatically and I have seen as low as 37% usage. Forcing SSAA increases GPU load but does not affect the frame rate at all. For example in one area I could be getting 46 FPS at 56% load, I enable SSAA and load jumps to 87% but the FPS remains the same.
Being in game and out of a menu reduces GPU load.
Below are some screenshots I took to showcase the increase/decrease in GPU load
@Alpha-180 that's a CPU limit, not really a Proton issue.
@doitsujin Just to make sure I'm understanding right you mean like a CPU bottleneck right? If that's the case it shouldn't be as the CPU isn't pinned at 100% load but rather at about 70% load (In game at least). In other proton games even with higher CPU usage on all cores the GPU is able to provide more frames granted the CPU is not at 100% load. Here's a screenshot from MH:W using proton to show what I mean if that's what you mean. In the screenshot the GPU is at 98% load and had hit 100% beforehand while on all cores usage was always above 80% on all cores, sometimes going into the 90+ range.
be as the CPU isn't pinned at 100% load
That's not how CPU limits work at all. Multicore scaling in this engine is limited, and your GPU is very strong considering that you're only running 1080p resolution and a game that can run at ~60 FPS even on a 1060. I'd honestly be surprised if you saw significantly higher GPU utilization on Windows in this game.
I don't know how the engine works but I do indeed have significantly higher GPU utilization in Windows. Over 50% difference in usage in the same area 47% in Linux using Proton vs 98% in Windows and the CPU is being used a bit more as well. Here are some screen shots with MSI Afterburner and Task manager showing the GPU/CPU usage.
Game crashes after completing a few bouncer missions Edit: Getting this after a couple minutes of normal gameplay too after completing a mission
Note: I tested this at 4K with every setting on Ultra (with Depth of Field and Blur disabled) and SMAA x1
I wasn't running with PROTON_LOG enabled, but I was running steam from console so I have a crashdump. Made it a dropdown to not disrupt the ticket because it's 206 lines.
If someone is interested in looking into this let me know if you need more information, perhaps another go at it with PROTON_LOG=1 or some other env variables
Compatibility Report
System Information
I confirm:
steam-927380.log
Symptoms
Reproduction