If we connect a virtual texture to the opacity mask output of a material the material will fail to compile. Currently this is expected because allowing it could cause problems such as:
If we connect only a regular texture we don't expect a problem.
However if the opacity mask uses a regular texture connected via MakeMaterialAttributes and BreakMaterialAttributes nodes and any virtual texture is connected to other properties in the MakeMaterialAttibutes then we still see a compile error.
It seems that the compilation validation logic is checking all texture samples connected to MakeMaterialAttributes instead of just the ones connected through the OpacityMask pin.
In a project where Virtual Textures are enabled, create a material like below.
[Link Removed]
Note that the texture connected to the BaseColor pin is a virtual texture, but the one connected to the OpacityMask pin is a regular texture.
Observe the material compilation error: "Sampling a virtual texture is currently not supported when connected to the Opacity Mask material attribute."
The expected behavior is for the material to compile.
i have this problem UE4CC-Windows-58DC12AF4B97F057BD108FBFF569B2E9_0000
I am not able to find world outliner how to enable it?
How can i modify the param name in EQS node
My UE5-0 Directional Light is too small and not real ,please tell me how to fix it thanks
Delay nodes occasionally don't fire the "Completed" output in a nativized build
How to achieve HLSL Multiple Render Target in Material blueprints?
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?
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-155682 in the post.
| 0 |
| Component | UE - Graphics Features |
|---|---|
| Affects Versions | 5.0 |
| Target Fix | 5.1 |
| Created | Jun 2, 2022 |
|---|---|
| Resolved | Jun 3, 2022 |
| Updated | Jul 11, 2022 |