protonscr

Dark Souls: Remastered

protonopen appid 570940Game compatibility - UnofficialMesa drivers
ValveSoftware/Proton#1026 · opened 2018-08-30 by michaeltintiuc · updated 2026-01-09 · 71 comments · github · game page · search this game
Mmichaeltintiuc 2018-08-30 github

Seems to play with no issues at all, controller, sound, cinematics work just fine.

OS: Solus
GPU: GeForce GTX 1050 Ti
Driver: 390.77
Proton: 3.7-3

OOschowa 2018-08-30 github

I needed to install vcrun2017 via winetricks into the prefix to make it work. Also i tested with different controllers and could not get the DS4 to behave correctly, the button mappings where messed up, while a DS3 and Xbox360 pad worked fine. Furthermore the game sometimes crashes when returning to the main menu. Otherwise the game runs and performs great.

Tested on:
Arch Linux
RX560
mesa-git
llvm-svn
proton 3.7-4
proton log

SSpookySkeletons 2018-09-01 github

Needs vcrun2017 but beyond this runs perfectly.

Mmichaeltintiuc 2018-09-16 github

There are substantial graphical artifacts in The Depths and Blight Town, here's an example: https://www.twitch.tv/videos/307672457?t=00h59m16s

Llegluondunet 2018-10-06 github

@michaeltintiuc could you correct your video link please?

Nnecuz 2018-10-06 github

Here's a permanent video showing Blighttown as of Proton 3.7-7 Beta: https://www.youtube.com/watch?v=UTP88UZQoM0

Sidenote: DualShock 4 works fine for me and I haven't had any crashes.

Mmichaeltintiuc 2018-10-07 github

@legluondunet my bad, the video expired, please see video from @necuz it's the same issue

Uuppet 2018-10-15 github

I load a saved game in blighttown bonfire. Scene keep flicking.
GeForce GTX 1050 Ti, Ubuntu 18.04, nvidia-driver-390 390.77-0ubuntu0.18.04.1

Mmichaeltintiuc 2018-10-23 github

Flicker remains with latest Proton 3.16-3 beta and Nvidia 410.57 drivers

Nnickfaces 2018-10-25 github

Needs vcrun2017 but beyond this runs perfectly.

Does Proton create a separate prefix for each game? That is, is it possible to use winetricks to install components in a prefix, just like when using a regular wine?

Iicemanx7 2018-11-12 github

Using proton 3.7.8 and proton 3.16.4 I get an infinite loading screen when trying to play DSR. I did install vcrun2017 via winetricks.

GPU: GTX 1060
CPU: 2400g
RAM 16G
OS: Arch Linux
Nvidia Drivers: 410.73

WWesCook 2018-11-21 github

@nickfaces Yes, I'm pretty sure it does. The path is found under /steamapps/compatdata/<game_id>/pfx.

Mmichaeltintiuc 2018-12-26 github

Is the flickering in blighttown still present?

Hhhirsch 2019-01-19 github

Tested a bit more. On exit to menu the game crashes for me every single time this has corrupted saves on multiple occasions but I did not lose any progress. Only with In-Home-Streaming characters move slowly while the environmental effects look regular speed. This game is far from ready for the white list.

Proton:Beta (3.16-6)
Distro:Manjaro Linux
Kernel:4.18.20-1-MANJARO
RAM:16 GB
GPU Driver:NVIDIA 415.22
GPU:NVIDIA GeForce GTX 980
CPU:Intel Core i7-4790K @ 4.00GHz

Mmichaeltintiuc 2019-01-22 github

Never had crashes on exit, I can try in-home streaming, but I don't see how it can effect the game really.
Besides the blighttown flicker it is on par with the Windows version

Lleifmetcalf 2019-02-16 github

As of 3.16-7 the game crashes after the logo screens, just as the menu screen starts to appear. This is after installing vcrun2017 with winetricks.

log

Proton: 3.16-7
Distro: Ubuntu 18.04.2 LTS
Kernel: 4.18.0-15-generic
RAM: 8 GB
GPU Driver: NVIDIA 415.27
GPU: NVIDIA GeForce GTX 970
CPU: Intel Core i7-3770 @ 3.40GHz

Kkisak-valve maintainer 2019-02-16 github

