- This topic has 40 replies, 10 voices, and was last updated 1 year, 10 months ago by
.
-
Posts
-
Upon reflection believe I owe you an apology.
Best advice I was ever given was not to interact with
anyone on the internet if you could help it, you simply
don't know who (or what) you are dealing with.
I got sucked in by your plea for help.
That was my first mistake.
Trying to help you was my second.
I can assure you if I ever see a request for help from
you again, I will do my level best to ignore it.
You may post further problems (and I am sure there will be many )without the fear of being "yelled at".
Again may I suggest pencil and paper as the way to go.
Best of luck, .....feeling you will need itInstalled Sephiroth and loaded it but didn't get this error. The only errors I got were all related to genesis 9 not being installed, but maybe this error appears only if you have G9 installed (also I'm using Daz 4.12).
I'm not an expert but there are two .dsf files containing the substring 'Sephiroth.duf", the first being
/data/Daz 3D/Genesis 9/Genesis 9 Mouth/Morphs/DazCover/Project S/XBMSephiroth Body.dsfand the other being XBMSephiroth Head.dsf in the same path.
The entire string is/Scenes/Sephiroth.duf#Genesis9Mouth-1but there's no file called Sephiroth.duf. However the file
/People/Genesis 9/Characters/DazCover/Project S/Sephiroth G9.dufdoes exist and it contains an object with the id "Genesis9Mouth-1" so maybe the .dsf files point to the wrong file and changing the path will fix the error?I had the exact same issue with this model back in the day, and yes, the file is messed up generating a message each time you're loading a G9 figure. It happens sometimes with some figures, generating an error or missing files message, or sometimes loading some unwanted morph each time you're loading the related generation figure (G9/g8, whatever) and you either have to delete the culprit or toy with the files, trying to rename things or set a different path if you know what you're doing
No big deal since it's just a message and doesn't makes the scene crashing or anything. That is mostly annoying.By the way, out of curiosity I tried Anna's trick before reinstalling the Sephiroth character: I'm still getting the same message
yeah the weird Sephiroth error doesn't happen if you don't have G9. it only happens when I load a G9 figure. You'd have to install G9 to see what I'm talking about
Maybe we both should tell DAZcover?
maybe they'll listen better if more ppl tell them about this error idkIt would be kind of weird for me to ask someone to give me support for an item I grabbed here for "free". 😉
Especially as it belong to the range or items I grab thinking "Oh, it might be nice to have it if someday doing some FF7 Fanart" and then never touch at all.
Here is my advice: unless you're using it on daily basis because doing series of pictures with this caracter for a weeks or months, uninstall the character, bring it back if you decide someday to do something with it: deal with the message and remove it from computer once done with the pic.Unless it's something crucial for Daz's daily use, it doesn't worth the trouble.
@khefrenn
oh oops I forgot most ppl here probably didn't get it legit xDI did pay for it though so for me this kinda feels like a waste of cash rip
I guess I'll just make an empty scene file and save it as "Sephiroth.duf" to avoid this error
Easiest solution most likely
Making an empty scene file might cause another error since Daz won't be able to find the #Genesis9Mouth-1 "property" in it. But it might not show an error dialog box and instead just write the error to the log file.
If you bought the thing, you should contact the vendor. You did pay for it.
Or maybe not, since the vendor might be a member here and they'll be able to figure out its you who shared their creation, lol.
🙂Go to currently used.
Make sure nothing is there.Currently Used does not always show all the morphs that get applied while loading a character. For example, there is this VO Sorg bundle at
Vo Sorg, And Young, and Male,and Male Young HD for Genesis 9 Bundle
which has a sneaky morph "Vo Sorg Body HD Details LV3" that loads while loading the base G9 character. But that morph does not show up in the Currently Used section even if you have hidden properties set to be shown. It doesn't even show up even when you Zero the figure, memorize and try to save modified morphs.Did anyone find a convenient way to detect such morphs?
Edit: This went unnoticed since I don't use HD morphs, and so its corruption to base G9 went unnoticed. I was able to spot it through the DS log files. Had I not checked the log files, this would have continued to bloat my scene files, creating an unnecessary dependency.
From the PAs site, "The character comes in a zip file, to be installed, with the Daz studio installer manager." I'm not sure what this means. Wouldn't you just extract the zip and place the files in the right folders?
I think we can now all agree that the problem wasn't a character affecting the DS prog itself, but a faulty character affecting another one (G9), which isn't the first time.I read this regarding "currently used" but I'm not sure if it's true or would help in your case-
"If one tries to look at "Currently Used", the OneFootNose can't be found on the list because the list only shows dials that have their current value set at something other than default - The default value for OneFootNose is 100%, so at dial value 100%, it is not 'used' in a sense that "Currently Used" looks at it. One can load the Genesis 8 Basic Female into an empty scene, and then "Zero the Figure" and check the "Currently Used" list, now the dial for OneFootNose should show up with a white zero value (white color is a sign of the value being something else than default)"
Had that error with g8,
From memory look at the directory stipulated in the log file.
It`l point to a morph directory.
Use a text editor to open each morph in that directory.
Do a "find" or "find all" for sephiroth.
You`ll see the culprit near the header somewhere.Delete the line- file save - ur done.
- You must be logged in to reply to this topic.
