Material assignment switch

[andybot_cg]

This problem is still present. Just grabbed the latest build, and node assignments keep jumping around. Each 2.78 version has had this problem. The last build that worked was somewhere back in 2.77, July I think. Why does this problem keep coming back?

[mraaay]

I have the same problem with other built from nightlies.

[mraaay]

Hi everone,
I have the same problem with material assignment. Nodes switch randomly!
I using vrayblender3-2.78-d804fac-x86_64-windows with Vray Build 3.40.02
What built from nightlies it's stable?
Thanks!

Best regard,

Chris

[kontrolermpl]

I'm using vrayblender3-2.77-8141c15-x86_64-windows from 2016-07-14 with denoiser support and this is very stable build. I'm just waiting when bdancer make the new one with RT support.

[bardo]

I think that we'll have to use that old build... I've the same problem with the latest builds...

[andybot_cg]

bump. Can we get this fixed so we can use current builds? I've tried using a few different 2.78 builds, and all of them are broken with regards to this issue. Problem is, it doesn't start showing up right away - you work in a file, make some edits, then realize half-way through a rendering that some materials are gone.

[entrymedia]

I have pinpointed the issue and it occurs sometimes (not always) when:
- duplicating objects (shift + D, alt +D)
- copying objects from another file using ctrl+C ctrl+V
- doing redo in object mode ctrl+Z

It may appear randomly too, but mostly I spotted the problem in listed cases.

[andybot_cg]

I have pinpointed the issue and it occurs sometimes (not always) when:
- duplicating objects (shift + D, alt +D)
- copying objects from another file using ctrl+C ctrl+V
- doing redo in object mode ctrl+Z

It may appear randomly too, but mostly I spotted the problem in listed cases.

"pinpointed" ha! So pretty much any normal editing. It also seems to happen when editing the list of materials assigned to an object - deleting an unused material slot for example.

[entrymedia]

"pinpointed" ha! So pretty much any normal editing. It also seems to happen when editing the list of materials assigned to an object - deleting an unused material slot for example.

Yeah, but with this I have some insight to when I should save and be especially cautious (I currently work on a broken build, but I'll probably revert to older one if the issue isn't resolved quickly). I didn't notice the thing with manipulating list of materials. It seems to me that the problem occurs usually when at the same time multiple nodetrees are added or assigned to the object. Didn't have any problems when adding new materials one by one. Also, it seems to be fine when I copy models stripped of materials from one file to another.