Dark Souls III performance regression with Proton 3.16 (374320)

[Bloodaxe95]

Game runs perfectly on my end, I notice no difference between Linux and Windows. Both standard mouse-keyboard and the Steam Controller work flawlessly!

• OS: Xubuntu 18.04
• GPU/driver-version: GTX 970 - nvidia-driver-396
• Kernel: 4.15.0-32-generic
• Proton: 3.7

[Bednar87]

crashes for me when I click new game.

`Computer Information: Manufacturer: Unknown Model: Unknown Form Factor: Desktop No Touch Input Detected

Processor Information: CPU Vendor: GenuineIntel CPU Brand: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz CPU Family: 0x6 CPU Model: 0x3a CPU Stepping: 0x9 CPU Type: 0x0 Speed: 3800 Mhz 4 logical processors 4 physical processors HyperThreading: Unsupported FCMOV: Supported SSE2: Supported SSE3: Supported SSSE3: Supported SSE4a: Unsupported SSE41: Supported SSE42: Supported AES: Supported AVX: Supported CMPXCHG16B: Supported LAHF/SAHF: Supported PrefetchW: Unsupported

Operating System Version: "Arch Linux" (64 bit) Kernel Name: Linux Kernel Version: 4.18.4-arch1-1-ARCH X Server Vendor: The X.Org Foundation X Server Release: 12001000 X Window Manager: Xfwm4 Steam Runtime Version:

Video Card: Driver: NVIDIA Corporation GeForce GTX 970/PCIe/SSE2 Driver Version: 4.6.0 NVIDIA 396.54 OpenGL Version: 4.6 Desktop Color Depth: 24 bits per pixel Monitor Refresh Rate: 59 Hz VendorID: 0x10de DeviceID: 0x13c2 Revision Not Detected Number of Monitors: 1 Number of Logical Video Cards: 1 Primary Display Resolution: 1920 x 1200 Desktop Resolution: 1920 x 1200 Primary Display Size: 20.39" x 12.76" (24.02" diag) 51.8cm x 32.4cm (61.0cm diag) Primary Bus: PCI Express 16x Primary VRAM: 4096 MB Supported MSAA Modes: 2x 4x 8x 16x

Sound card: Audio device: VIA VT2020

Memory: RAM: 7938 Mb

Miscellaneous: UI Language: English LANG: en_GB.utf8 Total Hard Disk Space Available: 104481 Mb Largest Free Hard Disk Block: 26759 Mb VR Headset: None detected

Recent Failure Reports: `

gist: https://gist.github.com/Bednar87/e71fb272481c8f64efc7ee1b614218e3

[ghost]

@Bloodaxe95 please do further testing with a family shared dummy steam account. Playing Dark Souls 3 using DXVK might trigger the anti-cheat system and cause a softban.

[photex]

Gets to a point where I get a mouse cursor then exits without an error

[meowmeowfuzzyface]

This game was working flawlessly for me on Friday. Today, it is not launching either with 3.73 or 3.74 beta, with or without "PROTON_USE_WINED3D11=1 %command%".

I'm on Ubuntu 18.04 with the 18.3.0-devel - padoka PPA driver for Fury X, same as Friday.

Possibly related, Dark Souls 2 was also working on Friday, but today it crashes unless launched with "PROTON_USE_WINED3D11=1 %command%".

[Emanem]

Main issues for me:

• In order to adjust the screen to 1440p in fullscreen, one has to go to window mode, then change to 1440p, then back to fullscreen - this setting doesn't get saved apparently
• All maxed out with 1080 GTX (396.54) and latest Proton (3.7-4 beta) the FPS is only 37.5 in 3440x1440 full screen; if I run in 1080p or 1440p windowed it's 60 FPS
• Sometimes the game doesn't exit properly and needs to be killed (when changing resolution form 1080p to 1440p)
• Screensaver/lock gets activated when playing with pad only

Almost whitelist... the game is very playable with my PS3 pad and it's just fantastic... (Ubuntu 16.04.4 with HWE).

