[Feature Request] Limited Input Flexibility in Material Functions

Ibtesam_Sadiq
Sun, 26 May 2024 15:18:58 +0000
Asset Creation

Current Behavior:

Material functions require specific data type inputs (Vector2, Vector3, Vector4, Scalar).

Built-in expressions within functions can handle various data types (automatic conversion).

Problem:

Creating separate functions for the same logic just to handle different vector sizes feels redundant.

Having all vector types as inputs in one function is messy and confusing.

Desired Behavior:

More flexibility in function inputs to handle different vector sizes (V1, V2, V3, V4) just like built in material expressions.

Are there other workarounds or best practices for handling different vector sizes in material functions without creating multiple functions?

1 post - 1 participant