As I mentioned here, vray doesn’t quite work with the asset browser.
I recorded first impressions of importing objects into an asset browser.
First, I import the object directly from disk.
Then I try to import it into the database.
Then from database to scene.
Then, in parallel, the object from the database and the object from the disk.
As always, strange things happen with the materials.
And of course, it would be nice to see the correct viewport preview in an asset browser rather than a black chunk.
A vray icon in the preview corner to symbolize that this is a vray scene would also come in handy. Just like the stuff from Redshift.
I will still be testing the compatibility with the asset browser and I will write about it here.
Thank you for providing us with detailed information about the issue.
We already have this issue logged in our internal bug tracking system and I have mentioned this forum thread. (Issue number: VC4D-946) I will let you know when the issue has been resolved.
We haven’t added support for the new asset browser system yet. This is on our to-do list and will be implemented in the future. We will let you know as soon as we have any updates on the matter. Thank you for your patience and understanding.
This seems to be a C4D S24-issue too. When I try to drag assets from a scene into the asset browser, all images (TIFF, JPG, PNG) in the materials of this asset get lost. The textures are shown as being imported in the asset browser-database but their link with the specific material-shader seems to be broken. Those assets in the asset browser keep this error/broken links when I drag them from the asset browser back into the viewport.
Those materials with image-files in the shader-slots are corrupt and textures have to be relinked manually. The texture path of the relevant shaders of the reimported assets shows the correct link to the target-“folder” of the asset manager (“assetdb:///”+[Name of the category-structure of my database]) but the image doesn’t show up in the material preview of the material manager. 2sided material also has broken texture-links after import into the asset browser.
In the asset browser the preview of the image-files shows the correct preview while the 3D/asset-preview has black materials instead.
Tested with Vray5 update 1.4.
All folders in my category-structure are in the same database of the asset browser on my local harddrive.
Any help how to keep the links active and work with the asset browser in S24?
We are aware that this issue is also present in Cinema4D S24 and this is also mentioned in the internal report (VC4D-946) that Valentin was referring to. Maxon changed the way the assets are loaded in Cinema 4D S24, and they introduced a new asset browser. Currently, V-Ray doesn’t support loading assets from the new asset browser in Cinema 4D S24 and R25. We will let you know as soon as we have any updates on the matter.
Unfortunately, I tried to tame c4d asset browser, but I don’t like this kind of asset management. I don’t seem to be using it.
It would be nice to be able to create your own material and object libraries and add them to Cosmos Browser, but under the private category, or something similar. Cosmos unlike c4d asset browser creates a clear structure of files on hdd.
I would like to let you know that our developers have added support for loading assets from the new asset browser system in Cinema 4D S24 and R25. This fix is available in the latest stable build and can be downloaded from here. Please note that objects with assigned node materials won’t render proper previews in the asset browser but will be usable and will render correctly once reimported back into a scene. This is an issue on the Maxon side and we have reported it to their developers.
Thank you for highlighting this. I have reported this to our developers for fixing (bug ID: VC4D-1240). We will have a look at this issue and I will let you know as soon as we have any updates to share. Thanks.
Is there anything new regarding bug ID: VC4D-1240? We installed the last update from yestarday but the import/export issue with vray libraries is still present.
I am afraid that we don’t have any news to share about this bug yet. I have bumped its priority and will let you know once we have any updates. Thank you.
It would solve a lot of hassle if vray and cosmos assets work with the File Assets Paths list in the Preferences menu. That way, even if a asset path is inexistent if it exists in the paths list in preferences, it wound get it, load and render.
