I just tested this! Only, my camera controls are broken and there is a constant "holding up and left" going on. When I click away from the window it stops but camera control only works via the default keybindings on my keyboard.

After looking at the linux_gaming reddit, sounds like there may be issues with keyboards as you say. With my Xbox One controller I haven't had issues.

Spent several hours playing this yesterday. With DXVK it hangs at launch, but it plays fine with the following start parameter.
PROTON_USE_WINED3D11=1 %command%

I've previously played it on upstream Wine-development 3.13 with DXVK 0.70 which worked and had better performance.

Debian Sid
GNOME 3.28 (Wayland session)
Mesa 18.1.6
LLVM 6.0.1
Ryzen 1700X
32GiB DDR4-2400
2x R9 Fury

Switched from Wayland to x.org and DXVK works fine on x.org. I did not have this issue on upstream Wine, but I do remember the game would not go fullscreen with upstream Wine+DXVK running Wayland.

Cutscenes do not show for me and I have input issues. The game seems to have a constant thumbstick input making it impossible to control the character.

Systeminformations -> http://termbin.com/rdxl

testing with default (DXVK)

• game starts
• no sound and movie in intro instead black screen with subtitles
• game rendering was fine on high
• rumble seems not to work

testing with PROTON_USE_WINED3D11=1 %command%

• game starts
• intro was completly skipped
• game rendering was fine on high
• rumble doesn't work

additional informations:
mplayer -> http://termbin.com/dykx

• sound and video fine

gstreamer -> gst-launch-1.0 -v playbin uri=file:///opt2/SteamLibrary/steamapps/common/Dark\ Souls\ II\ Scholar\ of\ the\ First\ Sin/Game/movie/prologue.wmv >log_gst64.txt -> http://termbin.com/5x57

• video plays but sound broken

vainfo -> http://termbin.com/ityl
vdpauinfo -> http://termbin.com/b5gp

Solved my issue with there being a constant "up and left" it was my Corsair M65 mouse. When plugged in by default it's detected as a gamepad (seen through jstest-gtk) after installing ckb-next (iCUE type drivers for Linux) the problem went away.

@JazzGlobal Do you have a Corsair mouse?

Edit: But now I have another problem when the game loses focus my mouse won't move the camera anymore. ;[

@BrosephJ

Yes I do. I'll test this later today!

@BrosephJ This didn't work for me. My mouse is the culprit, as you said. If my Corsair mouse is plugged in during game start (This goes for a number of games included DS2 and DBZ Xenoverse 2) then the input bug will happen. I have a wireless mouse so, for now, that will have to work.

Thanks for the suggestion.

Hello!
Tested with Proton 3.7-3 and got significantly lower performance (30-33fps) compared to built wine-staging 3.13 with DXVK-0.70 (Solid 60fps). So still some work to do! :)

@HikloLime
I'm getting a solid 60fps when using DXVK.
Have you verified that DXVK is being used and not wined3d11?
Also, what sort of hardware is it running on?

@HikloLime

I concur with Brisse89, it's been running very well under DXVK.

I would also check you have up to date drivers, and just in case, the proton 3.7-4 beta is worth a shot.

The opening is blank with subtitles but so far the rest of the game plays

@Brisse89 The latest Nvidia 396.54 drivers, and FPS was read from the DXVK HUD, so DXVK is fine. Could the difference e because I built wine-staging myself?

@murnux tried using the proton 3.7-5 beta, and the FPS was a solid 60!! Hallelhujah!

The game would be "Platinum" tier for me if it wasn't for the intro cinematic not reproducing,

The video that doesn't play is prologue.wmv on "/steamapps/common/Dark Souls II Scholar of the First Sin/Game/movie/"

Compatibility Report

• Name of the game with compatibility issues: Dark Souls II: Scholar of the First Sin
• Steam AppID of the game: 335300

System Information

• GPU: Nvidia GTX 780 Ti
• Driver/LLVM version: Nvidia 396.54
• Kernel version: 4.15.0-34-generic
• Link to full system information report as gist
• Proton version: 3.7-6 Beta

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.

