Unsupported texture VRayMtl

[snivlem]

Just wondering if this is a bug or not?

I get about a dozen of these warnings when rendering;

// Warning: V-Ray : Unsupported texture VRayMtl //

I think it maybe caused by assigned a lambert to an object, then in the lambert using material override?



(I only do this to see textures and colours from VRayMTl in VP2)

[yolov]

It's about using one shader as an input to another where a texture was expected instead.
See the link for more info (we're going to publish other cases there too): http://docs.chaosgroup.com/display/V...calLimitations

My bet on your case is using a shader for the environment override - vray expects to find a texture there.

[snivlem]

I never use a VRayMtl as a texture or input into anything other than a VRayBlendMtl or Material Overrides on maya standard shaders, this is why it is strange.

Edit: On a new build of V-Ray it says this;

// Warning: V-Ray : 'VRayBlendMtl3.outColor' (type: VRayBlendMtl) is not expected as texture input to 'road_vp.vrayMtlEnvironmentOverride'. //
// Warning: V-Ray : 'bridge_revit:Surface_VRAY.outColor' (type: VRayMtl) is not expected as texture input to 'bridge_revit:lambert2.vrayMtlEnvironmentOverride' . //
// Warning: V-Ray : 'londside3_v01:concrete_VRAYMTL.outColor' (type: VRayMtl) is not expected as texture input to 'londside3_v01:concrete_mat.vrayMtlEnvironmentOver ride'. //
// Warning: V-Ray : 'londside3_v01:coloumns_VRAY.outColor' (type: VRayMtl) is not expected as texture input to 'londside3_v01:coloumns_mat.vrayMtlEnvironmentOver ride'. //
// Warning: V-Ray : 'londside3_v01:galvanazied_VRAYMTL.outColor' (type: VRayMtl) is not expected as texture input to 'londside3_v01:galvanazied_mat.vrayMtlEnvironmentO verride'. //
// Warning: V-Ray : 'londside3_v01anel_mesh_50_VRAY.outColor' (type: VRayMtl) is not expected as texture input to 'londside3_v01anel_mesh_50_mat.vrayMtlEnvironmentOverride'. //
// Warning: V-Ray : 'londside3_v01:zinc_dark_bump.outColor' (type: VRayBumpMtl) is not expected as texture input to 'londside3_v01:zinc_dark_VP.vrayMtlEnvironmentOver ride'. //
// Warning: V-Ray : 'londside3_v01anel_mesh_30__2_VRAY.outColor' (type: VRayMtl) is not expected as texture input to 'londside3_v01anel_mesh_30_mat.vrayMtlEnvironmentOverride'. //
// Warning: V-Ray : 'londside3_v01anel_locker_VRAYM.outColor' (type: VRayMtl) is not expected as texture input to 'londside3_v01anel_locker_mat.vrayMtlEnvironmentOverride'. //
// Warning: V-Ray : 'londside3_v01:wood_VRAY.outColor' (type: VRayMtl) is not expected as texture input to 'londside3_v01:wood_mat.vrayMtlEnvironmentOverride '. //

Which looks to be the issue? So am I correct that when we use Material override, we just uncheck the highlighted;

[yolov]

The new warning messages look this way because we wanted to make them more informative, so you'd know when there's an unexpected connection.
As for your screenshot - yes, the environment override expects a texture, not a shader. The warnings you posted are all for shaders connected to environment overrides in material override attributes.

[snivlem]

Thanks for clearing that up.