When adding a RuntimeVirtualTextureOutput node to a Virtual Texture domain material, the RVT Output node overwrites any data being sent to the normal material node's output, which interferes with the material's intended use. The RVT Output node should generate an error when it is placed in a Virtual Texture domain material indicating it is not compatible with that material domain. This doesn't seem like a desired workflow for the user to use and is likely to cause more confusion around the intended function of the RVT Output node.
Expected Result
The RuntimeVirtualTextureOutput node doesn't affect the material since nothing is being passed to it, or an error is generated indicating the node can't be used with Virtual Texture domain material types.
Actual Result
The RuntimeVirtualTextureOutput node overwrites the data being passed to the normal material output node causing the decals to appear as magenta squares and no error is generated in the Material Editor
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-76682 in the post.
0 |
Component | UE - Graphics Features |
---|---|
Affects Versions | 4.23 |
Target Fix | 4.24 |
Created | Jun 21, 2019 |
---|---|
Resolved | Jul 17, 2019 |
Updated | Sep 19, 2021 |