ValveSoftware / Proton

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

Shadow of the Tomb Raider (750920) #1417

Open NTMan opened 6 years ago

NTMan commented 6 years ago

Compatibility Report

System Information

I confirm:

steam-750920.log

Symptoms

1) Low FPS on 4K normal preset (20-30 FPS) screenshot from 2018-09-12 21-35-55

2) Random crashes when I launch the game.

Reproduction

1) Launch the game. 2) Select "New Game" 3) Select difficulty level 4) Wait while loaded first level

Gameplay video

https://youtu.be/lVjLifLc2g0 https://youtu.be/mCZK73dmJzg

screenshot from 2018-09-12 23-38-38

screenshot from 2018-09-12 23-38-59

kakra commented 6 years ago

@NeptNutz Does it crash in wineserver for you? I'm inspecting a crash with my own build here and as far as I can tell it's not related to the patches I added. You should be able to look at dmesg to quickly find which process crashed lately. If that process crashed, you may need to manually clean up the exe files still running: pkill -9 .exe.

kakra commented 6 years ago

@NeptNutz I fixed it by reintegration the esync patches. So your crash is probably unrelated because the reintegration is needed only for wine-3.19 master.

berglh commented 6 years ago

Anyone experiencing this problem with nvidia 410.73 driver? I had to manually install it on Ubuntu 18.10 and remove other 396 components. I'm interested in this game on Proton when all bug are addressed.

mati865 commented 6 years ago

410.73 doesn't change much for Vulkan. 396.54.09 is still the best bet.

niedz., 11 lis 2018, 05:33: Berg Lloyd-Haig notifications@github.com napisał(a):

Anyone experiencing this problem with nvidia 410.73 driver? I had to manually install it on Ubuntu 18.10 and remove other 396 components. I'm interested in this game on Proton when all bug are addressed.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/1417#issuecomment-437643182, or mute the thread https://github.com/notifications/unsubscribe-auth/ABHsdo6lytf2l5RtGPIPD5TTWGH0hEZpks5ut6iagaJpZM4WlyFV .

ncoder-1 commented 6 years ago

linux 4.19.2 (archlinux) nvidia 415.18-1 and both Proton 3.16.4-BETA and 3.7.8

Sometimes crashes and sometimes I get a black screen after this screen (sound works, can hear birds and animals):

screenshot from 2018-11-17 15-44-46

kakra commented 6 years ago

Neither 410 nor 415 support all the features that DXVK currently needs. You should stick to the Vulkan beta driver currently until NVIDIA integrated the new Vulkan API functions into the mainline driver.

NextGenRyo commented 6 years ago

Hey All, Quick question. What fps do you all get? I get around mostly in the 30s give or take. My graphics card is a GTX 970 if that has anything to do with it and settings in game are medium even with low the fps is the same. CPU is an i7. The FPS can also drop to like 15 for a few secs. dxvk 0.92 Nvidia drivers: 410.73

To get rid of the black flashy textures we gotta turn off Ambient Occlusion, Motion Blur and Screen Space Reflections. As far as I know turning even one of them on will bring back the flashy textures.

Any one have any ideas on the fps issue? I'm sure the game can be played with my graphics card. Other than that game is running great. Even playable.

doitsujin commented 6 years ago

CPU is an i7

If it's a 10-year old i7 then it would naturally struggle, this game is extremely CPU-intensive.

NextGenRyo commented 6 years ago

Its Intel Core i7-6700 @ 8x 4GHz as far as i know its 3 years old, thats what the wiki says.

kakra commented 6 years ago

An i7-3770K here, so it fits the 7 year old bill. I also get around 30 fps but CPU and GPU are both underutilized (GTX 1050 Ti 4GB). So there's probably still sync issue between threads.

mati865 commented 6 years ago

Even on Windows with DX11 this game performs poorly, it can utilize only 4 threads and quickly becomes CPU bound. This game is really meant to be played on DX12 but vkd3d isn't mature enough yet.

NextGenRyo commented 6 years ago

@kakra When you mentioned the word SYNC i thought about enabling esync that seemed to have worked on one bit...when the game loads (loading screen before mission) I now get around 200-300 fps as before it was around 50 to 70 at that bit. Still in the 30s though in game play.

Maybe that gives some one more ideas.

mati865 commented 6 years ago

@mixalis1987 what is your OS? Logs could also help, see here how to obtain them.

