dxvk bug: https://github.com/doitsujin/dxvk/issues/579

Devil May Cry 4 SE, Numerous graphical problems.

Issue transferred from #2151.
@DigitalDevilSummoner posted on 2018-12-28T02:14:10:

Compatibility Report

-Devil May Cry 4 Special Edition

* Steam AppID of the game: 329050

System Information

https://gist.github.com/DigitalDevilSummoner/d7a227765539daee04f9fd1d98d2be93

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.

When starting a level as Vergil, Lady, or Trish, the level doesn't load correctly, and it isn't always consistent either, I was able to play Lady's opening story missions just fine, but not vergil. Picking Vergil and Tris for Bloody Palace, also did not work.

When starting bloody Palace as Trish, I get this:

I get similar results for Vergil and Lady.

CORRECTION: Nero, Dante, and Lady work. Vergil and Trish don't.

steam-329050.log

It is fixed in dxvk 0.95, see: https://github.com/doitsujin/dxvk/issues/579#issuecomment-453782689

Waiting for this version or greater to get into the latest Proton, it should then work.

Made and interesting discovery today

The graphical error only happens when the HUD is visible, the screenshot in my first post is from the beginning of bloody palace as Trish, which starts with a battle, and a visible HUD. I am running this on Proton 3.16-7 with Wine D3D and D3D11 disabled.

Compatibility Report

• Name of the game with compatibility issues: Devil May Cry® 4 Special Edition
• Steam AppID of the game: https://steamdb.info/app/329050/

System Information

• GPU: GTX 760
• Driver/LLVM version: NVIDIA 440.64
• Kernel version: 5.5.13-zen
• https://github.com/shoober420/linux-scripts/blob/main/home/shoober420/sysinfonvidia
• Proton version: 5.0-5b

steam-329050.log

Symptoms

Game freezes when switching to fullscreen mode. I have to force quit with htop.

Whitelist Request

• Name of the game to be whitelisted: Devil May Cry® 4 Special Edition
• Steam AppID of the game: https://steamdb.info/app/329050/

System Information

• GPU: GTX 760
• Driver/LLVM version: NVIDIA 440.64
• Distro version: Arch
• https://github.com/shoober420/linux-scripts/blob/main/home/shoober420/sysinfonvidia
• Proton version: Proton 5.0-6-rc1

LOG:
steam-329050.log

Proton 5.0-6-rc1, the next branch, seems to have fixed the bug with going fullscreen. Works great out of the box.

The game hangs when trying to start the game in fullscreen. Changing vsync or refresh rate doesn't make a difference. Changing to and from fullscreen works fine in-game if launched in windowed mode.

On a dual monitor setup, both 1080p while one is 144Hz and the other 60Hz. Nvidia GTX 1660 driver version 440.82. Using Proton 5.0-7 but the same problem is in earlier versions.

What I've found with the fullscreen issue, is that the game freezes on boot under both of the following conditions:

• Fullscreen is enabled, or toggled in-game
• Resolution is set to the desktop resolution

So on my 4K display, I cannot run the game at 3840x2160 fullscreen. But, either 3840x2160 windowed, or 2560x1440 fullscreen works fine.

This also applies when using the DDMK mod (requires consolas font verb installed in the prefix), which by default makes the game run in an enforced Borderless Windowed mode--it will freeze on bootup, before the window decorations are forced off. However, if fullscreen is disabled in DMC4's settings, and borderless is enabled in DDMK, it will have an effective borderless fullscreen at the display's native resolution, so this could be considered a fix.

Aside from this, with my current setup, the game has a lot of stuttering - consistently, even.
Ergo, start the game and run the benchmark: every time a new enemy spawns in, every time the benchmark is first run every session, the game has what looks like a loading stutter. The effect is very blatantly obvious in cutscenes and gameplay, anytime a new asset is loaded. This is easily repeatable, and does not seem to be shader stutter (which seldom happens these days on my setup anyways).

This is a 2015 DX10 game running on a 3060ti, so I'm pretty sure it should be more than able to handle DMC4.

@SeongGino
You are actually wrong regarding the stutters. They are 100% related to shader compilation. Been trying to play this game recently on Windows 10, and of course the first thing I've noticed were those stutters you mentioned in your post. So I tried to play the game with dxvk 2.6.2, and it successfully creates DevilMayCry4SpecialEdition.dxvk-cache which completely eliminates stutters in consecutive game sessions (ie during the first benchmark test the game heavily stutters on new enemy spawns, every time new effects play out, etc, but after restarting the game, the benchmark doesn't stutter anymore).

But, as is the case for the proton users, the game doesn't work in fullscreen on Windows 10 either. The game can only be launched in windowed mode when dxvk is installed.

DevilMayCry4SpecialEdition_d3d11.log

DevilMayCry4SpecialEdition_dxgi.log

@SeongGino Couldn't really repro on my amd desktop or nvidia laptop.

For both I used proton 9 (currently the default proton version), I first let steam compile the shader cache, then set the games to fullscreen at the highest setting possible.

On AMD there were no hitches when running the benchmark, not even the first launch..
On NVIDIA it stuttered when the first few enemies appeared, but closing the game, and even rebooting the computer didn't make these stutters reappear.

If you're still seeing these stutters it's possible that the nvidia drivers are cleaning up the shader cache due to hitting a limit, in that case setting __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 in the game's launch parameter may prevent the issue from reappearing.

I don't have a 4k monitor, but 2k on the desktop worked as expected, and 1980x1200 was fine on the laptop.

Desktop: ryzen 5700X3D, 9060 XT, mesa 25.2.0
Laptop: ryzen 8845, 4060, nvidia 575.64.03

@simifor It still definitely has a visible stutter by default on Proton 10, but setting the cache skip cleanup magic word does seem to resolve this.

Still, this isn't really an issue I have with other games.

For context, at some point or another, I had this set in my environment: __GL_SHADER_DISK_CACHE_SIZE=2000000000

So take that for what you will.