Depth reading features on devices without framebuffer fetch are relying on undefined behaviour.

For devices without framebuffer fetch we are relying on undefined behaviour for depth reading with decals, mod shadows and depth reading materials. (ES2 spec: 3.8.6 Texture Framebuffer Attachment).

for the most part we get the behaviour we want at a good performance. However, we are liable for any odd behaviour (such as seen in [Link Removed]).

We need to provide a proper, spec compliant, solution for depth reading.

A proper fix is to set GSupportsDepthFetchDuringDepthTest=false and draw depth to a float target and pass that as the aux depth texture (as happens when GSupportsDepthFetchDuringDepthTest == false). On devices that dont support float targets this could be rgb encoded. Additionally, we could consider an error in the gl rhi to detect this scenario.

run steps described in [Link Removed] and then set r.Mobile.ForceDepthResolve 0 and observe broken shadows.

[UE-23848] Bug Status

Fix UE-51650

i have this problem UE4CC-Windows-58DC12AF4B97F057BD108FBFF569B2E9_0000

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

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

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

How can i modify the param name in EQS node

How to achieve HLSL Multiple Render Target in Material blueprints?

How does UMG set overlapping layouts?

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 ?