Hey there @jawoods141! Welcome back to the community! There have been some reports of Vulkan having issues primarily for Linux users on 5.1. I’m thinking it is caused by using SM6 (Shader model 6) and Vulkan, however Linux users are such a small sample size I can’t get a good amount of data.
Could you try backing up your project, and trying setting it to SM5 in the project settings as a test?
Well that is exactly it, there is no project at all. I simply can not launch 5.1 at all to create a project. Is there a way for me to set it to SM5 in the engine settings itself? I will google that now. And thank you!
This is a bit of a tough one, I know we can change the RHI externally (DX11, DX12, or Vulkan) in the DefaultEngine.ini in the project’s config folder but I’ve never had to change the shader model outside of a project. I thought that the engine wouldn’t default you to SM6, as when I installed 5.1 it gave me a warning I’d need to change the project to SM6 to utilize nanite and lumen. In your case you hadn’t even gotten to that point. I’ll have to dig a bit deeper in this case.
If I discover anything helpful, I will post it here. In the mean time I am continuing my work on 5.0.3. Might just be a bug that we have to sit tight on for a bit
Okay, I am throwing in the towel on this issue. I have tried a lot with no success. In a month I will try compiling the latest version from github but until then I am staying on 5.0.3. If there is any additional information I can provide you guys about this issue let me know and I will get it for you, I am sure that a lot of others are also dealing with this issue.
Understandable! I’ll keep my ear to the ground on this specific issue. Your specs and the fact it’s failing on Arch is most of the information I needed off the bat. The Vulkan issues especially on Linux are hard to get good data on. If you learn anything let me know!
Quick question, is there a list of specific dependencies and version requirements for this that might be needed? I could not find anything on this. For example, glibc is a requirement and it requires version 2.17 or better. But there are other requirements for Linux but no documentation on that just a lot of old fashioned google searching based on compile errors when you first compile the engine. Any chance you might have a more complete list of requirements?
I don’t believe there is updated official documentation on the Linux side but on the requirements page it does have a bit of information about requiring specific Vulkan shader atomics set for SM6.
However I for anyone reading this thread that can get a project built but running but crashes on SM6, here’s how to disable it on the project side.
In your Project folder, DefaultEngine.ini you may be able to remove the check here for SM6 and see if it successfully opens.
Having this same problem using Windows 10. I changed RHI in the project settings to Vulkan and it crashed the editor, then I couldn’t open the project at all without getting “Fatal Error”. Had to open DefaultEngine.ini and remove everything after “DefaultGraphicsRHI=”, now my shaders are compiling from scratch again but at least the project opens.
Yes it seems that Vulkan has been having more issues, it’s becoming a community recommendation for anyone that doesn’t require Vulkan in this release of 5.1 to swap over to DX12/11 while many of the issues are sorted. However, some of the issues do have workarounds, like with issues that involve the rendering drivers. This specific issue is rough, as even without hardware or software raytracing this is sometimes failing.
This does actually take some relief off of my shoulders as for a little while I thought I had a hardware issue. Good to know that I am not alone. I am just staying on 5.0.3 while things get sorted or until a working work around is discovered. And of course I will still report anything I find.
OK well, got the git thing figured out. I do have another post coming but I need time to sort out what I have as it is complicated but it may help with this issue along with others related to VulkanRHI on linux.
Well, still no luck with this. I saw lots and lots of people having a very similar issue with steam games so I messed around a lot with steam client dependencies with no luck. I am of the opinion that this is likely a driver issue. There is also a chance that it is a hardware issue but that is very unlikely as literally everything else works fine and this laptop has passed the hardware tests I ran on it with no issues. I am trhowing in the towel and just waiting for updates and using 5.0.3 until then. If anyone does come across anything useful, lease post it and thank you all for trying to help still.
