Imported library stuck at loading

[Jonish]

Hello
Since using newer VfR with cloud material library (5.00.02?) my custom library with mats and HDRIs is stuck at refreshing. There's three dots on its right and it doesn't go away. Library cannot be opened nor removed or refreshed manually. Rhino restart doesn't help. If I add the library to a new Rhino file, it takes <1 sec.

Cheers
Jonas

[Peter.Chaushev]

Could you please reproduce the issue, then grab the latest vray-neui log file located at %APPDATA%\Chaos Group\V-Ray for Rhinoceros\vrayneui and share it with us?
And a couple more questions:

• Does the issue only occur only when working on scenes created with previous V-Ray version?
• Is your custom library located on a mapped drive?

Kind regards,
Peter

[Jonish]

Hello Peter,

Thank you for your response. I will follow your steps and let you know when / if I encounter this problem again.

My custom library is located on a local drive, buuuut I do use re-saved Rhino template for all my projects with V-Ray settings originally created while using VfR Next. Should I recreate my template once from scratch, now that I'm using VfR 5?

Thank you and have a splendid new year!

Jonas

[Peter.Chaushev]

The V-Ray data stored in your template files, even if outdated, should not be causing any issues with the library assets.
Nevertheless, please see if opening the library in a brand new scene (no template) results in a different outcome.

Overall, the safest way to store V-Ray preset settings in templates is to keep the templates clean of any plugin data (including V-Ray) and instead load them as .vropt files.
The .vropt files are best used within the same major V-Ray version (e.g. v4 files vropt files used only with V-Ray Next. v5 with V-Ray 5, etc).
If you wish to update old .vropt files, best practice is, as you guessed, to recreate them manually.

Kind regards,
Peter

[pavol_pastork]

The V-Ray data stored in your template files, even if outdated, should not be causing any issues with the library assets.
Nevertheless, please see if opening the library in a brand new scene (no template) results in a different outcome.

Overall, the safest way to store V-Ray preset settings in templates is to keep the templates clean of any plugin data (including V-Ray) and instead load them as .vropt files.
The .vropt files are best used within the same major V-Ray version (e.g. v4 files vropt files used only with V-Ray Next. v5 with V-Ray 5, etc).
If you wish to update old .vropt files, best practice is, as you guessed, to recreate them manually.

Kind regards,
Peter

Hi Peter, I have the same problem with custom loading stucking. I tried to recreate my template from scratch but problem with loading persists even in a file without template. I cannot delete stucked library and re-import it.
Thanks for solution.

[Peter.Chaushev]

A solution for this problem will be included in the upcoming v5.1 update of V-Ray for Rhino.

Regards,
Peter

[Jonish]

Thank you, Peter!

[pavol_pastork]

Now it works, thank you.

[konstantin_chaos]

Great to hear!