Question about these log file types.
Catherine3678ab
Posts: 8,383
Made a few purchases in the last couple of sales ... noticed that I now have quite a few error messages in the log files. The acquired figures seem to morph nicely enough although some of the errors seem to be targeted to lashes and/or teeth. As several refer to Handspan's products, Wild guess is that some are using Handspan morphs and don't know how to use such as MR - just trying to link to them instead of incorporating them into their work.
At any rate: Do I need to do anything about these types of error messages? are they safe to ignore? tia
Could not find target property for formula:
Could not find output property for formula:
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
For the most part, it'll be ok to ignore.
The drawback is that the results may be wildly different than what you expect, based on the promos.
Depends on what files you are looking at as to wether there is an issue or not.
Basically those two warning types mean the same thing, can't find the file or property at the specified pathway.
Some times it's down to dependancies not mentioned in the product, all of the DAZ own characters that have an 8 in the name, have corrective morphs which are ERC linked to morphs in the head, body and expression morph packs, if you don't have those packs installed then the ERC links fail and you get those warnings in the log.
In some cases you get them thanks to someone at DAZ deciding to "reorganize" the sub folders in the Morphs Folder, products made before that happened need to be updated otherwise you get those warnings, the products will still work so long as nobody changed the internal ID of the morphs as they were moving them. I know a couple of Handspan's characters fell into this catagory, not sure if they have been updated since though.
Another way of getting them is from a morph asset with bad parent data, that file wont be loaded by DS, so any others that have an ERC link to it will cough up those warnings.
Most you can ignore, some you can get away with deleting the DSF files, but any caused by bad parent data need to be fixed as the product doesn't work right.
Well at least one of Handspan's characters weren't updated. One by OziChick is due to a missing character dependency which is not even mentioned on the Product Page. The rest I haven't figured out yet however in removing all the vendors' products shown, no error messages!
Carabelle for Genesis 8 Female does not mention any dependencies but we have this:
2021-01-02 13:50:00.686 WARNING: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5759): Could not find output property for formula: Genesis8Female:/data/DAZ%203D/Genesis%208/Female/Morphs/DAZ%203D/Eva%208/FHMEva8.dsf#FHMEva8?value in file : /data/DAZ%203D/Genesis%208/Female/Morphs/OziChick/Carabelle/Carabelle%20Head.dsf
Hay! Fooled the OziChick call for Eva 8 [made my own Eva 8 from Eva 7] ... so now G8F loads without that particular error message. Funny thing though, when applied, Carabelle doesn't appear to even use Eva 8?! oh well ... off to the next
Anybody know what this is referring to?
eta: There is another file also called Kinsley Body. Seems all the working files [icons in D/S] call for Kinsley Body. So I removed KinsleyBody from the folder. Genesis 8 F loaded with no more errors for this one then. Hmmm ....
......................
Keyana by Handspan is not an old one, it's a new one. I put in a CS Ticket for this one.
..................................
Line 23 of that file is missing the closing quote and comma at the end of the line.
Okay thank you. I'll go see if I can find line 23. [haven't a clue how people count those]
Are we on the same page? These are the error messages.
Wordwrap rather negates my attempts to count lines. So the ", goes after which words?
Found an online line counter ... didn't help. The first errors were just replaced with illegal string errors then ... so hopefully CS can get it ironed out. In the meantime, she still looks pretty and her teeth look fine.
Sorry, that was in reference to
I don't have Keyana, so I'm not sure about that one...
Glad I asked then ;-) thank you.
..............
update: Found that :-) But it didn't solve the problem :-( Back to drawing board -> another day ;-)
Nope. Solution remains to remove one of the files. Situation is that there are 2 for the same location, big no-no. So I removed the one that the controller calls for. Since making these screenshots I also added in the card info so the body has an image too :-)
The rest of the long list is for another day ;-)
{gained over a minute off the loading time for G8F when I first removed "all" the problem files so yes I think this is worth a little time to address}
Cleared out a reference to a morph sold at a 3D store we are not allowed to post links to in this forum ;-)
Now Sisi loads without throwing error messages for the missing morph :-)
And wishlist is growing! Apparently there are some more Lashes and HD morphs available. So we shall just have to be patient while D/S loads those messages.
To fix the morph error messages for the Keyana character, filing a CS ticket did nothing. So I managed to figure it out and edited the file myself. So for those who have it, the file to edit is: MCM Keyana Teeth.dsf
Inside there are 4 places to edit the calls for morphs and their # info TO the names of the existing morphs. And now Keyana loads with no error messages :-)
The old error messages:
A few of the error messages were "solved" by purchasing the missing HD morphs. [yes they were listed on the Product Pages as being required]
A whole lot of error messages were zapped by removing a set or two of SY's free morphs.
A few of the log error messages are rather baffling. Files can't find themselves? all righty ...
BUT tonight's treasure is a little puzzle. Have no idea why there is a hierarchical mat file in the data morph folders for Pix Liliana but I've copied it over to the logical character's folder when it might be more useful ;-)
And yes, G8F loads a little smoother with fewer error messages :-)
One character left to fanthom!
These are its error messages:
Product = https://www.daz3d.com/pix-liliana-for-genesis-8-female
Can't find itself?
The character preset will have the eylashes set to auto load like you have with the main G8F preset, in the auto load settings you can set a MAT preset to be loaded at the same time, default setting means you need an hierarchical preset for it to work, and safest place to keep is in the data folder, even some DAZ Own come like this, even made a few of my own too.
Not so much it can't find itself, more a case of [what] is it doing looking for an eyelash morph asset ID inside the head morph asset.
Under one of my ultra-egos {Catherine3678ab}
That's interesting, good thing I left it in that folder then :-)
I was afraid that's what it was doing, sigh. Wonder if there's a way to extract that ...
https://www.daz3d.com/forums/discussion/comment/5502206/#Comment_5502206
^^^ should take you to my comment explaining G8 addons and their mat files.
As for Liliana, check the morphs folder, I suspect there might be a "Liliana Lashes.dsf" in there, it's going to be an empty (no morph deltas) control dial. Open it and check line 16, should look like this "id" : "Liliana Lashes", if it does then you found the right file.
Now you just got to edit FHM Liliana.dsf and change the pathways for the formulas.
Okay, thank you. I'll go back and try that. What I did for the moment was delete all references so I could get a load of G8F with "no error messages" :-)
Hmm ... there is no lashes file! Just the H. Mat file. I had copied that over to the main Content folder too, and it does only work as a mat file, does not load lashes.
I just downloaded a fresh zip too to check the folders.
So here are my notes of what I did to get rid of error messages. I also deleted a couple of useless shaping files for the eyebrows.
There were a few references to be deleted. On the last "}" there is to be no comma.