[kayosiii]

The issue I am having is that Steam controller will look but not move or attack, ditto for keyboard and mouse

[meowmeowfuzzyface]

Not sure what happened, but the game is now working flawlessly. I haven't changed anything so I guess there was a Proton update? I'm using the PROTON_USE_WINED3D11=1 %command% launch option.

Ubuntu 18.04 with the 18.3.0-devel - padoka PPA driver for Fury X.

[michaeltintiuc]

I get a crash each time I try to open the door after Iudex Gundyr, I am however running this on 390 nvidia drivers, this could be the issue :man_shrugging:

[dittr]

@michaeltintiuc do you have nvidia-driver-396, i had the same issue but updating the nvidia driver fixed it for me. (with nvidia-390 i got the same crash)

[michaeltintiuc]

I'm running Solus OS and the devs are kind enough to give some extra testing to the 396 drivers :laughing: and I'm waiting patiently, but that's awesome to know @Sw3eM , thanks for letting me know!

[Xeers]

Reborn OS (Arch Linux) AMD FX, Nvidia Geforce GTX 950 The game works perfectly but I can not upload the resolution more than 1920x1080 (my monitor is 2560x1080)

The command PROTON_USE_WINED3D11 = 1% command% is not necessary, it breaks the game

[UndeadKernel]

@Bednar87, did you figure out a solution to your problem? I have the same specs and problem (game crashes if I choose "new game"). To solve the issue, I started the game in Windows and saved as soon as I had control. Afterwards,I copied the save game from windows to linux. This way, I don't have to choose "new game", just "continue" and the game works rather well.

[Bednar87]

@UndeadKernel, nope. I don't have access to a windows machine I can try this on, but thanks for reporting you have found a solution that works for you.

Going to google to see if save games are portable...

[meowmeowfuzzyface]

@Bednar87 Save games are portable. For both DS2 and 3, the save directory in Windows is under C:\Users\\AppData\Roaming. The folder is called DarkSoulsIII.

You can copy paste that folder into /steamapps/compatdata/374320/pfx/drive_c/users/steamuser/Application Data/.

[patlefort]

I'm on Antergos. I have a problem with this game and my dualshock 4 controller: The right trigger isn't working properly. It does normal attacks and if I try to bind something to it, it's not detected. It works in DS1 and the left trigger work. Very strange problem. I tried to rebind it with steam controller settings but it doesn't work.

Next small problem is sometimes the cursor will become visible on the middle of the screen. To hide it, I have to press start, move the mouse, close the menus.

Another big problem: Sound. Sometimes, all the sounds will sound like it's coming from the front-left on my 5.1 setup. Restarting the game fix it until it does it again. The problem also occur in DS1.

[jonlap]

Seems to run very well (I only played 10-15 minutes though). Only issues were that problem with 1440p resolution mentioned earlier and Xbox 360 controller analog sticks and dpad being overly sensitive (working normally with every other game) to the point game is practically unplayable with it. Info here.

[GloriousEggroll]

Game runs fine here on DXVK: Proton: 3.7 Beta 6 OS: Arch Kernel: 4.19.0-rc2 Mesa: Mesa 18.3.0-devel (git-14fe9fa11b) LLVM 7.0 GPU: AMD RX Vega 64 CPU: AMD Threadripper 1950x

[tamato]

@GloriousEggroll What do you mean "on DXVK"?

What would I need to do to get it running on DXVK?

[UndeadKernel]

@Bednar87, I believe I've figured out why the game crashes when selecting "New Game". The backtrace of the crash shows that a problem lies in the Bink video player: 0 0x00000000002ded63 in binkw64 (+0xed63) (0x00007fb815988da0)

To fix the "New Game" crashing issue, in the folder Steam/steamapps/common/DARK SOULS III/Game/movie rename the file fdp_opening.bik to fdp_opening.bik.bkp. This way, the bink libraries won't find the video and will just skip it, allowing you to play the game.

