Recent builds, issues with referenced vrmesh proxies

[snivlem]

If something in the code was changed since previous versions of V-Ray, would there be a possibility that corruption could occur if the scene was originally created in V-Ray 3.1 then rendered in 3.3?

[ivaylo.ivanov]

Sadly, yes, if you have saved it after opening with the bugged version. But the same will happen if you open it with 3.1, so it's still strange... If you are testing with another scene, it will help if you send it to the support again for investigation.

[snivlem]

I have been unable to reproduce the bug I saw last weekend too (I was using 3.3 when it happened to see if I could speed up a scene I was working on ).

As of this post I have only been able to get the mesh to "corrupt" in Maya's outliner with the unknown node icon using 3.3 - so it's not really a bug but a strange behaviour.

However it renders fine this time.

1) Reference in a proxy mesh to a master scene
2) Instance this proxy around a few times
3) Group the proxies together in one group (including original reference)
4) Save scene, close and reopen scene
5) Instance a proxy then remove it from the group
6) Save scene, close and reopen

For me using 3.3, the instanced proxies use the "unknown" node icon that Maya uses and not the mesh icon. Obviously just a cosmetic issue as V-Ray will render fine and the mesh in the viewport displays fine but this is the only way I can reproduce something similar to the bug you fixed.

If I even find out anything else I'll report back here. Thanks guys.