You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
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.
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
Apitrace file(s)
ship_d3d9_trace.zip
Log files
The text was updated successfully, but these errors were encountered: