This is kind of expected on low-end hardware such as this. DXVK does need more VRAM than Windows, and Windows has much more sophisticated memory management.
For Frostpunk you'll probably need 8GB at least, since the game fills up that much memory for no good reason. That's not a bug in DXVK, it does that on Windows, too.
By the way, you could try latest dxvk-git, which uses the VK_EXT_memory_priority extension if available, and allows VRAM overallocation.
The extension isn't going to work on wine for now, but the overallocation behaviour may fix things for you.
The game runs great on decent hardware. I'm with GTX 1080 and the game runs with ~230 FPS.
I tried to test it with latest dxvk-git (0.96-41-gbe22756). When freshly started the performance was even worse (3fps) but after ~30 min leaving the game paused and doing things (open menu, close menu, zoom in, zoom out, look around) I get very weird behaviour.
There seem to be different "performance states".
Some are:
It seems to switch between such states (there are more, they may never be the same) semi-randomly, 2-3fps only happening in the first 10 min, capped 60fps happening very seldom.
This is "kind of" reproducible (the switching seems random, but always happens) and does not happen with 0.96.
If you want me to i can make screenshots showing that behaviour.
I would be very interested in an explanation.
@QuImUfu Disable Ambient occlusion, depth of field, global illumination. Those are hogs.
@ryanmusante all this is happening with minimal settings. These things are all of.
@QuImUfu Export running output to a logfile and see what the levels of usages are and the highs/lows.
I would be very interested in an explanation.
No idea, but performance can be rather random under memory pressure with the new overallocation behaviour.
Anyway, DXVK would probably have to dynamically page textures in and out of video memory to make this game sort of work on your card, which unfortunately is extremely hard and would require not only a complete rewrite of the memory manager, but also major changes to other parts of the code. It may not be impossible, but I can't promise that this will ever happen.
I was wondering.. would AMDVulkanMemoryAllocator help improving the situation?
Not really, no. While the AMD allocator supports defragmentation, the one thing that makes this so hard to implement is that all resources that get moved have to be recreated and copied at the right time.
Nothing extracted yet.
Frostpunk runs with 8fps on a RX460 2GB (unlocked to 1024 cores) with DXVK.
On windows it runs with 60 fps. (edit because i forgot to turn down the settings)
Is such a big performance hit expected?
The DXVK hud displays the game using 6GB of RAM. Could that be the reason for the low performance? Does DXVK use more video RAM vs. Windows drivers?
Software information
Frostpunk 1.3.2.42665.45362 minimal settings
System information