Hello @leifmetcalf, can you provide a known working version?

Lleifmetcalf 2019-02-16 github

@kisak-valve It used to work with proton 3.16-6 until character creation, and I just tried it with proton 3.16-4 and it works until character creation too.

Renaming the 'movww' folder in the game folder stops the game crashing at character creation for 3.16-4, I needed to install 'binkw32' too to stop it crashing with 3.16-6. I've never had the crash after the logo screens on any proton version. EDIT: see https://github.com/ValveSoftware/Proton/issues/1026#issuecomment-464494718

OOschowa 2019-02-17 github

Still works like before here with 3.16-7 (I made sure this version is actually installed). But even on earlier versions I randomly experienced crashes on the menu like @leifmetcalf described; those seemed to have been controller related, as temporarily plugging out the controller made the game start up again.

Lleifmetcalf 2019-02-17 github

Just tried 3.16-7 without a controller plugged in, and it still crashes after the logo screens finish, just as the start screen starts to fade in.

I tested 3.16-7, 3.16-6, and 3.16-4 each on a fresh wine prefix with vcrun2017 installed, and any controller unplugged. 3.16-7 crashes as I described, but 3.16-4 and 3.16-6 do not.

Lleifmetcalf 2019-02-17 github

For 3.16-4:
After vcrun2017 was installed it would crash after the first cinematic would play. Then, I needed to:

  • rename/remove the folder 'movww'
  • install binkw32 with winetricks
  • disable cloud save

After that the game runs fine.

Proton: 3.16-4
Distro: Ubuntu 18.04.2 LTS
Kernel: 4.18.0-15-generic
RAM: 8 GB
GPU Driver: NVIDIA 415.27
GPU: NVIDIA GeForce GTX 970
CPU: Intel Core i7-3770 @ 3.40GHz
Lleifmetcalf 2019-03-09 github

Game still crashes as in https://github.com/ValveSoftware/Proton/issues/1026#issuecomment-464377502 with Proton 3.16-8

Proton:3.16-8
Distro:Ubuntu 18.04.2 LTS
Kernel:4.18.0-15-generic
RAM:8 GB
GPU Driver:NVIDIA 415.27
GPU:NVIDIA GeForce GTX 970
CPU:Intel Core i7-3770 @ 3.40GHz

NNoiseGener8r 2019-03-13 github

Game still crashes on character creation even with cloud save disabled, movww folder renamed, and binkw32 installed. What is the exact command to install binkw32 with winetricks? I'd like to make sure I did it right.

Proton:3.16-8 Beta
Distro:Ubuntu 18.04.2 LTS
Kernel:4.18.0-16-generic
RAM:12 GB
GPU Driver:NVIDIA 415.27
GPU:NVIDIA GeForce GTX 780 Ti
CPU: Intel i7 930 (8) @ 2.801 Ghz

Lleifmetcalf 2019-03-14 github

What is the exact command to install binkw32 with winetricks? I'd like to make sure I did it right.

WINEPREFIX="$HOME/.local/share/Steam/steamapps/compatdata/570940/pfx" ./winetricks binkw32 in the same directory as the winetricks script from https://github.com/Winetricks/winetricks/raw/master/src/winetricks

Lleifmetcalf 2019-03-14 github

What is the exact command to install binkw32 with winetricks? I'd like to make sure I did it right.

WINEPREFIX="$HOME/.local/share/Steam/steamapps/compatdata/570940/pfx" ./winetricks binkw32 in the same directory as the winetricks script from https://github.com/Winetricks/winetricks/raw/master/src/winetricks

If you don't mind a character with the default appearance, I can make a character for you and send you the save file.

NNoiseGener8r 2019-03-14 github

Game doesn't start at all with Proton 3.16-4 and installing binkw32 with Winetricks via the correct command didn't fix it. Blighttown issue also exists (tested with character made on Windows 10, which I no longer have.)
They don't make this easy for us.

NNoiseGener8r 2019-03-14 github

Hold on, this is an interesting one. I just successfully created a character after making no changes to the setup from any of my previous comments. Character loaded fine, everything. However, this cannot be reproduced and I have yet to be successful again.

EDIT: The game does not start with any Proton version except 3.16-8 Beta and 3.16-6 does not appear as an option.