Could you post in-game benchmark results as well? My results on R7 2700X + GTX 1080, Nvidia 410.73, max settings (there are artefacts visible) and SMAAT2x: https://imgur.com/a/MFPeSM8

NextGenRyo commented 6 years ago

@mati865 hmm it might be my GPU in the end might not work well with the nvidia drivers for this game. On windows I did a benchmark with the same settings "medium" the game recommended High but I thought I would try medium anyway and I got 63 fps at the end. On linux same settings I got 32 fps. In a lot of videos on the net the only difference I can see is that they are running a GTX 1080. Tried taking a screenshot but all that came out was a black picture. Oh and lowest settings on linux I got 50 fps but still had heavy drops when actually playing.

This is what gave me the tip on the GPU: https://steamcommunity.com/app/750920/discussions/0/1734342161855349063/

My OS is Manjaro 18.0 Kernel: 4.19.2-1-MANJARO Desktop Environment: xfce4 Ram: 16GB

mati865 commented 6 years ago

@mixalis1987 are you using Exclusive Fullscreen setting? Maybe the compositor is misbehaving.

What is your output of ulimit -Hn command?

Are you CPU or GPU capped during the benchmark (you can take a picture with your mobile). Could you also try another demanding game? It could be the issue with GTX 970 infamous 3.5GB "bug".

NextGenRyo commented 6 years ago

@mati865 No Exlusive Fullscreen is off.

The ulimit -Hn command gives 1048576

20181120_172110

Turning off shadows does give a boost of about 10 fps but the game looks really bad. Never heard of the graphics bug, shame don't have a higher card to test. But why then does it run better on windows OS?

kisak-valve commented 6 years ago

@mixalis1987, @mati865 is referring to a marketing miscommunication around the release of the GTX 970. Here's a random article from around that time: https://www.pcworld.com/article/2888877/its-a-feature-not-a-flaw-nvidia-ceo-addresses-geforce-gtx-970s-memory-spec-fiasco.html

NextGenRyo commented 6 years ago

@kisak-valve Thanks for the info. So its a feature and not a bug, but why then the difference in fps with windows and linux, it must be with the drivers then?

mati865 commented 6 years ago

@mixalis1987 your CPU is unbelievably underperforming. Those figures would be right for something like i3 or Pentium but definitely not for your i7. Exclusive Fullscreen causes game to hang when minimizing but improves performance, you should try it. Another thing to try is changing CPU scheduler to performance (or pstate-performance for Intel).

I thought DXVK could be allocating so much memory it hits that slow 0.5GiB part but it's not the case. Nvidia released driver update to make applications less likely to allocate that 0.5GiB and I was wondering if it works with lower level stuff like DXVK.

NextGenRyo commented 6 years ago

@mati865 How do I change CPU scheduler to performance? Also it looks like enabling Exclusive Fullscreen did help.. a bit. With that on game did feel a bit smoother, still fps is around 45 though. That's with shadows set to low.

Why would the CPU under perform so bad? In task manager the cpu shows like 1-4% when i'm like browsing or something.

I figured the command to max CPU, it is cpupower frequency-set -g performance but it only helped a little bit.

mati865 commented 6 years ago

@mixalis1987

cpupower frequency-set -g performance
NextGenRyo commented 6 years ago

@mati865 Thanks, yea did that. Edited my previous post 20 minutes ago.

HonkingGoose commented 6 years ago

For reference: Feral Interactive are working on a Linux port of Shadow of the Tomb Raider.

From gamingonlinux.com:

Originally published by Square Enix and developed by Eidos-Montréal, Feral Interactive confirmed today that Shadow of the Tomb Raider is officially heading to Linux in 2019.

mati865 commented 6 years ago

@mixalis1987 if it's with ESYNC then I have no idea what could cause that bottleneck. There could be something useful in the logs, here are instructions how to obtain them: https://github.com/ValveSoftware/Proton#runtime-config-options

NextGenRyo commented 6 years ago

@HonkingGoose Yea I noticed that this morning, good peace of news. But no official release date could be end of 2019 haha. @mati865 Honestly I have no idea I honestly think it's the GPU, it's getting old but I got it to a playable state. In caves and tombs its actually pretty smooth, the major drop in fps is in towns but you can still run around and do your business so for now I guess I'll have to make do with that and keep randomly checking for solutions.

