Every time I try to test the project in Standalone mode, the game will start loading thousands of shaders. This happens on packaged games too.
The editor itself works fine.
Hey there @Erapty1! So even launched games need to cache their shaders on first run, so if you have lots of shaders it will frequently do this. Since a new standalone window is effectively a new launch of it’s own (not really built) build, shaders will often have to be checked in. If you package the game and run that iteration, the shaders should cache the first run and if there’s no changes to the packaged game the loading of them should be fast the next time around. The reason the editor doesn’t do this is because the editor shader cache isn’t cleared unless you do it manually.
1 Like
The problem is that this happens every single time i try to launch the game, even a simple project like the templates. Even if i let it finish, next time I launch it I have to wait for that to finish again
Every time you launch projects where the shaders got cached, the shaders are recompiling? That’s interesting! What engine version and RHI are you using?
5.1.1 and DX11. Since 5.1.1 released, packaged games seem to run fine, but the issue persists in standalone testing, but it runs smoothly while shaders compile, unlike in 5.1. Since I packaged the game, the shaders it compiles also got reduced from ~5000 to ~3000.
Great info! So I’ve been tracking a similar issue that had cropped up on systems that worked fine with DX11/SM5 however DX12/SM6 would result in crashes or shader issues. This may not be related, but it does however sound like it could be. If possible could you submit a bug report?
1 Like
Did you end up solving this issue?