Lleifmetcalf 2019-03-29 github

No longer getting the crash described in #1026 as of 4.2-1. I haven't tested character creation yet, but since no-one else could recreate the menu-crash issue we can probably get rid of the regression tag.

EDIT: Character creation works, and I haven't got it to crash yet! This with steam cloud sync enabled on a fresh wine prefix, no need for the binkw32 / movww fixes.

Hhhirsch 2019-04-02 github

Crash when returning to menu no longer present in current 4.x proton.

Lleifmetcalf 2019-04-19 github

As of Proton 4.2-3, the flicker in Blighttown is now longer present. Far as I've tested the game is golden. vcrun2017 is still needed though.

Proton: 4.2-3
Distro: Ubuntu 19.04
Kernel: 5.0.0-8-generic
RAM: 8 GB
GPU Driver: NVIDIA 418.56
GPU: NVIDIA GeForce GTX 970
CPU: Intel Core i7-3770 @ 3.40GHz

Ssolenum 2019-07-03 github

Using my xbox 360 gamepad causes the game to crash, works fine otherwise. Latest proton etc etc.

Any workarounds currently?

Mmichaeltintiuc 2019-07-04 github

@exezin see referenced issue above

Ssolenum 2019-07-04 github

@michaeltintiuc I assume from that, we just need to wait for a fix to arrive and there are no workarounds?

Mmichaeltintiuc 2019-07-10 github

It's been a while since I poked around proton, so not sure tbh

Ssolenum 2019-07-31 github

