protonscr

RenegadeX: Complete game freeze

dxvkclosed d3d9
doitsujin/dxvk#5855 · opened 2026-08-23 by andrew-2e128 · updated 2026-08-25 · 10 comments · github
Aandrew-2e128 2026-08-23 github

Since dxvk 3.0 after playing the game for a while (10~60 minutes) the game freezes completely and I get the following error :

err:   Exception on CS thread!
err:   Failed to create sampler object: VK_ERROR_OUT_OF_DEVICE_MEMORY

tested with and without Mangohud (no difference), the application is 64bit, but I think it's memory (and vram) usage is capped

Software information

RenegadeX (d3d9)

System information

  • OS: Arch Linux kernel 7.1.x
  • Window manager: Niri (wayland)
  • GPU: RTX 3060 Ti
  • Driver: Nvidia 610.43.03 to 610.57.04
  • Wine version: tested with wine (arch package) 11.13 to 11.16
  • DXVK version: 3.0 to 3.0.2 (and sometimes tested with random development builds)

Apitrace file(s)

  • NONE

Log files

game_info.log

KK0bin maintainer 2026-08-23 github

Apitrace file(s)
NONE

Please add that.

Oops, missed the 60 minute part. Sorry, my bad.

Ddoitsujin maintainer 2026-08-23 github

Well in fairness it's probably not viable to run apitrace for 60 minutes.

Anyway, maybe try this branch, wouldn't be the first time that all the bullshit surrounding DLSS support is causing problems; it's literally the only reason we even call vkCreateSampler at all.

Aandrew-2e128 2026-08-24 github

using this build https://github.com/doitsujin/dxvk/actions/runs/32673399895
issue seems to be resolved, 2 instances running for well more than an hour, I will stress test it later today

Aandrew-2e128 2026-08-24 github

after stress testing with one more game (dx8) and a few hours of gameplay, everything seems good with this

Ddoitsujin maintainer 2026-08-24 github

Well that's annoying, not sure what we can do short of providing a user option to turn those extensions off at the cost of not having DLSS etc in some of the more modern games. We can't auto-detect any of this and I don't have the slightest idea why creating legacy samplers would be causing issues in the first place.

Edit: well actually I supposed we could also simply ignore the error on the descriptor heap path, but it might very well error out eslewhere instead. Root cause isn't really debuggable here.

Ddoitsujin maintainer 2026-08-25 github

Please test with #5860.

This will ignore errors (which should be fine since there's no DLSS here anyway). If that still doesn't work, DXVK_CONFIG="dxvk.enableNvCudaInterop=False" can be set to explicitly disable the extensions.

Aandrew-2e128 2026-08-25 github

an observation; the issue does not happen with 3.0.2 on d3d10/11 game (tested with Endzone);
maybe just exclude d3d9?

note testing takes quite a lot of time, so results can take time

Ddoitsujin maintainer 2026-08-25 github

No real point in doing anything by default if we don't fully understand why it happens. And we have absolutely no evidence whatsoever that would suggest this is a common issue in D3D9 games (not that there are that many 64-bit D3D9 games to begin with).

If anything, the known issues with the NVX extensions all affect a small set of more or less random games. The difference is that they usually result in failed device creation which we already handle, rather than runtime errors.

Aandrew-2e128 2026-08-25 github

PR #5860 seems to be working fine,

Tested with this build https://github.com/doitsujin/dxvk/actions/runs/32834576063 seems to be working fine; After long test (2h+) I got the following 2 lines in terminal in the middle of the game logs, did not notice anything game wise.

warn:  Failed to create legacy sampler object: VK_ERROR_OUT_OF_DEVICE_MEMORY
warn:  Failed to create legacy sampler object: VK_ERROR_OUT_OF_DEVICE_MEMORY
Ddoitsujin maintainer 2026-08-25 github

Cool, so that's working as intended.