Version 51001 Material Asset Issue

[jason_cafferty]

Amongst other "issues" of stability I am experiencing since the update to 51001 that were not present in the initial 2 releases of v5 is an error in the asset managers material section. It displays the following error on some materials and then doesn't work requiring a total restart of both it and SketchUp to get it going again.

[DCHA34]

That's right. I got the same error message today.

[nikoleta.garkova]

Hi guys,

Thanks for sharing.

DCHA34 are you on Windows as well?

In case this error comes up, would it be possible to grab the vrayneui logs and forward them through our contact form so we can have a look? You can find them in:

• C:\Users\USERNAME\AppData\Roaming\Chaos Group\V-Ray for SketchUp\vrayneui - look for the latest vrayneui log files

You can forward them by reaching us through our contact form, just make sure to mention this thread in the email.

You've mentioned it is happening only with some materials, have you observed any patterns on when is this occurring?
I'm assuming you are not having issues on freshly created projects - can you please confirm?

Thanks and looking forward to your reply.

[DCHA34]

Hi Nikoleta,

yes i'm on Windows 10.

You can try this model :
https://3dwarehouse.sketchup.com/mod...3a4f4c27b/gate

With this model, I get the error message.

[kenancakir]

I tried it.. I open the file, without expanding the preview i drag some vray materials to the list and choose one of them and expand the preview part, it works.. As soon as i choose the gate materil it gives the error, and dragged vray materials are also gives that error after that.. When i delete the gate material at the beginning and open vray asset editor, there is no problem at all..

[DCHA34]

Voilà! That's exactly the problem.

[nikoleta.garkova]

Thanks for sharing, guys. I was able to reproduce this as well and I've logged it internally (ID number WEBUI-5809) so our developers can have a look. Will keep you posted.

[konstantin_chaos]

Hi guys,

The issue has been located and fixed.
The fix will make it in the next update (you can expect it soon soon).

Konstantin