Custom Node interprets MaterialAttributes inputs as float3

It seems that the Material Editor's Custom nodes don't handle inputs of type FMaterialAttributes correctly, and instead interpret them as float3.

Using Material Attributes as an input to a Custom Expression causes the HLSL Translator to create multiple CustomExpression# functions, for each used member of the Material Attributes, rather than using FMaterialAttributes.

1. Create a material like this, where a MaterialAttributes struct is used as the input to a Custom node:
   [Image Removed]
2. Observe shader compilation errors and/or generated HLSL code indicating that the MaterialAttributes input is interpreted as being of type float3

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

How to achieve HLSL Multiple Render Target in Material blueprints?

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 ?

I'm working on a VR Project and I cannot add Nav Mesh to the stairs??

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

How can i modify the param name in EQS node

Is this camera window implemented with SceneCaptureComponent2D&UMG?

Teleporter in the Creative Hub is Locked and cannot be accessed

How can actor's procedural mesh component variables translate positions with acotr?

What property of the Slider is the image used when dragging?