search

ValveSoftware / Proton

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

Castlevania Lords of Shadow 2 (239250) Black shadows glitches in ingame cutscenes #760

Open Zero86Sk opened 6 years ago

Zero86Sk commented 6 years ago

Game runs flawelssly and CG cutscenes too.

But during the Ingame cutscenes there is this black mass that is blocking characters and the enviroment from appearing. Interesting that the 1st cutscene is fine its the fight after the 1st boss fight this stared to happen.

Tested with Proton 3.7.4 beta I tried to run it with PROTON_USE_WINED3D11, PROTON_NO_D3D11, and PROTON_NO_ESYNC No change.

My Steam info: https://gist.github.com/Zero86Sk/d629f657c1ae861c36657cdf238a7765

Here are a few Screenshots:

snimka obrazovky z 2018-08-27 18-32-56

snimka obrazovky z 2018-08-27 18-33-08

snimka obrazovky z 2018-08-27 18-33-24

snimka obrazovky z 2018-08-27 18-35-03

snimka obrazovky z 2018-08-27 18-45-24

snimka obrazovky z 2018-08-27 18-44-57

DanMan commented 6 years ago

Just tried the demo and after turning down depth of field in the graphics options, the black areas disappeared. Nothing else was changed after installation.

nelsam commented 6 years ago

I can launch and play the game (with some flickering and whatnot) with proton 3.7-8 (and 3.7-8 beta); but with proton 3.16-3 beta, it hangs at the loading screen just after the intro videos.

kisak-valve commented 6 years ago

Hello @nelsam, 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. Additionally, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

nelsam commented 6 years ago

I had a weird problem reproducing the problem this morning. My best guess is that the game was still using proton 3.7-8 beta even though 3.16-3 beta showed as the version in use in my Steam Play settings - probably just a UI hiccup? I certainly don't remember switching back to 3.16-3 beta last night. It was a surprise that it was selected this morning.

Anyway, I switched to 3.7-8, then switched back to the 3.16 beta (which is now 3.16-4 beta) - and the issue is back.

system info: https://gist.github.com/nelsam/3238c7e9728495bf02a46e9f99e58e96 log file: steam-239250.log

I let it run for ~30 seconds before killing it (side note: it ignores kill -15 and I have to use kill -9). Let me know if more or less time would be helpful.

jonlap commented 5 years ago

This game works flawlessly with Proton 3.7-8 on my system but it seems it's borked on Proton 4.2. I did not test with 3.16. Looking at protondb, there are two reports with similar setup I have, that have the same issue: game crashes to loading screen when starting new game. Log of the crash with 4.2-9 here.

fsyy commented 5 years ago

i had those glitches too, after some fiddling around with proton versions, i deleted the prefix (i lost my savegame, be prepared) and started with proton 3.16-9 and the following launch option: PROTON_USE_WINED3D=1 %command% now it works without any problems. i played around 2 hours at once now.

DanMan commented 4 years ago

It runs for me with 4.11-9, but there are some rendering artifacts now (green and/or opaque god rays), some missing effects (no tail when he lashes out at enemies) and it seems like the Depth of Field (DoF) "high" setting is no different from medium (the only other setting apart from "off").

D9VK works better: there is a tail when slashing, and the god rays at the start aren't green/opaque. But DoF set to high doesn't look any different from medium. The effect is clearly different on Windows though.

Vladimir-A commented 4 years ago

System Information

Symptoms

The game starts and freeze on "Loading", and I can only kill the process.

upd

Works fine with proton 5.0-1.

shoober420 commented 4 years ago

Compatibility Report

System Information

LOG: steam-239250.log

Symptoms

Crash at launch, no window

kisak-valve commented 4 years ago

@shoober420, same assessment as https://github.com/ValveSoftware/Proton/issues/764#issuecomment-600590478.

shoober420 commented 4 years ago

Compatibility Report

System Information

LOG: steam-239250.log

Symptoms

Game runs, but crashes when changing resolutions. Upon launching the game again, resolution change is not saved.

kisak-valve commented 4 years ago

Hello @shoober420, does running the game with PROTON_USE_WINED3D=1 avoid the resolution change crash?

shoober420 commented 4 years ago

@kisak-valve Using "PROTON_USE_WINED3D=1" does fix the issue.

WINED3D LOG: steam-239250.zip

iWeaker commented 3 years ago

It is an internal problem of Wine or for a specific patch, I have that problem when I change the resolution with all versions of PROTON (Proton 5.13 or Experimental) but with Proton GE 6.1 it does not happen, it changes resolution without any problem.