Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tomb Raider: Underworld (8140) #3616

Open
shoober420 opened this issue Mar 8, 2020 · 7 comments
Open

Tomb Raider: Underworld (8140) #3616

shoober420 opened this issue Mar 8, 2020 · 7 comments
Labels
DXVK/D3D9 🐸 Regression from enabling DXVK/D3D9 by default Game compatibility - Unofficial Games not expected to work without issues

Comments

@shoober420
Copy link

shoober420 commented Mar 8, 2020

Compatibility Report

System Information

VULKAN WITH VSYNC DISABLED LOG:
steam-8140.log

Symptoms

Game stutters and freezes for as long as a couple seconds sometimes. Loading screen dropped down to 1FPS and took forever to load the game.

@kisak-valve
Copy link
Member

Hello @shoober420, does running the game with PROTON_USE_WINED3D=1 have an effect?

@iWeaker
Copy link

iWeaker commented Mar 8, 2020

@shoober420 The game has problems in Windows, especially with Nvidia graphics, the solution is to activate VSYNC so that it works correctly.

@shoober420
Copy link
Author

shoober420 commented Mar 8, 2020

@kisak-valve
Using "PROTON_USE_WINED3D=1" fixed the stuttering dramatically, and made it playable.

D3D WITH VSYNC DISBALED LOG:
steam-8140D3DNOVS.log

@iWeaker4you
Enabling VSync, along with using WineD3D, made the game run perfect. Enabling VSync completely eliminated any stutters and freezes.

D3D WITH VSYNC ENABLED LOG:
steam-8140D3DVS.log

Using DXVK with VSync enabled was still producing stutters and freezing. DXVK behaved the same, whether VSync was enabled or disabled.

VULKAN WITH VSYNC ENABLED:
steam-8140.log

@kisak-valve kisak-valve added the DXVK/D3D9 🐸 Regression from enabling DXVK/D3D9 by default label Mar 8, 2020
@kisak-valve
Copy link
Member

Tomb Raider: Underworld (8140)

Issue transferred from #4640.
@hotwinter posted on 2021-02-20T10:16:37:

Compatibility Report

  • Name of the game with compatibility issues: Tomb Raider: Underworld
  • Steam AppID of the game: 8140

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

The game does not launch, lots of repeated c0000005 exception thrown, log is too large, thus compressed

steam-8140.zip

@acdcfanbill
Copy link

acdcfanbill commented Mar 8, 2021

Compatibility Report

  • Name of the game with compatibility issues: Tomb Raider: Underworld
  • Steam AppID of the game: 8140

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.

launch log file

steam-8140.log.gz

Symptoms

Game fails to launch. There is no window that pops up or anything, just silently fails to start after several seconds. I tried various version of proton to run it and I've added PROTON_USE_WINED3D=1 to my launch options. I suspect it may be hardware (or drivers for this particular hardware) related as my hardware has failed to launch the game on every Ubuntu release since 19.10 up to my current install of the 21.04 beta. There has been no hardware changes, but several software updates including various kernels and mesa builds in each major Ubuntu version.

Reproduction

  1. set Launch Options and Proton version if desired
  2. click Play button
  3. steam shows game as running for a few seconds then it shows it as not running

@acdcfanbill
Copy link

I was thinking about this issue and decided to test something as the previous person with an issue also had a 3950x processor but an NVIDIA GPU. It might have to do with the number of CPUs the game sees/launches on? I've just adjusted my launch options to this PROTON_USE_WINED3D=1 taskset -c 0-3 %command% and now the game starts and runs very smoothly. The game must not handle 16 cores/32 threads very well because I can adjust the taskset command from -c 0-1 all the way up to 0-30 and it works, but if i pass it all 32 threads with -c 0-31 it fails to start the game again.

@hotwinter
Copy link

I was thinking about this issue and decided to test something as the previous person with an issue also had a 3950x processor but an NVIDIA GPU. It might have to do with the number of CPUs the game sees/launches on? I've just adjusted my launch options to this PROTON_USE_WINED3D=1 taskset -c 0-3 %command% and now the game starts and runs very smoothly. The game must not handle 16 cores/32 threads very well because I can adjust the taskset command from -c 0-1 all the way up to 0-30 and it works, but if i pass it all 32 threads with -c 0-31 it fails to start the game again.

That's interesting... Yes, I can confirm that this is actually the behavior, in fact after knowing about this, I searched and found another post with similar problem in the steam discussion of the game https://steamcommunity.com/app/8140/discussions/0/2791621786941084149/, so indeed this doesn't look like a problem of proton

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DXVK/D3D9 🐸 Regression from enabling DXVK/D3D9 by default Game compatibility - Unofficial Games not expected to work without issues
Projects
None yet
Development

No branches or pull requests

5 participants