Import custom morphs not detecting some directories

[Chuki Cicha]

Import custom morphs automatically opens the file explorer in the folder where there should be the morphs for the selected mesh. Though there are sometimes that with some meshes it doesn’t, I don’t know what could be happening, because it works with some meshes, but not with others. It just opens the file explorer in the last location I was.

‌

[Thomas Larsson]

This is known problem and quite irritating. The folder is deduced from the mesh url. However, the url is relative, and corresponds to the absolute location DAZ root path + url. It may happen that there are several absolute locations that correspond to the same relative url, and the plugin chooses the wrong one.

Maybe one could add a button to the file selector to switch to the other folders.

[Thomas Larsson]

You can control the favored location by changing the order of the content directories in the global settings. The plugin will try the content directories from top to bottom, and pick the first one where the relative url matches an existing folder.

[Chuki Cicha]

I have only one directory and it still doesn’t find some url’s

‌

[engetudouiti]

I think to detect what cause problem, Chuki Cicha need to offer object (mesh) daz info which cause issue.

Because script may try to use url property of mesh. which are attached when you import duf scene. like this pic.

then try to serch sub-directory of each mesh “/morph” directory

I suppose if the URL arelady changed or removed with your workflow.

or if there is up-date issue for blender bpy flie import function, to set folda.

About absolute path problem, I suppose if Thomas try

http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/samples/file_io/file_find/start

then convert all relative path to abs path.

and try to use the abs path in exported json and ebz , then attach those URL for mesh as prop.

Though it do almost same thing what we do by python in blender, but it seems more precisely get absolute path of each mesh (and rig) in current daz scene.

The relative path manner actually cause same issue, if we miss manage daz database file structure (sometimes we see duplicated item, which saved as same relative path, for multi root directory)

‌