Of course this means that you won't see the introduction video. If you want to see it, just open the renamed video file with VLC. To listen to the narrator, change the audio channel.

Anybody knows what is needed to adequately run bink videos in wine? It seems that the DLL file binkw64.dll is causing problems.

[darkpumpkins]

It does crash for me to at startup. I was previously able to play it outside steam linux on wine + dxvk 0.63.

Proton: 3.7 OS: Ubuntu 18.04.1 Kernel: 4.15.0-34-generic Mesa: Nvidia 396.54 GPU: Nvidia MSI GTX 970 Gaming 4G CPU: Intel core i5-2500k

steam-524220.log

[kisak-valve]

Hello @darkpumpkins, your log doesn't match this game. Was this issue report where you intended to post?

[darkpumpkins]

Crash on startup ( this time with the correct log :P ), well the game does not start at all.

Proton: 3.7-6 OS: Ubuntu 18.04.1 Kernel: 4.15.0-34-generic Mesa: Nvidia 396.54 GPU: GeForce GTX 970/PCIe/SSE2 CPU: Intel® Core™ i5-2500K CPU @ 3.30GHz × 4

steam-374320.log

[kisak-valve]

err:winediag:FILE_CreateFile Too many open files, ulimit -n probably needs to be increased is the line of interest in the log.

[darkpumpkins]

great ! Dark souls III run ! Thanks for the tutorial, ulimit also was a pain for my samba ... -_- where should i put my old windows saves into steam proton to restore my old saved games ?

[krompus]

Game is running stable here, but performance takes a hit compared to Windows; my FPS is halved (30ish on Linux, smooth 60 on Windows):

• Arch Linux
• i5 4670K @3.8GHz
• GTX 770 Nvidia 396.54-4
• Proton 3.7-6

Hopefully future updates will improve performance. I'm about due for a new rig, though. :)

[michaeltintiuc]

It seems to have gotten worse, it no longer works, unless I rename the video files and the framerate took a hit.

[darkpumpkins]

if someone else does encounter problems with ulimit here is a solution : https://phpsolved.com/ubuntu-16-increase-maximum-file-open-limit-ulimit-n/

[krompus]

@darkpumpkins ah, thanks; I didn't know this game was affected by that issue. I discovered this when testing Downwell a few weeks ago: crashed after about 60 seconds before, stable as a rock after raising the limit.

[darkpumpkins]

@krompus kisak-valve mention me a point that i did not notice about steam play into the requirements => https://github.com/ValveSoftware/Proton/blob/proton_3.7/PREREQS.md#fd-limit-requirements I had the ulimit error into Nioh and Dark souls III but for Nioh seems wine related problem ^^.

