Hey everyone.
For some reason i got a blue screen when i opened up GZDoom once, and now i just can't open the game anymore with the vulkan renderer. Open GL works just fine though.
I tried different games with Vulkan and they seem to work just fine.
OS: Windows 10 (NT 10.0) Build 19045
GZDoom version g4.13.0
W_Init: Init WADfiles.
adding D:/Games/Doom/Sourceports/GZDOOM/gzdoom.pk3, 679 lumps
adding D:/Games/Doom/Sourceports/GZDOOM/game_support.pk3, 3308 lumps
adding E:/SteamLibrary/steamapps/common/ultimate doom/base/DOOM.WAD, 2306 lumps
adding E:/SteamLibrary/steamapps/common/Ultimate Doom/rerelease/id24res.wad, 530 lumps
adding D:/Games/Doom/Sourceports/GZDOOM/game_widescreen_gfx.pk3, 214 lumps
adding D:/Games/Doom/Sourceports/GZDOOM/gzdoom.exe, 1 lumps
S_Init: Setting up sound.
I_InitSound: Initializing OpenAL
Opened device IOpenAL Soft on Speakers (PRO X 2 LIGHTSPEED)
EFX enabled
I_InitInput
I_StartupMouse
I_StartupKeyboard
I_StartupXInput
I_StartupRawPS2
I_StartupDirectInputJoystick
Vulkan device: INVIDIA GeForce RTX 3080
Vulkan device type: discrete gpu
Vulkan version: 1.3.289 (api) 565.360.0 (driver)
Max. texture size: 32768
Max. uniform buffer range: 65536
Min. uniform buffer offset alignment: 64
Execution could not continue.
Could not create pipeline cache: vkResult -13
vkresult -13
Moderator: GZDoom Developers
-
-
- Posts: 3145
- Joined: Sat May 28, 2016 1:01 pm
Re: vkresult -13
Try delete the zdpc files in %localappdata%\zdoom\cache
If that doesn't fix it, try reinstall your display driver.
If that doesn't fix it, try reinstall your display driver.
-
-
- Posts: 3145
- Joined: Sat May 28, 2016 1:01 pm
Re: vkresult -13
This is unfortunately the third time this fixed the issue. Either the compatibility check done by the backend is not correct according to the spec (I need to check this), or NVIDIA's driver sometimes build a broken pipeline cache and we need to put in some kind of fallback for this situation.
-
-
- Posts: 3145
- Joined: Sat May 28, 2016 1:01 pm
Re: vkresult -13
Looked into this a bit and the driver is responsible for validating its own cache data we saved for it according to the Vulkan 1.3 spec. So basically its the NVIDIA driver shitting itself, but since its been happening for a few people now it may still become our problem.