Could you post a cfg file thats present when the issue occurs?

Could you post a cfg file thats present when the issue occurs?

All settings are default. I've tried to change, even deleting some of them and still nothing. Only complete deletion is working.

-- [Game-Configuration]
-- Attention: This file is re-generated by the system! Editing is not recommended! 

i_useSteamController = 1
sys_spec = 3
r_VSync = 1
r_Fullscreen = 1
r_Width = 1920
r_Height = 1080
r_overrideDXGIOutput = 0
sys_MaxFPS = 144
sys_spec_water = 3
sys_spec_volumetriceffects = 3
sys_spec_sound = 3
sys_spec_postprocessing = 3
sys_spec_physics = 3
sys_spec_light = 3
sys_spec_gameeffects = 3
sys_spec_particles = 3
sys_spec_shading = 3
osm_targetFPS = 30.000000
osm_enabled = 0
cl_hfov = 85.000000
r_arkssr = 1
r_arkssdo = 1
r_AntialiasingMode = 3
r_TexMaxAnisotropy = 8
sys_spec_texture = 3
sys_spec_shadows = 3
sys_spec_objectdetail = 3

Well, I can just leave empty cfg with write protection enabled. But In that case I have to change settings manually every start.

I am not reproducing on Windows with my R9 380. Maybe some bad hidden character gets sneaked into the cfg? unsure since it also works for me if i copy your cfg above into mine.

Could you try making a file called dxvk.conf (conf is the extension so make sure it isn't a text file like dxvk.conf.txt) in the games root folder (so not next to the exe) and insert dxgi.nvapiHack = False and see if it changes anything?

Could you try making a file called dxvk.conf (conf is the extension so make sure it isn't a text file like dxvk.conf.txt) in the games root folder (so not next to the exe) and insert dxgi.nvapiHack = False and see if it changes anything?

Nah, nothing.

I've found a solution: just put all options you need in shortcut or bat file. For me it was something like:

Prey.exe +sys_spec 4 +sys_spec_water 4 +sys_spec_volumetriceffects 4 +sys_spec_sound 4 +sys_spec_postprocessing 4 +sys_spec_physics 4 +sys_spec_light 4 +sys_spec_gameeffects 4 +sys_spec_particles 4 +sys_spec_shading 4 +sys_spec_texture 4 +sys_spec_shadows 4 +sys_spec_objectdetail 4 +r_TexMaxAnisotropy 16 +r_VSync 0

Exactly like this, in one line. But some options, like "r_arkssdo", "r_arkssr" and "r_AntialiasingMode" refuse to work through shortcut options nor config files (both, system.cfg and game.cfg).
All in all it seems like "sys_spec" is the option that cause crashes. Without dxvk everything's fine though.

@CortexReaver do you still experience this issue with newest DXVK and drivers?

@CortexReaver do you still experience this issue with newest DXVK and drivers?

I will test when I have some time, but I am playing with the default DirectX libraries right now (well, played like a couple of month ago) because it was slightly faster and I got less screen tearing that way.
But instead I've tested newer versions of DXVK recently on another CryEngine game: Homefront Revolution, and it still gives you less FPS then vanilla libraries in some places (especially burning barrels, casting shadows from high detailed human models). It's still "janky" on DirectX anyway, and I don't think it will become any faster with a wrapper. But as far as it goes - no visual artifacts and no crashes as well in both of these games, not to mention CryEngine is very picky in general.

Tested with one of the latest DXVK nightly build (this one: https://github.com/doitsujin/dxvk/actions/runs/4806741291) and latest nVidia drivers (531.79) - still got this error. But it slowly getting on the level of original DX libraries performance-wise, that's for sure :)

I can confirm the issue is still present both in the GOG and Steam versions.

@CortexReaver @Filoppi Can you give this another go with 2.5.3?

@Blisto91 I have since made my own full Prey mod: https://github.com/Filoppi/Prey-Luma/
that should also be compatible with DXVK as long as ReShade is run in DX11 mode. People have been using it on Proton.
I also had issues with crashes on boot when the game was set to High settings, it somewhat fixes itself if it's set to Medium or Very High. It seems like the DirectX device is re-created 2 or 3 times on boot when settings are set to High for some reason, maybe that's what DXVK isn't handling right.

@CortexReaver @Filoppi Can you give this another go with 2.5.3?

Can't replicate this on Windows 11 24H2 with the latest AMD driver and DXVK 2.6.1