The distance field scene is shared between scene renders in a given frame. However, LOD requests are not tracked over the entire frame, but per scene render (e.g. camera or scene capture). Thus, if a scene render requests LOD0 for the distance field of an object and a second scene render requests LOD1, it will cause flickering in the distance field shadow tracing. This happens, since requests are enqueued as async readbacks, and thus in the next frame, the first render can end up using the distance field scene representation of the second render and vice versa. (see attached gif, note this is captured without temporal AA.)
1. Create empty scene.
2. Add a local light and enable distance field shadows.
3. Add a shadow caster object, and a receiving shadow object.
4. Add an actor with a SceneCaptureComponent, make sure it renders the shadow casting object and place it at a location larger than set by the GLumenSceneGlobalDFClipmapExtent.
5. There should now be flickering between LODs in the distance field shadows.
i have this problem UE4CC-Windows-58DC12AF4B97F057BD108FBFF569B2E9_0000
I am not able to find world outliner how to enable it?
How to achieve HLSL Multiple Render Target in Material blueprints?
Undefined sysmbol: typeinfo for AActor when cross-compile linux dedicated server on windows
How can i modify the param name in EQS node
Delay nodes occasionally don't fire the "Completed" output in a nativized build
How does TextureRenderTarget2D get TArray<uint8> type data?
Why does the REMOVE method of map container remove elements have memory leaks?
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-176870 in the post.
| 1 |
| Component | UE - Graphics Features |
|---|---|
| Affects Versions | 5.3 |
| Target Fix | 5.6 |
| Created | Feb 12, 2023 |
|---|---|
| Updated | Oct 18, 2024 |