Tweet
Hey guys,
We recently upgraded to Vray 6.10.09 StableNighty Build but since then we are facing big issues with Forest and Xref scenes.
I have a very hard time reproducing our bugs in simple a scene we have several issues ranging from a complete crash or rendering stops at the "updating instances" step and alter the scene right after makes it impossible to render again.
That last bug led me to think that there is something that changed between 6.0.08 and 6.10.09 concering Xrefs and/or VrayProxy
For the test I created a new Teapot and exported it to vrmesh
Created a new scene with a new VrayProxy with the previously vrmesh inside.
then created a new Xref object targeting the freshly created 3dsmax scene with the VRayProxy inside.
When I open it I have the Teapot in viewport but when I switch the version to pick the EditPoly and then go back to VRayProxy it disappear this don't happen on VRay 6.0.08
Yes the Xref looks resolved and If I render it render properly but for some reason I don't think the Xref is really resolved.
In one of our test when we do the exact same actions the xref appear "unresolved". when you hit render the xref update to "resolve" and back to "unresolved" a the end of the render. (it make sense because the vray proxy is compiled only when you hit render, but this update could result in a crash at update instance when you have 100+ xref scattered in a forest of x units).
To me the xref can't resolve when it has a VRayProxy inside since VRay 6.10.09.
I know it looks a bit silly, but i'm trying to debug this since we updated the VRay version and to be honest i am running out of ideas on my end. Almost every of our scenes can't be rendered with our process since the last update. If I revert the version to 6.0.08 it works properly. (Of course we can't revert now because we were waiting for a bug fixes for an other issue).
I've attached the teapot scene too.
We recently upgraded to Vray 6.10.09 StableNighty Build but since then we are facing big issues with Forest and Xref scenes.
I have a very hard time reproducing our bugs in simple a scene we have several issues ranging from a complete crash or rendering stops at the "updating instances" step and alter the scene right after makes it impossible to render again.
That last bug led me to think that there is something that changed between 6.0.08 and 6.10.09 concering Xrefs and/or VrayProxy
For the test I created a new Teapot and exported it to vrmesh
Created a new scene with a new VrayProxy with the previously vrmesh inside.
then created a new Xref object targeting the freshly created 3dsmax scene with the VRayProxy inside.
When I open it I have the Teapot in viewport but when I switch the version to pick the EditPoly and then go back to VRayProxy it disappear this don't happen on VRay 6.0.08
Yes the Xref looks resolved and If I render it render properly but for some reason I don't think the Xref is really resolved.
In one of our test when we do the exact same actions the xref appear "unresolved". when you hit render the xref update to "resolve" and back to "unresolved" a the end of the render. (it make sense because the vray proxy is compiled only when you hit render, but this update could result in a crash at update instance when you have 100+ xref scattered in a forest of x units).
To me the xref can't resolve when it has a VRayProxy inside since VRay 6.10.09.
I know it looks a bit silly, but i'm trying to debug this since we updated the VRay version and to be honest i am running out of ideas on my end. Almost every of our scenes can't be rendered with our process since the last update. If I revert the version to 6.0.08 it works properly. (Of course we can't revert now because we were waiting for a bug fixes for an other issue).
I've attached the teapot scene too.
Comment