Anyone noticed better performances with lastest nvidia beta driver ( 396.54.05 ) ? ( here is the repository : https://launchpad.net/~graphics-drivers/+archive/ubuntu/dev )

[patlefort]

I fixed my controller problem by applying some community controller profile. I don't know why this worked.

[meowmeowfuzzyface]

@patlefort If you have Steam configuration for your controller on by default, try turning it off and letting the game recognize the controller directly. You can do this per-game in Big Picture mode by going to the game in your library and selecting Manage Game. Set the controller configuration to Forced Off.

Steam controller configuration doesn't work with any of my Proton games, so this is how I've been working around it.

[jomarocas]

i have a gtx 970 and latest drivers and run in certain places in 30 fps and others in 50, this is stable in windows with 60 fps

[Emanem]

i have a gtx 970 and latest drivers and run in certain places in 30 fps and others in 50, this is stable in windows with 60 fps

Are you playing fullscreen or windowed? Because fullscreen incurs in a Nvidia drivers problem where it's basically forcing V-sync and then it goes back to 30 fps. For example, I have a 1080 GTX and I play 21:9@1440p and windowed it goes around 60 FPS, but fullscreen it goes to 37.5 (my screen is 75 Hz) because it can't precisely hit the 60 FPS with V-sync like enabled (i.e. even 59 FPS is not good enough for V-sync).

[Niroc]

Whilst in Fullscreen mode, I'm unable to change the resolution from 1080p down to my normal 900p res like in Windows. Swapping to Windowed mode, changing the resolution and swapping back to Fullscreen mode doesn't not work either which people have been doing to go to 1440p. For me it just defaults back to 1080p

On another note, whilst Fullscreen my fps is NOT locked to 30 as mentioned above by @Emanem. I get not so smooth 38-47 fps but, to maximize performance and resource I use a dedicated X session only running the openbox window manager & Steam on my NVIDIA card and V-sync is not enabled on this X session. My normal desktop runs on my Intel GPU on another TTY.

Also, I've been playing for 10 hours with no ban yet from the anti-cheat system.

• GPU: GTX 870m 6GB
• CPU: I7-4710MQ @ 3.5 GHz
• OS: Manjaro
• Driver/LLVM version: Nvidia 396.54
• Kernel version: 4.14.71-1
• Proton version: 3.7-7 Beta

[Niroc]

The resolution issue should be fixed in the following commit: https://github.com/doitsujin/dxvk/commit/87f1cd238516bc76d9525a1f75314a27d6e53e68

We'll need to wait for DXVK v0.82 to see it in proton most likely, unless Valve cherry pick the commit when updating the v0.81

[UndeadKernel]

With the latest Proton Beta (3.7-7), I'm observing drastic FPS drops in many areas where I would not previously have FPS problems. From a stable 45-50 FPS, the FPS drops to 20 and below, making the game unplayable.

Reverting back to Proton 3.7-6 is the only way to keep a stable FPS.

My system information can be found here.

[kisak-valve]

Hello @UndeadKernel, please copy your system information from steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

[Niroc]

@kisak-valve I think the regression is down the temporary high CPU load from the DXVK State Cache. @UndeadKernel could try starting the game with following launch option "DXVK_STATE_CACHE=0" to check. Proton 3.7-7 works fine for me but, I've been pretty much everywhere in-game.

[UndeadKernel]

@Niroc, I tried playing with the launch option "DXVK_STATE_CACHE=0" and still saw FPS drops. It seems to be related to the multiplayer's mode though: I notice considerable FPS drops only after I traveled to another player's "map". The map, though, was the same as mine. For the first 30 minutes of play (without multiplayer), the game was performing as expected. Therefore I do not believe it's related to the cache.

[Niroc]

@UndeadKernel peculiar... I'll do some invading too see if my laptop does the same. Check out nvidia-xrun & Feral game mode (for Feral game mode set you PAM file "/etc/security/limits.conf" too "*insertUserNameHere* - nice -5 " then restart, The nice value does seem to help with the responsiveness of my gamepad. ) I'll let you know what I find.

[UndeadKernel]

@Niroc, I was already using Feral's Game Mode and my system has been configured with the necessary changes (i.e., ulimit and nice limits) to run Proton. With Proton 3.7-7, the game's window is managed differently: I can use ALT+F4 to kill the game. With 3.7-6 ALT+F4 does nothing. I don't know if this is making KDE (my window manager) change its compositor settings for the game.

[krompus]

I'm getting massive FPS drops when I warp at bonfires on 3.7-7 stable and 3.7-8 beta; 3.7-6 stable didn't have this issue. I was using it just last night, and the only software that has changed since has been 3.7-7 replacing 3.7-6.

• i5 4670K @4.0GHz
• GTX 770 2GB with nvidia 410.57-4
• Arch Linux
• Linux kernel 4.18.12.arch1-1

Edit: installed nvidia-vulkan-dkms 396.54.09, and the issue persists; not a driver issue. 720p works pretty well despite looking like poo, so that's what I'm using for now.

[Niroc]

@Undead Cool, I did some invading btw and I haven't noticed any frame drops on the FPS counter when in other other peoples worlds. Personally, I use the lightweight Openbox window manager that literally just runs steam & my games on it's own X session on my Nvidia card. I haven't touched KDE this decade so, I couldn't say about that much about that I'm afraid...

I haven't noticed the bonfire warping frame drop outlined by @krompus, I run the game at 900p on my GTX 870m with most setting set to med/low to ensure a consistent 60 FPS (Same as Windows as, the second DLC is rather GPU taxing in certain areas). More details on my system are 9 posts up though, I'm now running Proton 3.7-8 beta.

I have encountered a new issue were the audio begins to crackle after running Dark Souls 3 for a prolonged period. (It took 5+ hours to happen, it's happened more than 3 times)

[UndeadKernel]

Reporting on the FPS drop issue after testing with Proton beta (3.16-1). The in-game performance is generally much much better. I've seen an FPS increase of more than 20%. However, after traveling to another world (either through a bonfire or through an invasion), the FPS drops to less than 15 FPS and the game becomes unplayable.

Any idea how I could debug this issue?

[meowmeowfuzzyface]

Dark Souls 3 (and 1 and 2) are crashing on launch for me since the Proton 3.16 update.

-Name of the game with compatibility issues: Dark Souls PTDE, Dark Souls II Scholar of the First Sin, and Dark Souls III

-Steam AppID of the game: 211420, 335300, and 374320

-GPU: Radeon Fury X

-Driver/LLVM version: mesa 18.3.0-devel from Padoka PPA, LLVM 8.0.0

-Kernel version: 4.15.0-36-generic

-Link to full system information report: Gist

-Proton version: 3.16 and 3.7-8

steam-211420.log steam-335300.log steam-374320.log

Description: All 3 games were working perfectly with 3.7-8 until the 3.16 update. Switching back to 3.7-8 does not solve this crash. The behavior is the same for both versions.

Since the update, Dark Souls PTDE, Dark Souls II Scholar of the First Sin, and Dark Souls III all crash on launch. Other DX11 games are working fine with DXVK (Witcher 3, Skyrim SE, Killing Floor 2).

Oddly, Dark Souls II and III do not crash if they are minimized (using alt + pgdn). Upon maximizing, they are stable if there is no input. If I press any button, the game crashes after one or two seconds. Dark Souls PTDE crashes even when minimized.

Things I have tried: Using the launch option for WINED3D11 or NO_D3D11. Using the -fullscreen launch option. Deleting the WINE prefix. Verifying integrity of the game files. Disabling the compositor.

Reproduction: For all 3 games: Launch the game normally. A window will pop up and crash without displaying anything.

For Dark Souls 2 and 3: Launch the game and immediately minimize the window. The game will launch normally in the background. Upon maximizing the window, press any button. The game will crash after 1-2 seconds.

[michaeltintiuc]

@meowmeowfuzzyface I had previously had similar issues with other games, reinstalling them seemed to help. I have just tried swtiching to 3.16 and if anything the performance had improved. Running on Solus OS (kernel 4.9.113), GTX 1050Ti (drivers 410.57)

[michaeltintiuc]

@meowmeowfuzzyface also check the changelog for the changed launch options

[meowmeowfuzzyface]

@michaeltintiuc Thanks for the heads up. Unfortunately, reinstalling did not change the behavior. It is still crashing to desktop briefly after launching. Using the new PROTON_USE_WINED3D command causes an instant crash without the Dark Souls III window even appearing at all.

[meowmeowfuzzyface]

I ppa-purged the Padoka unstable branch and upgraded to Ubuntu 18.10 which uses mesa 18.2.2. The crashing has gone away with 18.2.2. So this is an issue being caused by the recommended driver version (18.3.0-devel).

[mlassnig]

Not crashing, but still experiencing the FPS drops. What is weird is that I get stable 60fps, after first warp/YD I get "stable" 30fps, after the second I get stable 15 fps, third warp 8fps, then I get disconnected. Looks like a bug somewhere in the way vsync is applied, force-halfing the FPS in some weird way?

-- Kernel 4.18.6, GTX970, NVidia 396.54.09, Vulkan 1.1.70, Proton 3.16-3