Failed to find shader type TOneColorVStruefalse in Platform PCD3D_SM5

Development Programming & Scripting Multiplayer & Networking
, , , , ,
1

Today I migrated my project to UE 4.16 (all sources compiled successfully), but when I tried to open *.uproject, I got this error:

Assertion failed: ShaderRef != NULL && *ShaderRef != nullptr [File:D:\Build\++UE4+Release-4.16+Compile\Sync\Engine\Source\Runtime\ShaderCore\Public\Shader.h] [Line: 1448] 
Failed to find shader type TOneColorVStruefalse in Platform PCD3D_SM5


UE4Editor_Core!FDebug::AssertFailed() [d:\build\++ue4+release-4.16+compile\sync\engine\source\runtime\core\private\misc\assertionmacros.cpp:349]
UE4Editor_UtilityShaders!TShaderMap<FGlobalShaderType>::GetShader<TOneColorVS<1,0> >() [d:\build\++ue4+release-4.16+compile\sync\engine\source\runtime\shadercore\public\shader.h:1448]
UE4Editor_UtilityShaders!ClearQuadSetup() [d:\build\++ue4+release-4.16+compile\sync\engine\source\runtime\utilityshaders\private\clearquad.cpp:50]
UE4Editor_UtilityShaders!DrawClearQuadMRT() [d:\build\++ue4+release-4.16+compile\sync\engine\source\runtime\utilityshaders\private\clearquad.cpp:234]
UE4Editor_Engine!<lambda_a0cd6242bc337ea48ad24b70d59678e7>::operator()() [d:\build\++ue4+release-4.16+compile\sync\engine\source\runtime\engine\private\userinterface\canvas.cpp:928]
UE4Editor_Engine!TGraphTask<TEnqueueUniqueRenderCommandType<`FCanvas::Clear'::`2'::ClearCommandName,<lambda_a0cd6242bc337ea48ad24b70d59678e7> > >::ExecuteTask() [d:\build\++ue4+release-4.16+compile\sync\engine\source\runtime\core\public\async\taskgraphinterfaces.h:883]
UE4Editor_Core!FNamedTaskThread::ProcessTasksNamedThread() [d:\build\++ue4+release-4.16+compile\sync\engine\source\runtime\core\private\async\taskgraph.cpp:954]
UE4Editor_Core!FNamedTaskThread::ProcessTasksUntilQuit() [d:\build\++ue4+release-4.16+compile\sync\engine\source\runtime\core\private\async\taskgraph.cpp:701]
UE4Editor_RenderCore!RenderingThreadMain() [d:\build\++ue4+release-4.16+compile\sync\engine\source\runtime\rendercore\private\renderingthread.cpp:327]
UE4Editor_RenderCore!FRenderingThread::Run() [d:\build\++ue4+release-4.16+compile\sync\engine\source\runtime\rendercore\private\renderingthread.cpp:461]
UE4Editor_Core!FRunnableThreadWin::Run() [d:\build\++ue4+release-4.16+compile\sync\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:76]

I’m using UE 4.16.1. I know there was a similar bug, which has been fixed (UE-44393 [CrashReport] Assertion due to failing to find shader type), so I wonder how to fix this one? For me, it’s critical, because I simply can’t run my project at all. I tried to clean Saved, Intermediate folders - it didn’t help.

2

I tried to play with configs and found that I can run the project only without this setting:

r.ClearCoatNormal=True

Looks like the error can be related to Clear Coat feature.

3

The problem appeared again after update to UE 4.16.2
Now I don’t know which render setting caused it and I can’t delete any other settings.
I also found the same problem, when I tried to open Multiplayer Shootout project from learn tab (Multiplayer Shootout | Unreal Engine Documentation).

4

I’m getting this to now, I’ve just replaced my motherboard and done a reinstall now I’m getting this, did you every find out why?

Seems a plugin was creating this issue for me on 4.16.2, once i deleted it… it started fine.

5

I updated to 4.17 and error disappeared.

6

Yeah 4.17 worked fine for me apart from other bugs im waiting to be fixed, i removed the FixItNote plugin and 4.16 is working again for me, something in this plugin it does not like.

7

Yes, you’re right. It’s all because of FixIt plugin. I’ve got the same error today on 4.17 when I turned on Forward Rendering (it was worked fine with deferred rendering in 4.17, however). Disabling plugin also didn’t help. Only removing it from Plugins folder.

8

Looks like FixIt plugin from Marketplace gives such error. The situation in 4.17 is better (deferred rendering is worked fine), but it also has some issues (forward rendering not working - same error with this plugin). Plugin removing currently fixing this problem. Maybe somebody will give an idea what’s wrong with it someday somehow…