Vray 7 - Override Xref Materials XrefObject not working when not part of a multi/sub object material.

[Vizioen]

Something odd here. I have an XrefObject of a car model from Evermotion. When imported as XrefObject I get a group because it consists of multiple objects, inside all of them are XrefObjects with each of them having a single material (not part of subobject) applied.

Say I want to change the material on the license plate:

- I load the material from the license plate in the Slate Editor, I press override material and change the bitmap.
- I start IPR to check out the material, looks good.
- If I then use production render, either bucket or progressive, it ignores what I just did, it keeps the same material.
- If I replace the material completely by just applying another (regular non Xref) material on it, it works (although yesterday it didn't)

I tested this with other models and I came to this conclusion:

When using XrefObjects and their respective Xref material is only a single material and not part of a sub-object material, it will disregard the override of an XrefMaterial. But when overridden with a regular material it works. See screengrab (CLICK > I can't upload Gifs anymore? They are static?)

The thing is yesterday I could not even get the material to change even when applying a regular VrayMtl, today it works though, so I can't reproduce that anymore, must have been pebcak or something else at play.

This together with VMAX-13406 is really annoying for me to work with XrefObjects. XrefScene does not give you the same functionality at all as Vladimir suggested in this thread: VrayCryptoMatte, doesn't work with Xref Materials. - Chaos Forums I can't change XrefScenes in my scene itself, I can't duplicate, move, rotate, scale XrefScenes (easily) either. So this really starts to become difficult to work with them. I'm not sure this bug is a new one in Vray 7, or old one, I thought it used to work.

Btw this subforum has the title of V-Ray for Blender beta (when creating a new thread, check your browser title bar above) as someone already pointed out, it got me confused for a second.

[Vizioen]

Really something weird with the forum, I fixed some typos in the above post and it doesn't change, but when I click EDIT, I can see my latest changes.

[hermit.crab]

When using XrefObjects and their respective Xref material is only a single material and not part of a sub-object material, it will disregard the override of an XrefMaterial. But when overridden with a regular material it works.

It's already logged (internal bug-tracker id: VMAX-8420). It's a 3ds Max thing and concerns Production rendering only. You can workaround it by rendering via Standalone (V-Ray > .vrscene exporter > Export and Render).

[Vizioen]

Hi Aleksandar, thanks for the reply, I didn't find the thread that first reported this (now I did with the bugtracker number). Unfortunately the proposed workarounds are not a good solution for me.

Judging by the number (not sure if correct), this is quite an old bug? If I understand correctly, this is something Autodesk needs to fix? Is this something that Chaos communicates to them, or do we need to report this to Autodesk ourselves? If not Autodesk's responsibility, could this be bumped as well as VMAX-13406 please, both are really time consuming bugs.

Thank you.

[hermit.crab]

Judging by the number (not sure if correct), this is quite an old bug? If I understand correctly, this is something Autodesk needs to fix? Is this something that Chaos communicates to them, or do we need to report this to Autodesk ourselves? If not Autodesk's responsibility, could this be bumped as well as VMAX-13406 please, both are really time consuming bugs.

I meant that it concerns the V-Ray integration in 3ds Max specifically. Not sure if Autodesk is involved. I will ask around and see if I can bump their priority, though.

[Vizioen]

Thanks Aleksandar