Latest proton release appears fix both the gamepad input causing a crash (#2805) and you no longer need to install vcrun2017 manually.

HHasshu 2019-09-12 github

Apparently, it's impossible to assign the right mouse button to any action, since it always acts as "cancel" in both the main menu and the in-game one. I'm not sure if that's something related to Proton (v4.11-3), but it used to work just fine on Windows 7.

CChiitoo 2019-09-12 github

Apparently, it's impossible to assign the right mouse button to any action, since it always acts as "cancel" in both the main menu and the in-game one. I'm not sure if that's something related to Proton (v4.11-3), but it used to work just fine on Windows 7.

This is a strange one. I seem to be able to assign it every now and then, timing it usually less than a second from clicking on the action to be set (too fast does not seem to work either though).

(Wine Vanilla 4.15-79-gec83f0c53c863)

HHasshu 2019-09-17 github

This is a strange one. I seem to be able to assign it every now and then, timing it usually less than a second from clicking on the action to be set (too fast does not seem to work either though).

@Chiitoo Indeed, that seems to be the case. (Proton v4.11-4 now.)

Sshoober420 2020-01-23 github

Whitelist Request

System Information

Game runs great out of the box!

Kkisak-valve maintainer 2020-01-23 github

Hello, is anyone seeing an issue with this game and Proton 4.11 which would block it from being whitelisted?

Ssolenum 2020-01-23 github

Whitelist Request

System Information

  • GPU: GTX 1070
  • Driver/LLVM version: NVIDIA 440.31
  • Distro version: Lubuntu
  • Proton version: 4.11-12

Works beautifully out of the box here on 4.11-12

AAwesamLinux 2020-03-07 github

System Information

  • GPU: RX 5700 ITX
  • GPU Driver: Mesa 20.1.0-devel (git-69628ab 2020-03-03 bionic-oibaf-ppa)
  • Kernel version: 5.3.18-050318-lowlatency
  • Distro version: 19.3 Tricia (64 bit) (Cinnamon)
  • Proton version: 5.0-3

Compatibility Report

The game works fine other than one possible issue, Fullscreen option acts the same as Borderless. When you try alt+tab back to the desktop the game does not minimize. I believe however this was also a problem on Windows. But other than that everything works fine

✔ Good performance (tried with ACO)
✔ Nintendo Switch Pro controller worked (wired and wireless)

steam-570940.log
system_info.txt

MMollyMaclachlan 2020-05-11 github

Whitelist Request

Name of the game to be whitelisted: DARK SOULS™: REMASTERED
Steam AppID of the game: 570940

System Information

  • GPU: GTX 1050 Ti
  • Driver/LLVM version: NVIDIA 440.44
  • Distro version: Slackware 14.2
  • Proton version: 5.0-7

Full system information report can be found here.

Report

Excellent performance, everything working fine save for alt+tab. While I don't have quite the same issue as @AwesamLinux in that I can alt+tab, the game is sometimes a little fickle in that it will take a few tries to do so. I haven't attempted to use a controller (since I don't have one) and so cannot comment on whether or not that works.

Jjshaker000 2020-05-16 github

I am having trouble launching this game and would appreciate some help.

I am running it on ArchLinux on Steam, using proton5.0.7

The game quits immediately on launch (no window appears). I noticed that steam by default makes a 64 bit pfx, but deleting it, making a 32 bit pfx, and then installing vcrun2017 doesnt seem to help.

I also get this message while installing vcrun2017 (with winetricks)

------------------------------------------------------
Working around wine bug 37781 
------------------------------------------------------
------------------------------------------------------
This may fail in non-XP mode, see https://bugs.winehq.org/show_bug.cgi?id=37781
------------------------------------------------------
Using native,builtin override for following DLLs: api-ms-win-crt-private-l1-1-0 api-ms-win-crt-conio-l1-1-0 api-ms-win-crt-heap-l1-1-0 api-ms-win-crt-locale-l1-1-0 api-ms-win-crt-math-l1-1-0 api-ms-win-crt-runtime-l1-1-0 api-ms-win-crt-stdio-l1-1-0 api-ms-win-crt-time-l1-1-0 atl140 concrt140 msvcp140 msvcr140 ucrtbase vcomp140 vcruntime140
Executing wine regedit C:\windows\Temp\override-dll.reg
Setting Windows version to winxp
Executing wine regedit C:\windows\Temp\set-winver.reg
------------------------------------------------------
Running /usr/bin/wineserver -w. This will hang until all wine processes in prefix=/data/games/steamapps/compatdata/570940/pfx terminate
------------------------------------------------------
Executing cd /home/jshaker000/.cache/winetricks/vcrun2017
Executing wine vc_redist.x86.exe
0024:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
0024:fixme:ntdll:NtQueryInformationToken QueryInformationToken( ..., TokenElevation, ...) semi-stub
0024:fixme:ntdll:NtQueryInformationToken QueryInformationToken( ..., TokenElevation, ...) semi-stub
0024:fixme:advapi:DecryptFileW (L"C:\\windows\\Temp\\{78986A8F-AAD7-4C71-912C-5DF8A31D4556}\\", 00000000): stub
00c4:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
00c4:fixme:ntdll:NtQueryInformationToken QueryInformationToken( ..., TokenElevation, ...) semi-stub
00c4:fixme:ntdll:NtQueryInformationToken QueryInformationToken( ..., TokenElevation, ...) semi-stub
00c4:fixme:advapi:DecryptFileW (L"C:\\windows\\Temp\\{A39B0E63-0AB3-40FC-9343-74DDF511CF5C}\\", 00000000): stub
00d0:fixme:shell:SHAutoComplete stub
00d0:err:richedit:ReadColorTbl malformed entry
00d0:err:richedit:ReadColorTbl malformed entry
00d0:err:richedit:ReadColorTbl malformed entry
00d0:err:richedit:ReadStyleSheet skipping optional destination
00d0:err:richedit:ReadStyleSheet skipping optional destination
00d0:err:richedit:ReadStyleSheet skipping optional destination
00d0:err:richedit:ReadStyleSheet skipping optional destination
00c4:fixme:ver:GetCurrentPackageId (0031FE94 00000000): stub
0024:fixme:ver:GetCurrentPackageId (0031FE94 00000000): stub
------------------------------------------------------
Note: command wine vc_redist.x86.exe returned status 66. Aborting.
------------------------------------------------------

Any help would be appreciated.

I have an 4G ram, and intel integrated graphics (and have both lib-mesa and lib32-mesa installed)

OOschowa 2020-05-16 github

Why did you make a 32-bit prefix? The game is 64-bit and vcrun2017 installs just fine to a 64-bit prefix. Nuke your prefix, let steam create a new one, and try vcrun2017 again.

You also need to have vulkan-intel installed on Arch, but if you only have 4GB of RAM, chances are your intel iGPU is pretty old without proper vulkan support, which means dx11 games on proton won't work well or at all, what's your GPU model?

Jjshaker000 2020-05-16 github

I was able to make a proton log (by changing launch options to PROTON_LOG=1 %command%) (fter installing vulkan-intel, and making a 64-bit WINEPREFIX with vcrun2017 installed and it seems as though I am getting a handful of errors from steam of the form

ld.so object .... cannot be preloaded (wrong ELF class)

I later get these errors from windows: (or at least, I think windows, because the carriage returns change)

warn: D3D11CoreCreateDevice: Adapter is not a DXVK adapter
warn: OpenVR: Failed to initialize OpenVR

What would be more tests I could try, or are these symptoms recognizable at all? I do appreciate the help.

My graphics card is an INTEL HD Graphics 6000

steam-570940.log

Kkisak-valve maintainer 2020-05-16 github

Hello @jshaker000, err:vulkan:wine_vkCreateInstance Failed to create instance, res=-1 is the line of interest in your log. 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.

Does any vulkan application work on your system like vulkaninfo from vulkan-tools?

As a side note, it may be worthwhile to install the lib32-vulkan-intel package as well, but that is most likely unrelated to the issue you're seeing.

Jjshaker000 2020-05-16 github

Running vulkan tools fails for me ...

ERROR: [Loader Message] Code 0 : /usr/lib32/amdvlk32.so: wrong ELF class: ELFCLASS32
ERROR at /build/vulkan-tools/src/Vulkan-Tools-1.2.137/vulkaninfo/vulkaninfo.h:642:vkCreateInstance failed with ERROR_OUT_OF_HOST_MEMORY

I should investigate this further, as it is likely the cause of my problem ...

https://gist.github.com/jshaker000/84d7c2fe4600a34b87a55f5208e1bd1d

EDIT: Found my problem (it was actually hiding in front of me in the vulkaninfo. For some reason I had both AMD and intel vulkan installed, which confused steam. Thank you so much for the help! @kisak-valve)

Vviolet-fish 2020-10-29 github

I've tried very many things to get this game to launch and it only flashes a white screen for about 3 seconds. I'm running Arch with an Nvidia GTX 960. I'm able to play other games running vulkan and the vulkan cube demo works just fine. I've tried using protontricks to install vcrun but that doesn't seem to help.

HHasshu 2020-11-01 github

@mrlinuxfish Do you have the game installed locally?

Vviolet-fish 2020-11-01 github

It’s installed on a secondary hdd in my computer with all the rest of my games and validates fine if I check the cache files on it

HHasshu 2020-11-01 github

I see. Network-attached storage doesn't work well with Proton, hence my question.

Nnahla-nee 2021-01-21 github

I've been having problems with this game too. It used to run perfectly fine on my system but for the past couple of months, it just randomly freezes after a couple of minutes of playing (5-10 mins). currently running Linux 5.10.9, nvidia gtx 1070 proprietary driver 460.32

Aavalonv 2021-11-25 github

I'm having very severe issues with this game. For starters, on installation, the game appears to default to setting all options to "off" for some reason, which means, no sound, no HUD, etc, which at first I assumed was a bug. Controller input (DS4) seems to only work intermittently, it always picks up at the start, but it often stops working after pressing a button and after that I can only use mouse + kb.

3/4 times I've booted it has crashed while navigating the main menu. I've included a proton log of one those crashes:

wine: Unhandled page fault on read access to 0000000000000000 at address 0000000140549829 (thread 0110)
Unhandled exception: page fault on read access to 0x00000000 in 64-bit code (0x0000000140549829).
https://gist.github.com/avalonv/989338fab1844c9ee582778e716656d6

Aavalonv 2021-11-26 github

I've been able to reproduce it more or less consistently on another system (also arch linux)

The game boots fine without a controller connected. However, when a controller is connected it will crash after loading the main menu 90% of the time, other times the controller will stop working after receiving one input, and very, very rarely it will work as intended.

The only way to use a controller I found works consistently is if you boot the game without one connected, turn it on after it finishes loading the main menu, and wait a few seconds for steam to recognize it. The game will freeze for a few seconds but after that I can use the controller without any issues.

Kkisak-valve maintainer 2021-12-03 github

Dual Shock 3 no input in windows-only game

Issue transferred from https://github.com/ValveSoftware/Proton/issues/5377.
@gamendez98 posted on 2021-12-03T03:21:41:

Your system information

  • Steam client version (build number or date): steam-manjaro 1.0.0.73-1
  • Distribution (e.g. Ubuntu): Manjaro 21.2.0
  • Opted into Steam client beta?: [No]
  • Have you checked for system updates?: [Yes]

Please describe your issue in as much detail as possible:

My control(dual shock 3) is not detected by Dark Souls Remastered(proton 6.3-8) nor can I get any inputs. My control config is the default one in both the general steam config and the game.

The control works perfectly both in big picture mode and in proton-native games

Steps for reproducing this issue:

  1. Download dark souls remastered
  2. Use dual shock 3

Work-aronud

I already solved this issue for myself but I wanted to post this for feedback. I got it to work by checking only the XBOX configuration support and Guide Button focuses steam in the general steam controler configuration, and by selecting force on in the game. If this is necesary for all windows-only games(as i recall I had to do this before) why isn't this the default config.

Kkisak-valve maintainer 2022-01-12 github

Dark Souls: Remastered unable to use Dualsense controller

Issue transferred from https://github.com/ValveSoftware/Proton/issues/5492.
@Lodger posted on 2022-01-12T18:49:02:

Compatibility Report

  • Name of the game with compatibility issues: Dark Souls: Remastered
  • Steam AppID of the game: 570940

System Information

  • GPU: GTX 1080 TI
  • Driver/LLVM version: Nvidia 470.94
  • Kernel version: 5.15.11
  • Link to full system information report as Gist:
  • Proton version: 6.3-8

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.

Symptoms

I'm unable to use a Dualsense controller with Dark Souls: Remastered. These are my current controller settings:
shot-2022-01-12_13-43-11

The game behaves simply as if no controller is plugged in; no input from the controller affects the game at all, except for the touch pad, because that also controls the mouse. Portal 2 works flawlessly with the same settings (although it doesn't use Proton), so I'm certain the controller works. Enabling Steam Input in the properties tab does not fix the problem, nor does big picture mode. I haven't tested this with any other controllers because I don't have any.

Reproduction

As far as I know, just try to use a Dualsense controller with Dark Souls: Remastered.

LLodger 2022-01-12 github

When editing the controller configuration in BPM (I don't know if BPM needs to be enabled for this to work but I don't know how to edit the controller map otherwise), if I set a button to a keyboard key then the game responds appropriately. I tested this by setting the triangle button to W, and was able to get past the "press any key to start" part of the main menu. It seems like then that DSR just isn't recognizing the inputs being sent to it.

Kkisak-valve maintainer 2022-04-21 github

Dark Souls: Remastered can't be launched

Issue transferred from https://github.com/ValveSoftware/Proton/issues/5778.
@mwprado posted on 2022-04-21T20:30:19:

The last Proton version(7.0-2 and experimental) this game had been launched was 5.0-10. Running using 7.0-2 stop after few seconds. In 5.6-13 and 6.3-8 opens a window with "Preparing to launch Dark Souls: Remastered..." and no response.

My system is Rocky Linux 8.5 using steam client from EL8 fedora fusion.

Mmwprado 2022-04-21 github

5.0-10 is not working. it only worked on the first execution.
I've found:
steam-570940.zip

err: DxvkInstance: Failed to create instance
err: D3D11CreateDevice: Failed to create a DXGI factory

Mmwprado 2022-04-23 github

It works again!
It was the same problem of Jurassic World Evolution 2.
I've changed to run over wayland and installed with libvdpau and libva installed (x86_64 e i686). I've submitted another gist file with my specs.

Kkisak-valve maintainer 2022-04-24 github

Dark Souls Remastered (570940)

Issue transferred from https://github.com/ValveSoftware/Proton/issues/5791.
@Vovkiv posted on 2022-04-24T14:46:49:

Compatibility Report

  • Name of the game with compatibility issues: Dark Souls Remastered
  • Steam AppID of the game: 570940

System Information

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

Game works fine first around 15 seconds after lauched (i can interact with interface, try start new game, etc), but after that time game just crash

Reproduction

  1. Launch game
  2. Wait around ~15 seconds
  3. Crash
  1. Please copy it to your clipboard by pressing Ctrl+A and then Ctrl+C.
    Then paste it in a gist and post the link in
    this issue.

(For some reasons, ctrl+c and right click + copy don't copy anything in this window)

Kkisak-valve maintainer 2023-04-22 github

Dark Souls Remastered (570940) doesn't load in Ubuntu 23.04

Issue transferred from https://github.com/ValveSoftware/Proton/issues/6710.
@dmwest posted on 2023-04-22T12:16:49:

Compatibility Report

  • Name of the game with compatibility issues: Dark Souls Remastered
  • Steam AppID of the game: 570940

System Information

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.

Symptoms

When you try to load the game the game window starts to open and then minimises. The screen then becomes frozen and you have to kill the game window to get back to the desktop. I have tried different proton versions but this doesn't appear to make any difference.

The game was working on Ubuntu 22.10 so something must have changed in the new version.

Reproduction

Install Steam on Ubuntu 23.04 and run Dark Souls Remastered without any launch options.

steam-570940.log

VVadimKht 2024-02-13 github

i don't know where to post about it but i feel annoyed DSR won't run on proton on wayland KDE (fedora linux) (works on kde xorg). it worked on RPM but that version of steam was broken (lagging on GPU and cpu intensive when not on gpu) so i switched to flatpak. flatpak console input when entering game before instnatly closing itself at the end, is like
WARNING: discarding _NET_WM_PID 2331 as invalid for X11 window - use specialized XCB_X11_TO_PID function!

x86_64-linux-gnu-capsule-capture-libs: warning: Dependencies of libnvidia-pkcs11.so.545.29.06 not found, ignoring: Missing dependencies: Could not find "libcrypto.so.1.1" in LD_LIBRARY_PATH

fsync: up and running.
wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
Setting breakpad minidump AppID = 570940
Steam_SetMinidumpSteamID: Caching Steam ID: 76561198076547053 [API loaded no]

Game 570940 created interface STEAMAPPLIST_INTERFACE_VERSION001 / AppList
(alot of created different interfaces)
Game 570940 method call count for IClientUserStats::RequestCurrentStats : 1
(few of these for different method calls)

Uploaded AppInterfaceStats to Steam
[2024-02-13 23:58:01] Background update loop checking for update. . .
[2024-02-13 23:58:01] Checking for available updates...
[2024-02-13 23:58:01] Downloading manifest: https://client-update.akamai.steamstatic.com/steam_client_ubuntu12?t=1979362066
[2024-02-13 23:58:01] Manifest download: send request
[2024-02-13 23:58:02] Manifest download: waiting for download to finish
[2024-02-13 23:58:02] Manifest download: finished
[2024-02-13 23:58:02] Download skipped: /steam_client_ubuntu12?t=1979362066 version 1705108172, installed version 1705108172, existing pending version 0
[2024-02-13 23:58:02] Nothing to do

it doesn't seem to even output error. it says it works fine. does anyone have similar issue? how'd you fix it?

Kkisak-valve maintainer 2024-05-18 github

[BUG] Dark Souls: Remastered visually freezes but everything else works

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7744.
@sudoharun posted on 2024-05-18T09:24:13:

All Proton versions

Video:

https://github.com/ValveSoftware/Proton/assets/123123333/f15b2381-ab12-4584-9fd7-dcbd436a9325

Steam log:
steam-570940.log

Kkisak-valve maintainer 2024-05-18 github

Hello @sudoharun, it might be worthwhile to also mention your issue to your video driver vendor.

Ssudoharun 2024-05-18 github

I made an issue recently on the DXVK github, since the errors I were getting in the logs were related to that here: https://github.com/doitsujin/dxvk/issues/4009

Aaaronrudkin 2024-09-06 github

I am having a reliable crash to desktop 100% of the time when launching this game on Steam Deck LCD. I've attached a log, the only two things I see are EDID / resolution reporting issues (which I think are benign, and also I've tried forcing resolutions externally) and then eventually it hits a page fault but I can't make sense of where to go from there.

To be clear, no one else is having this problem so I suspect I'm hitting an edge case hardware failure and I need to RMA.

On boot, I get through the game logos, and the CTD happens within about 10 seconds of being on the main menus. If I try to mash through the menus to get to New Game it will crash before I get through character creation. If I just sit on the menu without input it will also crash. When the crash occurs, audio continues but the window stops updating and no longer receives any input. After about 3-4 seconds in the hung state the windows closes and returns me to the game in my Steam library. I do not receive any visual errors.

Assume I have tried everything a regular user can try: switching between stable OS and beta, trying 6 different versions of proton (8.x, 9.x, experimental, experimental bleeding edge, GE 8, GE 9), toggling steam overlay, toggling refresh rate and resolution forcing, toggling TDP limits and shading settings, launching in desktop mode, reimaging the Steam deck, resetting the BIOS, launching offline and online, launching online and setting the game to offline, installing on internal storage versus SD, verifying install files, uninstalling and reinstalling, turning off Steam Cloud, nuking saves and starting from scratch, rebooting, shutting down and cold booting, uninstalling Decky Loader, waiting a few days and trying again. I also tried using protontricks to emulate virtual desktops. Someone asked whether I had undervolted (no). The one way in which the Deck is non-standard is that I swapped eMMC storage for an NVMe, but again the crash still happens when launching from SD.

I have not had non-standard issues with any other game on Steam deck. I have already posted on the Dark Souls Remastered Steam forum (no help), the Steam Deck forum (no help), and contacted Steam Support (4 replies, 2 of which asked me whether I'd done the things I had already listed myself as trying, and 2 of which seemed to think I was requesting the compatibility rating of the game be changed, which is not what I'm requesting).

I'm virtually certain this is an edge case hardware failure in my deck with either the RAM or VRAM. I have not run a memtest yet because I'm not really sure the right way to proceed. Hopefully someone can check out my crash dump log and see if there's anything else I should try:

steam-570940.log

Thanks!

Kkisak-valve maintainer 2024-09-24 github

Dark Souls Remastered refuses to launch: "not enough RAM" while I do have enough RAM

Issue transferred from https://github.com/ValveSoftware/steam-for-linux/issues/11292.
@PimpOfSune posted on 2024-09-24T13:46:40:

Your system information

Please describe your issue in as much detail as possible:

Honestly, I don't know where should I go with this problem.
Communication with Bandai Namco's Customer Support is stuck at "send us DxDiag or go away" phase.
Support of Steam itself tends to route all mentions of Linux towards Steam-for-Linux issue tracker (<- we are here).
So... d'oh...

Long story short, Dark Souls Remastered have 6GB RAM listed in its minimal system requirements at https://store.steampowered.com/app/570940/
My Lenovo L340-15API is guaranteed to have at least 6GB of RAM available as RAM (other 2GB are dedicated to Vega 8 Mobile GPU's needs).
But, apparently, MY 6GB of RAM is not enough for Dark Souls Remastered as it refuses to launch with
"The system does not meet the minimum memory requirement to run the application"
error message.
Screenshot from 2024-09-24 16-40-00
The game don't even attempt to create its files in prefix's documents and/or appdata.

I... don't know what to do in this case.
The last (and the only, in 20+ years) time I've seen stuff like this - in Hand of Merlin - the check was implemented by a mentally healthy developer, so if the check was failed - the game'll ask "are you sure?" and if you sure - will proceed running anyway.
Apparently, this practice is not modern enough for a more popular game from a better known worldwide company.

Steps for reproducing this issue:

  1. Have a laptop with exactly 6GB RAM available
  2. Install DS:R through Linux variant of Steam
  3. Try to run, see the error
Wwantija 2025-01-03 github

Very odd issue I was having, the game will crash usually within 5 minutes of playtime or shorter, the workaround is to use gamescope or reduce the processes niceness. I tried -15 and that seemed to work, gamemode should do the trick for niceness.

Bbraiam 2026-01-09 github

Anyone having trouble with rebinding controllers in the game? Rebinding a button to another action and using it, will do both actions instead when using a separate controller.

Bbraiam 2026-01-09 github

Ok, Darksouls have a problem where A and B (WEST/SOUTH) buttons can't be remaped in any capacity:

The game has issues with swapping the A and B buttons in any capacity. Swapping the Confirm and Cancel buttons to Japanese style doesn't function as intended. Swapping Roll and Interact doesn't function as intended.

https://www.pcgamingwiki.com/wiki/Dark_Souls_Remastered