Problems with importing materials into the Asset Browser

[Eden_Soto2]

I'm on R25 with the latest Arnold plugin and I'm consistently having issues when importing materials into the Asset Browser. If I import a material I've made where the image textures for the material are in the "tex" folder relative to the C4D document, once imported and dragged into a new document, the image references are still relative (just the original filename and extension with no path) without the "asset:\\path\to\image" type of formatting etc., so they all break... and furthermore, if I move to another machine and use the same Asset Browser library, the links will change from the actual filename (or asset:\\link type path) to something like "asset:\\file_XXXXXXXXXXXXX~" which becomes even more troublesome to relink all of them.

Is this a known issue? Is there a workaround for it? Maybe a specific way to import them into the Asset Browser so the links in the materials update properly?

[peter.horvath6V6K3]

The path should be changed automatically to the assetdb:// url format, when the material is added to the library. Not sure if it's a bug in Cinema 4D or something is missing from the plugin. I'll have to talk to Maxon to figure it out.

[peter.horvath6V6K3]

If I import a material I've made where the image textures for the material are in the "tex" folder relative to the C4D document, once imported and dragged into a new document, the image references are still relative (just the original filename and extension with no path) without the "asset:\\path\to\image" type of formatting etc., so they all break

This should be fixed in C4DtoA 3.3.10. If you still have any issues, please let me know.

if I move to another machine and use the same Asset Browser library, the links will change from the actual filename (or asset:\\link type path) to something like "asset:\\file_XXXXXXXXXXXXX~" which becomes even more troublesome to relink all of them.

Not sure about this one, that sounds like a bug in C4D rather than the plugin. Please check the 3.3.10 build if it fixes the issue. If not, please check if the same happens with a native C4D material or it is specific to Arnold.