Large RenderThread cost when using r.ShaderCompiler.JobCacheDDC

In the editor when running with ODSC our shader maps will never be complete.
This causes us to continually evaluate uniform expressions every frame for every material.
This results in a large RT cost. The culprit code is the following:

FMaterialRenderProxy::EvaluateUniformExpressions:

`OutUniformExpressionCache.bUpToDate = Context.Material.IsRenderingThreadShaderMapComplete();`

Is it safe to just assuming the cache is up to date? and as long as we re-cache everytime we get a new shader map things should always be up to date.

[Link Removed]

1. Change shaders
2. Launch PIE
3. Look at Unreal Insights captures
4. See large cost in FMaterialRenderProxy::EvaluateUniformExpressions

[UE-23848] Bug Status

i have this problem UE4CC-Windows-58DC12AF4B97F057BD108FBFF569B2E9_0000

I am not able to find world outliner how to enable it?

Bonjour j'ai un petit problème c'est que je ne vois plus l'onglet "scability" pour changer les graphismes de uefn et j'ai pas trouvé l'option pour le faire revenir ?

Delay nodes occasionally don't fire the "Completed" output in a nativized build

How to achieve HLSL Multiple Render Target in Material blueprints?

How can i modify the param name in EQS node

Error UE5 5.0.3

Undefined sysmbol: typeinfo for AActor when cross-compile linux dedicated server on windows

When I open UE4 4.24.3 it appears that. Does anyone know how to solve?