We do not guarantee backwards compatability for custom expressions using implementation-detail engine features.
The expected behavior occurs in 4.19; unexpected behavior occurs in 4.20 and 4.21. Marking this as a regression.
Per User:
Reading the LightAttenuationTexture in a material receives interference from other textures under forward rendering. When viewing the output of the material preview window unrelated textures (usually masks used in other materials) will appear on the preview mesh depending on where the camera is looking. In addition to this, the LAT output within the viewport appears to be affected by another texture, as though it is receiving the lighting data, but has also added the other texture on top of it.
Why does the REMOVE method of map container remove elements have memory leaks?
How does TextureRenderTarget2D get TArray<uint8> type data?
What is the cause of the packaging error falling back to 'GameUserSettings' in ue5?
How to delete some elements correctly when deleting an array loop?
How do I set a material as a post-processing material?
What is the difference between Camera and CineCamera?
How does TArray loop correctly remove elements in blueprints?
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-61513 in the post.
18 |
Component | UE - Graphics Features |
---|---|
Affects Versions | 4.20, 4.21 |
Created | Jul 5, 2018 |
---|---|
Resolved | Jul 6, 2018 |
Updated | Mar 10, 2020 |