Locate vrmesh in Component Definition path

[jiminy-billy-bob]

From what I've seen, if a path to an asset (ie a bitmap file or a .vrmesh) is wrong, V-Ray will look into the model's directory and try to find the asset there.

Would it be possible to do the same with Component Definitions?
If a Component Definition is a proxy and the path to the .vrmesh is wrong, look into the directory that you get with ComponentDefinition.path : http://ruby.sketchup.com/Sketchup/Co...nstance_method

Use-case :
A content creator might want to distribute assets as .skp files with already embedded proxies with materials, etc. These .skp files can be loaded in another project as components. But if the .vrmesh files are not located in the same location as the project, they are not found by V-Ray.
The end-used then has to repath every asset.

Ideally, V-Ray could have a list of the paths of all the Component Definitions (plus the model's path), and search in all these locations for all the missing assets. This expands the feature beyond .vrmesh files, and ensures accompanying bitmaps are also correctly loaded.

As this features already existes with model.path, I guess it shouldn't be too complicated to expand?

[Peter.Chaushev]

Hello, Thomas,
Posting here the same reply from our email correspondence in case anyone else is curious about this topic:

"We should already be doing this."

"Let's say you've got a V-Ray Proxy with associated materials within a component definition. This definition is then exported as an .skp. Finally, that .skp is imported in another project.
For the purpose of testing all files are in different locations:
Location A - the .vrmesh file
Locaiton B - the component definition .skp file
Location C - the texture files used in the proxy material
Location D - the other project .skp file


V-Ray will look for the .vrmesh file in locations A, B, and D. The texture image files will be searched for in C, B, and D.
If associated files are located elsewhere, their paths can be easily edited using Extensions > V-Ray > File Path Editor."


Kind regards,
Peter