It's hard to diagnose if it is the card because every one I see is playing on a gtx 1080 or more. I was planning on upgrading soon anyway so we will see.

mati865 commented 6 years ago

In caves and tombs its actually pretty smooth, the major drop in fps is in towns

This and graphs you uploaded previously strongly indicate the CPU is holding back. It can be driver bug or whatever else but in the end CPU either cannot keep up or is not utilized properly.

NextGenRyo commented 6 years ago

So do I need new CPU or do we have some kind of settings we can play with? I already set the power to max performance from the command provided.

I also set the performance to max for the GPU in the nvidia control panel.

mati865 commented 6 years ago

You said it's working fine on the Windows so it's not hardware issue.

You could run in the terminal this command:

while true; do (echo "%CPU %MEM ARGS $(date)" && ps -e -o pcpu,pmem,args --sort=pcpu | cut -d" " -f1-5 | tail) >> ps.log; sleep 5; done

And run around the city for about 1-2 minutes to get some data.

NextGenRyo commented 6 years ago

OK my new graphics card came today and I thought I would test it out...obviously. Indeed when changing the card it did help with the FPS on this game. I got up to 75 in towns as before I was getting 15, 25 - 30 ish. I am getting 90 to almost 150 outside of towns. I still set the CPU to performance and I also set the card to max power usage to help. without those settings I got around 40 - 50 in town still good. The card I got is GTX 1080 ti. So my theory was right.

NextGenRyo commented 5 years ago

My OS updated today and it had the latest nvidia drivers and vulkan for manjaro. Tested the game and I was getting amazing FPS up to 150 on ultra settings and around 70 in towns. We still got the flashing black skin though with the two settings mentioned previously set on. No big deal.

Jo3yization commented 5 years ago

Just sharing since I stumbled upon this & it might provide useful.

Look at the DX11 frame latency & CPU clockspeed in the benchmark, then look at DX12. September Benchmarks: https://youtu.be/9OKVPIOxtMY December Benchmarks(Same problem still there: DX11 vs DX12: https://youtu.be/Am8951dIL8c

The overall framerates are better in DX12, but the CPU clockspeed is not being maintained for some weird reason, the temps are not throttling and theres no power limit issues(tested via intelburn//realbench/prime), it easily holds 4.2ghz during stress & in DX11 so the problem is with DX12 only.

This weird DX12 behaviour would also explain why the game runs much better with windows power options set to high performance(force max clockspeed). But that's just a bandaid fix rather than a real one unless you want your CPU running full bore @ desktop without changing power settings all the time.

I took a direct video of the difference when enabling high performance here: https://youtu.be/tKrdKfdLhQ0

Doesnt happen in other DX12 games and appears to be isolated to Tomb Raiders DX12 API, so the problem would likely carry over to other OS, so set your CPU frequency to max using whatever means possible.

In regards to black skin,, screen space reflections would be one of the most likely culprits. I had a shadow clipping issue with an early release of SotTR that was caused by Screen Space Contact Shadows on High. medium fixed it, but the issue has since been patched. You can see it at the start of the in-game benchmark here: https://youtu.be/9OKVPIOxtMY

kakra commented 5 years ago

In Linux, you could probably use Feral's GameMode daemon to work around this, and set the CPU to performance governor.

pdaniell-nv commented 5 years ago

I'm curious if anyone who has seen the black flashing skin issue has tried with a DXVK with https://github.com/doitsujin/dxvk/commit/6dd82dfe0317387458c6788dcf51a717422fdb48 and seen whether it resolves that issue.

kakra commented 5 years ago

@pdaniell-nv No, it doesn't resolve that here (nvidia). I think the black patches should be reflection from wet skin. Comparing graphics in Youtube "Let's Play" videos with my setup leads me to think that the skin isn't rendered correctly in many scenes: DXVK introduces color banding on Lara's skin, and it looks dull instead of "sweaty" or "wet" (not sure how to describe it). But this may well be a result of lower graphics settings.

I'm currently using the latest master build here compiled as winelib.

NextGenRyo commented 5 years ago

I don't know about all that but I'm playing with ultra settings, but to not have flashing black skin I must turn off Motion Blur Screen Space Reflections and Ambient Occlusion Not sure about that last one to be honest. Also to keep the FPS above 100 and to not notice any lag in heavy populated areas I set the CPU to Performance Governor The game runs great. On my second run through now :)

