Context:
Someone had asked in Spectrum chat how to fix the Vulkan Crash Issue and OP responded by explaining how to clear shaders.
Silvan-CIG:
Sorry about that guys, it was me causing this. I will explain how as it was quite technical.
Clearing the shaders folder will not fix this issue. It is a corruption and doesn’t necessarily lead to a crash, just the CPU reading some random memory.
I am working on massively improving the “Optimizing Shaders” step at the moment in the tech preview stream. It will be much faster and reduces the memory usage by a huge amount. So as i was implementing this, i made a custom build with my change to send it to QA for testing.
To further understand this issue you need to know that all combinations of shaders are collected on a global server. So as our QA was testing the build he encountered a new shader which i’ve added and it was added to the shader list. The next live build picked up this shader which the code couldn’t deal with at the time resulting in this corruption. The issue already has long been fixed but since the live code uses very outdated code this was happening.
Anyway, it is fixed already and hotfix should be coming in soon!
Cheers
Silvan-CIGEdit: OP was right that it fixed the issue since clearing the shaders folder reverts back to DX11 and this is a Vulkan only issue!
Edit: fixed title typo
You must log in or # to comment.
Oh that’s a classic blunder :D
