Hi, I have been having this error. This occurs when i try to package my project to linux and with source build.
I could build with empty project and engine 4.20
I used to have this error on an old project and another version. Try to look for assets in your game using this default material which is Editor only. Try also to exclude every folder which is not supposed to be packaged from packaging in your Packaging settings.
A good way to see if one of your assets you are packaging is referencing this Material, is to right-click on this WorldGridMaterial in the content browser and “Find References”. It should show you every asset referencing this WorldGridMaterial. Do not forget to enable “Show Engine content” and stuff like that in the content browser (can’t remember where this Material is).
Thank you for answering!
I copy-pasted my project to another location and cleared out content folder and then packaged. It gave same error, so it does not depend on what material I use in my project.
Also tried to make empty project and added a map, where is only one cube with WorldGridMaterial. This project was built with UE4.20 (Not source build) and build was successful.
There is some problem with my engine built from source.
Please go to your project properties, Platforms → Linux and disable GL3 there. For whatever reason there’s an issue compiling default material in your engine installation for GL3. This RHI has been long deprecated anyway, so by not supporting it you will only save yourself more trouble.
(The compilation of the default material shouldn’t fail nevertheless).
Thanks RCL! A quick question though: in 4.17 there is the same bug, even with just DX11 activated, do you know if there is a way to fix the problem in the 4.17 version?
[File:D:/Build/++UE4+Licensee/Sync/Engine/Source/Runtime/Engine/Private/ShaderCompiler/ShaderCompiler.cpp] [Line: 2397] Failed to compile default material /Engine/EngineMaterials/WorldGridMaterial.WorldGridMaterial!
, would just deleting gridmaterial fix it or …
Project wont’ start anymore and I’d really liked to get back in, sounds like an easy problem , just afraid to breaking something for good if I do the wrong thing…
Trouble also is , there is NO D:/build at all, whats up here ? ;00 Is this temporary and it deletes all after crash ?
And in case of this problem in Windows. How do I resolve this? I just had this problem and I can’t EVEN get into Unreal 4.27.2. How do I solve this problem? PLEASE HELP!!!
I have ran into similar situation today. Going to Epic Game Launcher and verifying UE installation and plugins solved the issue - I can load my project without issues.
UE 5.3.2
just got this a couple days ago as well tried all the solutions above to no avail. so if anyone else has this issue the solution that worked for me was to disable SM5 for the targeted vulkan RHI in project settings. must be a bug in the graphics drivers. not sure who this needs to get to for fixing, but hope this helps someone.
Edit: it appears that you just cant have both enabled at the same time, use sm6 if you need the new features of ue5 like virtual shadow maps and such, sm5 if you dont need any of the new stuff
OMG, you’re my savior!!
I need to disable 1 of SM5 and SM6 for Vulkan RHI. My pacakged project will work normally.
I cannot express how appreciative I am. I’m curious how do you learn that anyway?
after trying all the above solutions and nothing working, even re-downloading and building ue5.5.2 from source. i realized it definitely was the project and more specifically the packaged project. so i just decided to read the logs more carefully and saw a lot lines about the vulkan shaders not supporting things before the worldgrid material error occurs. so figured maybe theres a conflict going on. so i unchecked one to test and behold it was able to open the packaged game. then i switched and it still worked, but having them both enabled broke it again. so i just left sm6 enabled cause i use the new features. only thing that changed for me was upgrading to new unreal and i think i got some gpu driver updates. so i assume something went wrong with amd drivers and ue5.