search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.63k stars 1.07k forks source link

Dark Souls II: Scholar of the First Sin (335300) #137

Open liamphmurphy opened 6 years ago

liamphmurphy commented 6 years ago

The DX11 version of Dark Souls 2 works out of the box, videos, sounds (even the grass!)

OS: Arch Linux GPU: NVIDIA GTX 1070 Driver: 396.51

Out of the box Proton 3.7 configuration.

jtfen86 commented 6 years ago

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.

liamphmurphy commented 6 years ago

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.

Brisse89 commented 6 years ago

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

Brisse89 commented 6 years ago

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.

JazzGlobal commented 6 years ago

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.

Glog78 commented 6 years ago

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

testing with default (DXVK)

testing with PROTON_USE_WINED3D11=1 %command%

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

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

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

jtfen86 commented 6 years ago

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. ;[

JazzGlobal commented 6 years ago

@BrosephJ

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

JazzGlobal commented 6 years ago

@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.

kisak-valve commented 6 years ago

Hello @BrosephJ, @JazzGlobal, https://github.com/denilsonsa/udev-joystick-blacklist may be worth looking into.

ghost commented 6 years ago

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! :)

Brisse89 commented 6 years ago

@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?

liamphmurphy commented 6 years ago

@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.

JR1994 commented 6 years ago

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

ghost commented 6 years ago

@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?

ghost commented 6 years ago

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

aboutafter commented 6 years ago

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/"

HonkingGoose commented 6 years ago

Compatibility Report

System Information

I confirm:

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:

Game feature Works Remarks
Introductory logos Yes ...
Skipping introductory logos Yes ...
Game launches to main menu Yes ...
Playing the game Yes Seems to work just fine for me, performance is good.
In-game textures/effects Yes This seems to work fine, I haven't seen anything odd.
Online connectivity Yes Both summoning people + getting summoned + getting invaded.
Did not test: invading people.
Cut-scene after starting new game Partially Subtitles show, no sound, no music, no graphics.
In-game in-engine cutscenes before boss fights Yes ...
Getting new achievements Yes ...

Controller support for Xbox 360 controller:

Function Works Remarks
Controller input recognized Yes Input is quick and precise, no issues here for me.
Vibration Yes ...
Proper in-game controller prompts Yes ...
meowmeowfuzzyface commented 6 years ago

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.

Veske commented 6 years ago

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

meowmeowfuzzyface commented 6 years ago

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.

kisak-valve commented 6 years ago

Scaling issues in Dark Souls II: Scholar of the First Sin (335300)

Issue transferred from https://github.com/ValveSoftware/Proton/issues/1953. @rihardsk posted on 2018-11-11T22:48:50:

Screen scaling is broken for all resolutions except 1280x720 in windowed mode:

The issue is worse if i use a 1920x1080 external monitor (instead of the 1366x768 builtin display of my laptop).

I'm running the game with these options:

PROTON_USE_WINED3D11=1 optirun %command%

Here's the log: steam-335300.log

Here's my system's info. What's missing there is that i have a dedicated GT530m GPU on which i'm running the game using bumblebee.

I haven't tested other games on Steam Play so i'm not sure whether the issue is exclusive to Dark Souls 2 or not.

rihardsk commented 5 years ago

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.

Selhar commented 5 years ago

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.

tsreaper commented 5 years ago

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.

andreldmonteiro commented 5 years ago

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.

Unaccounted4 commented 4 years ago

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!

20201015231959_1

HonkingGoose commented 4 years ago

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.

thaewrapt commented 3 years ago

Intro video is now playable with Proton Experimental.

LaurentOngaro commented 3 years ago

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 ?

thaewrapt commented 3 years ago

@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).

LaurentOngaro commented 3 years ago

@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

thaewrapt commented 3 years ago

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.

LaurentOngaro commented 3 years ago

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

kozross commented 3 years ago

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.

duartec3000 commented 2 years ago

@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.

r2rX commented 1 year ago

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.

kisak-valve commented 1 year ago

Dark Souls 2 SOTFS - Intro video not working ("Verified" status)

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7189. @X6205 posted on 2023-10-23T07:54:10:

Compatibility Report

System Information

Symptoms:

Game has "verified" status, but intro video is not playing on Proton 8.0-4. Only placeholder image with colored squares is shown instead of video. Otherwise game looks to be working. (With Proton GE is intro video working properly).

kisak-valve commented 6 months ago

DARK SOULS™ II: Scholar of the First Sin (335300) - Debug menu mod can't be opened via keyboard shortcut, but controller shortcut works fine

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7750. @Vinjul1704 posted on 2024-05-19T12:04:58:

Compatibility Report

System Information

I confirm:

Proton log: https://gist.github.com/Vinjul1704/abaa58416b89633f2550509d3d8dd601

The log had about 408 million lines of "trace:seh:__processing_throw ()" in the middle, which I removed in order to not send a 2 GB large log file. If you want me to upload the full log regardless to check if there might be something there, please let me know.

Symptoms

When using the following debug menu mod for testing and speedrun routing, the keyboard shortcut to open it (F10 by default) doesn't work, but the controller shortcut (L3 + Start) works fine: https://github.com/LordRadai/DebugManager-v2.0-Release

When asking the mod author how the keys are checked, their response was that "GetAsyncStateKey" is used with the released flag.

I hope it's fine to report issues with mods like this here. If it isn't, I apologize.

Reproduction

Install debug menu mod -> Set appropriate dinput8.dll override -> Launch game -> Press F10 -> Nothing opens