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

[d3d9] The Ship(2400) uses up all virtual memory and GPU memory and then crash #2893

Closed
zzhiyi opened this issue Sep 7, 2022 · 3 comments · Fixed by #2896
Closed

[d3d9] The Ship(2400) uses up all virtual memory and GPU memory and then crash #2893

zzhiyi opened this issue Sep 7, 2022 · 3 comments · Fixed by #2896

Comments

@zzhiyi
Copy link
Contributor

zzhiyi commented Sep 7, 2022

After launch, the game gradually uses up virtual memory and GPU memory and then crashes, both on Proton 7.0 and on Windows 11. Even though the game is 32bit, it manages to use up 8G dedicated GPU memory and 8G shared GPU memory. And finally, running out of GPU memory, the game crashes. On Wine, the virtual memory limit is hit first and crashes. With native d3d9 on Windows or wined3d on Proton 7.0-4, the game runs normally. On Proton, you need to turn off the fullscreen hack first to get around its bugs.

Software information

The Ship (SteamID: 2400)

System information

  • GPU: AMD RX5500 8G
  • Driver: 30.0.15021.11005(AMD driver on Windows)
  • Wine version: Wine 7.0
  • DXVK version: 1.10.3

Apitrace file(s)

ship_d3d9_trace.zip

Log files

@K0bin
Copy link
Collaborator

K0bin commented Sep 7, 2022

Please try it with a DXVK config file like this:

d3d9.memoryTrackTest = True

Also, I just noticed you're using 1.10.x, please retry it with the latest master version of DXVK, as that contains a bunch of work to reduce virtual memory usage in D3D9 games.

@zzhiyi
Copy link
Contributor Author

zzhiyi commented Sep 7, 2022

After using "d3d9.memoryTrackTest = True" the game can run correctly. What's weird though, I can't reproduce this bug after even turning on this option once. Now with "d3d9.memoryTrackTest = False" or no dxvk.conf, the game doesn't crash any more. I have to delete the game directory and reinstall the game to reproduce it. With DXVK master, the bug still persists.

@K0bin
Copy link
Collaborator

K0bin commented Sep 7, 2022

Some games create D9D textures until that fails to determine the amount of available VRAM.

The game probably does this once and stores the result somewhere.

DXVK normally doesn't fail texture creation because that breaks texture mods for example. The option enables that. IIRC Microsoft has changed that behavior a couple of times and gotten a lot of backlash for breaking mods. I don't remember what they ended up with in the end.

Either way, we should enable the option for that game by default. I'll submit a PR to do that later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants