Laubwerk trees making problems with seemingly every new VRay update

[Art48]

I recently posted an issue about the Laubwerk Trees plugin and since I updated again today to the new SP the scene crashes again for the same reason. I just thought I'll let you know since this may indicate it's an issue on VRay's end.
The last time (and first time) that crash occured was also when the file had been done with an older VRay version.

This is the thread I am refering to:
http://forums.chaosgroup.com/showthr...when-rendering

No worries, I fixed it by reloading the trees as stated in that thread.

[vlado]

Hm ok, we need to try and reproduce this here.

Best regards,
Vlado

[matanov]

The scene from the dropbox link is missing, please upload it again (if you don't want to share it publicly - peter.matanov@chaosgroup.com).

[Art48]

Here it is: https://www.dropbox.com/s/2otzbokjwt...blems.rar?dl=0

[matanov]

It's not crashing here.

[Art48]

And you don't get the null mesh error/warning? Not the same issue as in the thread I linked?

[matanov]

I get the warning, but it's probably caused by not loading some parts of the tree library, when the paths are fixed there is no warning.

[Art48]

Yeah I see that issue and the reason I think it's strange or could be a VRay problem (COULD be) is that it messes up the proxy files after a VRay update. Had that 2 times in a row now and the funny thing is that the paths are correct and the mesh files are there but for some reason I have to reload the mesh files after a VRay update. It is of course not a pressing issue and is easily fixed but it would be good to know why it happens after VRay updates.

[vlado]

We have not changed anything related to proxy handling in this build so it's really mysterious...

Best regards,
Vlado

[Art48]

Could you reproduce it? One computer with an older VRay version, load my scene, relink the meshes, then update and open the same scene again and see if the links are broken?

[Zdravko.Keremidchiev]

I try that but didn't manage to reproduce the issue, the links were fine.

[Art48]

Hm that is strange, then it seems to be an issue on my end - sorry to bother