kakra commented 5 years ago

@mixalis1987 I'm using motion blur because I like that effect very much - it looks more natural and makes a better immersion during fast camera movements, so I never played without it. I tried with and without SSR but it didn't remove the black patches. I also really don't like turning off AO because everything looks too flat without it. But AFAIR I've ran the benchmarks without AO and the black patches were still there. This leaves us with motion blur but I don't see how that could create such an effect. Maybe it's a specific combination of those settings (and others, too, since you use ultra quality).

NextGenRyo commented 5 years ago

@kakra Hmm indeed turning on AO and setting it to HBAO+ removes the black skin however the other one BTAO will bring the black skin. Motion Blur and SSR will bring the black skin.

kakra commented 5 years ago

@mixalis1987 I tried HBAO+ and it didn't help here... There's some effect on Lara's skin that's causing it. It can also be seen with some NPCs but only during a few cutscenes.

NextGenRyo commented 5 years ago

@kakra I've been playing for over an hour with HBAO+ on and it looks fine with NPC's. Motion Blur and SSR still off though.

ncoder-1 commented 5 years ago

Now works for me with:

linux 4.20.1 (archlinux) nvidia 415.25-6 Proton 3.16-6 Beta

screenshot from 2019-01-13 14-11-38

Frame rates hover around 80 fps, never below 60 on a GTX 1080. No black artifacts.

shandstp commented 5 years ago

It looks like my system is very similar to elimpnick's,

linux 4.20.1 (archlinux) nvidia 415.25 (does the "-6" mean he has a more recent driver than me?) proton 3.16-6 Beta nvidia gtx 1080

but even after I tried matching the graphics settings shown in elimpnick's comment, I still get the black artifacts that so many people have been talking about. Strangely, it only seems to affect Laura and Jonah's skin while all other characters seem to be unaffected. It also seems to get worse when they are closer to the screen, so it may be that it affects other NPCs but haven't got close enough to notice. Besides the artifacts and the "No Display Adapter" warning mentioned by NeptNutz, the game seems to run fine for me.

kakra commented 5 years ago

nvidia 415.25 (does the "-6" mean he has a more recent driver than me?)

That part of the version number is not nvidia but arch specific. It's a subversion/revision, instance/build, or "generation" number - not really interesting for the driver itself. It's only some arch-internal versioning scheme.

shandstp commented 5 years ago

@kakra Thank you for the clarification. In that case, I'm at a loss as to why elimpnick is able to get rid of the artifacts and I'm not. I'd like to do something help resolve this but I'm pretty new to both linux and programming, so I'm not sure where to start.

kakra commented 5 years ago

@shandstp I'm also seeing the artifacts no matter which settings I chose. Almost all NPCs will show these artifacts in cut scene close-ups, it's not only Lara and Jonah. It may be a driver/hardware combo thing. I'm running on a GTX 1050 Ti 4GB, FHD resolution.

topolittle commented 5 years ago

The artifacts are still there with the same settings as elimpnick. I am running kernel 4.19.14-300, nvidia drivers 425.27 and proton 3.16-6 beta. I have a GTX 1080 too by my framerates are between 50 and 80, with the governor set to performance.

NextGenRyo commented 5 years ago

yea black artifacts still there, using wine 4.0-rc5 and nvidia 415.25 GTX 1080ti framereates around 80ish max settings.

topolittle commented 5 years ago

I updated the game via steam, video drivers to 418.30 and the kernel to 4.20.6-200 and the black artifacts are gone. Same game settings.

NextGenRyo commented 5 years ago

@topolittle Thanks! Good to know. Once those drivers are out of beta I'll be updating :)

kakra commented 5 years ago

@topolittle I can confirm that the black artifacts are gone. I wonder if this also fixes the black pixel bleeding happening sometimes when TAA is turned on.

ncoder-1 commented 5 years ago

No longer working for me. This is on Linux 5.0.5-arch1-1-ARCH, nvidia 418.56-3 and both proton 3.16.8 and 4.2-1. Basically, the initial splash screen loads as a black screen, then the game exits.

If I add the following launch option: PROTON_USE_WINED3D=1 %command%, I can get into the game, but it is unplayable (graphic errors and very low FPS). According to a user report here: https://www.protondb.com/app/750920, it seems it may be caused by a recent raytracing update in the game.