Material type mismatch

A literal, parameter, call or output does not match its declared type. Authoring commands can retain some invalid drafts for correction, but shader generation requires a successful type check.

#Common causes

• A value has the wrong lane count, is nonfinite or cannot fit in f32.
• Call arguments do not match the operation signature, or the declared result type differs from the inferred type.
• A domain output has the wrong type, or a numeric value is used where a boolean or symbolic texture is required.

#Fixes

• Apply the attached material.node.type, material.parameter.reset or material.output.default command when its proposed correction matches your intent.

• Correct argument types and use explicit color conversion such as linear(encodedColor) where required.

• Use the attached material.node.literal fix to replace an invalid expression with a typed zero, or correct the literal in material.text.apply.

• Code: ARA3201

• Constant: material::TYPE

• Reported by: ara-material