← Return to topic

Q30 Update Crash Fixes

lakimakiGoida · 10 Sep 2026 at 02:58 · permalink

At the moment, a number of people are having issues related to the graphics processing in regards to the new update. The exact cause isn't exactly known, but it looks like KEX began running on Vulkan as of the new update.

Besides verifying game integrity, uninstalling/reinstalling Quake and/or Steam, I've currently found some parameters to paste in Q1's launch properties that have helped people out:

1. +r\_rhirenderfamily "vulkan"

2. +r\_rhirenderfamily "d3d11"

3. +r\_rhirenderfamily "d3d11" +d3d11\_compileShaders 1

Another possible fix is going to users-->you-->saved games-->nightdive-->quake and deleting everything in there and having the game replace it, although this will nuke your save files and again, it might not work for you, so it's more of a last resort.

Yes, by some random fashion setting renderer to Vulkan OR Direct3D has fixed this for people. I'm no graphics card nerd, couldn't tell you how.

Hoping this helps anyone stuck; I'll update this with any more info I can find of assistance too.

Pixel · 10 Sep 2026 at 02:58 · permalink

Thanks mate, and all the luck to Drexler!

fructe · 10 Sep 2026 at 02:59 · permalink

Thank you so much, I was so excited to play and getting blocked really bummed me out! If you have integrated graphics like me the third option works!!

smailasltu · 10 Sep 2026 at 02:59 · permalink

thanks, you saved me, idk why they done with this update to make so much trouble, i wouklf prefer to play previous version of the game

Jok3rJB · 10 Sep 2026 at 02:59 · permalink

None of these fixes worked for me 😭

aspenscript · 10 Sep 2026 at 03:00 · permalink

None of these worked for me. When using "vulkan" nothing changes, the game launches in a minimized window with a black screen as before. When I used "d3d11" and the one after that, I got an error that says "kexRHIShaderManagerD3D11::CompileProgram: progs/compiled/hlsl/default_vs_5_0.bin not found"

hugomora · 10 Sep 2026 at 03:00 · permalink

+vk_compileShaders 1 fixed the issue for me with Vulkan.

lakimakiGoida · 10 Sep 2026 at 03:00 · permalink

Added, thanks

kliktari · 10 Sep 2026 at 03:01 · permalink

Yeah I get that error message with any of these launch parameters except the last one. The last one launches but has unacceptable flicker and visual artifacts.

marik163 · 10 Sep 2026 at 03:01 · permalink

so fucking shit. It's not launching for me either. I'll try these and see if they work. Keen as to play the new levels too

v_alpeev · 10 Sep 2026 at 03:02 · permalink

Yeah, I'm getting that error too. Hoping Nightdive can run a hotfix soon.

lakimakiGoida · 10 Sep 2026 at 03:02 · permalink

Edited the post, check at the bottom to see how to get this working on Ironwail.

lakimakiGoida · 10 Sep 2026 at 03:02 · permalink

I edited the post, Ironwail is able to run this now. Hopefully it'll help, please let me know if you run into a problem.

lakimakiGoida · 10 Sep 2026 at 03:03 · permalink

If you're still getting the error, Ironwail can work with mg3 now.

v_alpeev · 10 Sep 2026 at 03:03 · permalink

+r_rhirenderfamily "vulkan" actually boots up the game, but I get a new error. Error - ERROR_INVALID_SHADER_NV Line: 391 File: kexEngine\source\rhivulkan\rhiPipelineStateVK.cpp Line 391

+r_rhirenderfamily "d3d11" does nothing, same for +vk_compileShaders 1,

+r_rhirenderfamily "d3d11" +d3d11_compileShaders 1 is the winner. I don't see any weird bugs as of yet, but we shall see.