Loading...
> >

Removing Non-Default Morph Values in Base G3F?

PangurBanPangurBan Posts: 28
in Daz Studio Discussion

Hi all

Is there a way to remove "inherited" values in a default figure? Somehow, my G3F now loads with some non-default settings (not sure how this happened, apologies for lack of specifics there), and now, as well as new G3F figures loading with these values, my pre-existing renders which also use G3F now seem to inherit these values as well.

I tried re-installing G3F Starter Essentials, but that didn't seem to solve the issue. As a kludge on new renders, I can just zero all morph values, but that doesn't help on pre-existing renders, and I'd really like to know how to fix it properly.

Any ideas?

Thanks

Al/PangurBan

Comments

  • murgatroyd314murgatroyd314 Posts: 1,542

    The problem is not in G3F itself, but in a morph file which has a default value other than zero. You need to identify and remove or fix the offending morph.

  • PangurBanPangurBan Posts: 28

    Hi Murgatroyd

    Great answer, thanks, that solved it. If anyone else hits the same issue, the solution was:

    • As Murgatroyd said, the issue was that one of the subdirectories in DAZContent\data\DAZ 3D\Genesis 3\Female\Morphs\ had the "tainted" morphs, not the base G3F, and this was being inherited whenever G3F loaded
    • To work out which one it was, I moved all the morph subdirectories into a temporary area, and loaded G3F in Daz Studio - it didn't pick up the taint, so this was clearly the right track
    • I then systematically replaced the subdirectories until the issue re-occurred (this wasn't have to be one at a time, I loaded about half of the remaining ones to see if it was in that batch, and so on) - this isolated the specific product had been overwritten with the tainted morphs

    I then re-installed the tainted product, and all was fine.

    Thanks

    Al/PangurBan

  • FletcherFletcher Posts: 63
    This has always been a PIA - rogue morph messing up a character. Care to share what product had the rogue morph?
  • mindsongmindsong Posts: 1,712

    if a re-install fixed the issue, it sounds like no particular vendor/product was involved, but rather an errant (re)save by the user or a script/util on top of an OK product.

    cheers,

    --ms

  • PangurBanPangurBan Posts: 28

    Heya Fletcher

    Yep, it must have been something I did, as the original files were intact, as mindsong says. Unsure exactly what I did to re-save over the originals, but hey, I know what to do if it recurs.

    Cheers

    Al/PangurBan

  • LeanaLeana Posts: 11,822
    mindsong said:

    if a re-install fixed the issue, it sounds like no particular vendor/product was involved, but rather an errant (re)save by the user or a script/util on top of an OK product.

    Or there was actually a problem and the product had been updated to fix it.

  • mindsongmindsong Posts: 1,712
    Leana said:
    mindsong said:

    if a re-install fixed the issue, it sounds like no particular vendor/product was involved, but rather an errant (re)save by the user or a script/util on top of an OK product.

    Or there was actually a problem and the product had been updated to fix it.

    truly a possibility... I didn't want to get a random vendor bad press if some rogue script (or unwitting user) was accidently damaging a perfectly OK product.

    you make a good point.

    --ms

Sign In or Register to comment.