Proton log:

steam-335300.log

Steps to reproduce log:

1. Start game.
2. Press new game.
3. Intro movie "plays", subtitles show but no sound, no music, no graphics.
4. Skip movie.
5. Go back to menu.
6. Quit game.

Test report:

Controller support for Xbox 360 controller:

Dark Souls 2 (and 1 and 3) 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.

UPDATE: Downgrading to mesa 18.2.2 solved this issue. It seems it's a problem with mesa 18.3.0.

With 3.16-4 I can launch this game only when using system native libraries. With steam runtime this game will not even launch.

The game works overally very nice with native libraries but I can never alt-tab out of the game. Alt-tab will make the camera un-movable with a mouse for some reason. I can still move around with keyboard and theoretically could move the camera using keyboard shortcuts.

I am running the expansion pack of the game: Dark Souls 2 - Scholar of the first sin. The vanilla version ran fine for me as well and had the same alt-tab issue. Will also say that the Steam controller does not work with this game for some reason. Can use steam controller in Big Picture to launch the game but the controller inside of the actual game will not take effect.

My system info: https://gist.github.com/Veske/573cdb6fa3f90a356460ee9b1c312d31

Hey @Veske if you set a shortcut for "show desktop" such as Alt + D or something like that, you might be able to get the game out of that locked window, and then Alt + Tab should work. This is what I've been doing as a workaround for Alt + Tab not working.

The above issue was caused by Bumblebee somehow messing things up. After I switched to using nvidia-xrun instead of Bumblebee, Dark Souls works fine in full screen. I've yet to try other resolutions than my laptop's native one but i expect it to be only a matter of configuring Xorg and/or Openbox.

I'm having the same exact issue as @BrosephJ (up and left keys are constantly "pressed", making it impossible to play), however updating the drivers didn't help. Did anyone successfully fix this? Everything else seems to work fine out of the box.

I'm having the same exact issue as @BrosephJ (up and left keys are constantly "pressed", making it impossible to play), however updating the drivers didn't help. Did anyone successfully fix this? Everything else seems to work fine out of the box.

I'm faced with the same issue. It's because Linux is mistakenly regarding some devices as joy sticks. If you go into /dev/input you will see a device called "js0" (or "js" + other numbers). Just remove this device, or use this https://github.com/denilsonsa/udev-joystick-blacklist.

I'm having a really bad hard freeze that requires a hard reset of the system after sometimes clicking on the windows button on proton 4.11-7.

So I decided to try 5.13-1 for all it's video playback claims with the original Dark Souls 2. It's trying, poor thing!

Those weird colored bars are actually a sign of progress!

https://github.com/ValveSoftware/Proton/issues/1464#issuecomment-710094016

