Nice ! though it's really odd... a DSF links to a DUF..., haha ~
Odd, but sadly not all that unusual in my experience, I've found the parent pointing at non existing DUF files, non existing DSF files, hell I've even found long randomly generated strings of characters instead of a pathway/file name.
No idea how the **** they do it, as DS will add the correct parent data to the morph as it's being imported into DS, which then get's saved into the DSF file.
Odd and odder... I almost handle these stuff everyday...I've never experienced that there's a definition of DUF in DSF. As for long randomly generated strings, yep, I've seen that before with SBH geometry, more or less.... Well, "parent" data in DSF should be also a geometry / node definition from DSF rather than DUF...
I'm still wondering... odd...
Here I can't add dsf file but I can show.
That was almost what I imagined but was what I could not reproduce either... Anyway, just follow the SOP and correct steps for saving assets in the future.
Comments
That was almost what I imagined but was what I could not reproduce either... Anyway, just follow the SOP and correct steps for saving assets in the future.
If you want to keep the morph then you will have to change the "parent" line.
For G8F the line should read as "parent" : "/data/DAZ%203D/Genesis%208/Female/Genesis8Female.dsf#geometry",
and that includeds the , (comma) at the end
I even doubt if the data in that DSF is "correct".... and if there're ERC formula data, OP will have to check n replace as well.