Have you tried increasing GTT size to something like 3/4 of your available RAM? This engine is known to "emulate" D3D9-style resource uploads, which means that every single buffer/texture is backed by an additional STAGING resource, and those do go into GTT.
The trace somehow just crashes apitrace on my end even when just trying to open it in the UI, so unfortunately that doesn't seem to work.
Greetings, @someApprentice
In order to workaround your issue try the following:
-no_staging launch argument to your AnomalyDX11.exe executable file.As a result, game should use VRAM instead of RAM for graphics resources.
Additional Info: https://old.reddit.com/r/stalker/comments/hkli3g/bugfix_out_of_memory_how_to_win_out_of_memory_bug/
Have you tried increasing GTT size to something like 3/4 of your available RAM? This engine is known to "emulate" D3D9-style resource uploads, which means that every single buffer/texture is backed by an additional
STAGINGresource, and those do go into GTT.
Yes, increasing GTT size resolves the issue.
Apparently, it is an engine issue and nothing can be done at the DXVK layer.
Thank you for your response.
Add the
-no_staginglaunch argument to yourAnomalyDX11.exeexecutable file.
Launching Anomaly with the -no_staging argument doesn't seem to affect anything.
It's could be because the Anomaly uses its own engine X-Ray Monolith, which is based on X-Ray rather than X-Ray itself.
But thank you for response, @Digger1955.
Nothing extracted yet.
The game crashes after overloading GTT without using VRAM at all. Simple is that. I don't even know what else I could add to the description. All other resources like CPU, RAM, or swap are also not overloaded.
The Wine log and apitrace are attached in the respective sections.
Software information
STALKER Gamma
System information
Apitrace file(s)
apitrace.tar.gz
Log files
wine.log