We put in a bunch of work improving quartz video between 5.0 and 5.13, so some games may start working (I don't have specific titles, sorry). If you see a color bars pattern appearing now, that's an indicator of our work on certain codecs. You will hopefully see the real video instead of those color bars very soon.

Intro video is now playable with Proton Experimental.

The game works well under Arch Linux with proton 5.13-6 even the intro video is playing fine
But I still have an issue after the game windows has lost focus (for instance when using alt-tab ): the camera become un-movable with a mouse (but I can still move around with keyboard)
Restoring focus or Leaving the running game does not solve the issue. I must totally quit DS2 and relaunch it to restore the camera movement with the mouse.
Very Very annoying !
I've played Dark Souls and Dark souls 3 in same conditions (Arch Linux with steam and proton) without this issue.
I read in a forum that it could be solved by changing some wine settings (using virtual desktop with mouse focus). But I can see how to do that with a game using proton 5.13-6

Can anybody help me ?

@LaurentOngaro sadly, it's a known issue, I haven't tried this particular workaround yet but maybe you can find it useful: https://github.com/ValveSoftware/Proton/issues/137#issuecomment-435492997

If you'd like to go with virtual desktop, you should run winecfg through protontricks and configure it there (or do it via a command line as winetricks can switch those settings as well).

@thaewrapt Thanks for your help.
I installed protontricks and created a new wineprefix, but I don't understand how I can choose a given Wineprefix (with custom settings) when launching DS2 from Steam (or even from a terminal). Do you know how I can do it ?
I will be desperate to play DS2 on Windows

I installed protontricks and created a new wineprefix, but I don't understand how I can choose a given Wineprefix (with custom settings) when launching DS2 from Steam (or even from a terminal). Do you know how I can do it ?

What you need is described here: https://github.com/Matoking/protontricks/blob/master/README.md#usage. First example will give you an AppID of the game (which is anyway in the title of this particular GitHub issue right now, 335300). The second form will give you an ability to run winetricks on the SotFS prefix, with <ACTIONS> being the same you are normally doing with a command winetricks <ACTIONS>. I recommend googling for protontricks examples if it still makes a little sense to you.

Thanks for your answer.
I understand the command line options and the AppID.
Anyway It's not totally clear for me, but I understand the great lines. I presume I've to RTFM.
But I'm not sure that changing wine settings can solve this issue. It will probably be a waste of time.
I should have to play DS2 under Windows

I am getting an issue where, upon reaching the point in the game where you have to input your name, no keyboard input gets accepted. Furthermore, no matter what I press, I cannot proceed.

@LaurentOngaro @Veske After extensively searching the web for a solution to the ALT+TAB mouse camera issue this thread is the only place where I could find any info that lead me to a solution.

Without any further ado the solution is to set a virtual desktop with the native resolution of your monitor in winecfg.
The easiest way of doing that is:
Run in the terminal protontricks 335300 --gui
Select the default winprefix > Run winecfg > Graphics > Check Emulate a virtual desktop > Insert your resolution > Apply and OK.

I'm sorry for the bump to such an old thread but this issue is game-breaking and very specific to the linux gamer community, this post might help another lost soul out there.

The intro video seems to not display properly with Proton Experimental - Bleeding edge (as of writing this). Video playback showed the placeholder T.V broadcast image but the subtitles and audio were presented properly.

Running Steam v1689034492 with Mesa 23.3.0-git & RX 6800M.

@Ynverxe mouse cursors is fine for me on kde plasma wayland both in the menu and when ingame, camera movement seems fine as well. It's possible related to hyprland's implementation of wayland.

@Ynverxe mouse cursors is fine for me on kde plasma wayland both in the menu and when ingame, camera movement seems fine as well. It's possible related to hyprland's implementation of wayland.

I was using KDE. I have Hyprland installed but I wasn't running it.

@Ynverxe what plasma version are you using? I'm on 6.3.5. Tried with 2 different mice + a dualsense controller, the first mice I used wired and wireless, the second wired, and dualsense wired (using the trackpad), and they were all fine. I tried with the game windowed and also fullscreen at native and lower than native resolution.

@Ynverxe what plasma version are you using? I'm on 6.3.5. Tried with 2 different mice + a dualsense controller, the first mice I used wired and wireless, the second wired, and dualsense wired (using the trackpad), and they were all fine. I tried with the game windowed and also fullscreen at native and lower than native resolution.

Sorry for the delay. The incompatibility wasn't DS2, it was the LightningEngine mod which caused that visual bug on Wayland. Just switched to x11 again because I understand the problem is caused by 3rd party software.

@Ynverxe Do you mean this mod? https://www.nexusmods.com/darksouls2/mods/1146?tab=description I was able to use it normally, no flickering mouse on my end, at least with its default settings. I was able to verify the mod was loaded and working thanks to the F1 interface and playing around with the illumination and antialiasing options

@Alexandr-Dimitrov the issue is likely on your end as it's working fine here, as well as seemingly most people over protondb https://www.protondb.com/app/335300 . I got to the forest of fallen giants where I idled for half an hour and there was no disconnection at any point with proton experimental.

Also note that this issue tracker is for upstream proton, even if you see the same symptoms with GE's proton that doesn't mean the logs will be the same, so avoid using it to collect logs.