Server fatal crashed: Vulkan: qvkQueueSubmit

[SiLenCe-WB]

Hi!

I've tried running quake3e-vulkan.x64.exe on 3 different systems with integrated GPUs (both Intel and AMD) and I always end up crashing with the following error:

----- Client Shutdown (Server fatal crashed: Vulkan: qvkQueueSubmit( vk.queue, 1, &submit_info, vk.cmd->rendering_finished_fence ) returned VK_ERROR_DEVICE_LOST) -----
RE_Shutdown( 3 )
----- Client Shutdown (recursive error after: Vulkan: qvkQueueSubmit( vk.queue, 1, &submit_info, vk.cmd->rendering_finished_fence ) returned VK_ERROR_DEVICE_LOST) -----
WARNING: Recursive CL_Shutdown()
recursive error after: Vulkan: qvkQueueSubmit( vk.queue, 1, &submit_info, vk.cmd->rendering_finished_fence ) returned VK_ERROR_DEVICE_LOST

The performance is flawless and substantially better than on quake3e.x64.exe (opengl) but the gl version never crashes. Am I doing something wrong or is this behaviour to be expected if I don't have a dedicated GPU?

BTW, I've been able to replicate this issue very fast by simply strafe jumping on the bottom part of Q3DM17, around the jumpers. I was using the default graphic settings to make sure it wasn't config related (I did a cvar_restart + vid_restart).

Thanks for the help!

[ec-]

Could you record demo and post it along with q3config.cfg?

[SiLenCe-WB]

I swear I've just posted a video and the q3config file. Let me try again:

• q3config: https://drive.google.com/file/d/1S3S0gc6-SIiNH4G72u6bhsm6tKp1iSTc/view?usp=sharing
• video: https://drive.google.com/file/d/1t1UjQhTZHWxyRSmmS0D1-idf-A5KhEnH/view?usp=sharing

[ensiform]

According to stack overflow at least one person had this happen when there were indices larger than the given vertex vector/array. Could be some out of bounds thing with the map that needs a guard

[SiLenCe-WB]

I have this issue in other maps too. I just realised that it was easy to replicate the issue in that specific area.

[SiLenCe-WB]

I've tested the same thing with an NVIDIA card (4070 Ti Super) and I had no issues whatsoever. So it seems to be a problem with integrated GPUs.

[ec-]

I can't reproduce it on various Intel iGPUs.
Also I see you have some modded textures (console, fonts, map etc.) - could you share your full setup somehow?

[SiLenCe-WB]

I can't reproduce it on various Intel iGPUs. Also I see you have some modded textures (console, fonts, map etc.) - could you share your full setup somehow?

Sure thing mate! Here it is: https://drive.google.com/file/d/1G1AhkNuXM_oFaaJwEVKHTcLXuvlwpaMo/view?usp=sharing

I removed the extra packages (which improve visuals) from that build but you can download them here: https://drive.google.com/drive/folders/1HheSapMEsrNVWuAKGKr1e0GmKu-7mGw4?usp=sharing

But bear in mind that I have the same issue without them, so those can't be causing the problem. Although I must say, I feel that with those packages added, the vulkan error pops up faster but it could have been just a coincidence.

[SiLenCe-WB]

I found that just by doing this, I can replicate the error very fast
https://streamable.com/a0y226

It usually drops the error in less than 30 seconds.