Loading...
> >

Duplicate formulas on a figure

jedijuddjedijudd Posts: 606
in Technical Help (nuts n bolts)

Are these bad? I have had these for a very long time with V4 and not noticed any problems, I just started getting them with G8F with a figure I recently purchased

Comments

  • Richard HaseltineRichard Haseltine Posts: 102,729

    They mean something isn't working  -either two different properties haev the same name, and are linked to another property in each case with the same name (that is, there's code saying Link "X" to "Y" in two products, and X is the same in each or Y is the same in each or both) or it means that a single product has two instructions to link X and Y (perhaps as the esult of running ERC Freeze twice without baking between, perhaps as a result of hand editing). At best it's causing a linkage not to work as intended, at worst it may actually be blocking a property from working at all.

  • FenixPhoenixFenixPhoenix Posts: 3,118
    Richard Haseltine said:

    They mean something isn't working  -either two different properties haev the same name, and are linked to another property in each case with the same name (that is, there's code saying Link "X" to "Y" in two products, and X is the same in each or Y is the same in each or both) or it means that a single product has two instructions to link X and Y (perhaps as the esult of running ERC Freeze twice without baking between, perhaps as a result of hand editing). At best it's causing a linkage not to work as intended, at worst it may actually be blocking a property from working at all.

    Richard, do you know if there's a way to figure out which formulas/products are causing the conflict? I've been getting the "duplicate formulas" since a long time as well, but with so many products, I wouldn't know where to even begin to figure out what's causing the message.

  • Richard HaseltineRichard Haseltine Posts: 102,729

    The log file will show the second proeprty that is actually triggering the issue, but it won't show th first (if it's a conflict between two products, which is most likely with something that has been through QA).

  • vwranglervwrangler Posts: 4,902
    edited April 2019
    FenixPhoenix said:
    Richard Haseltine said:

    They mean something isn't working  -either two different properties haev the same name, and are linked to another property in each case with the same name (that is, there's code saying Link "X" to "Y" in two products, and X is the same in each or Y is the same in each or both) or it means that a single product has two instructions to link X and Y (perhaps as the esult of running ERC Freeze twice without baking between, perhaps as a result of hand editing). At best it's causing a linkage not to work as intended, at worst it may actually be blocking a property from working at all.

    Richard, do you know if there's a way to figure out which formulas/products are causing the conflict? I've been getting the "duplicate formulas" since a long time as well, but with so many products, I wouldn't know where to even begin to figure out what's causing the message.

    Male-M3dia described a way to trace the error, for a different product, in this post, and I traced it through in this next-to-last post. It is a royal pain to trace them and figure out what's going on.

    It also helped that both the corrections for Growing Up and M3D Clayton were relatively recent; it made tracing the first product much simpler, because of the way the error occurred.

    Post edited by vwrangler on
  • FenixPhoenixFenixPhoenix Posts: 3,118
    Richard Haseltine said:

    The log file will show the second proeprty that is actually triggering the issue, but it won't show th first (if it's a conflict between two products, which is most likely with something that has been through QA).

    Thanks, it's going to be quite a process to figure it out, I expect.

     

    vwrangler said:
    FenixPhoenix said:
    Richard Haseltine said:

    They mean something isn't working  -either two different properties haev the same name, and are linked to another property in each case with the same name (that is, there's code saying Link "X" to "Y" in two products, and X is the same in each or Y is the same in each or both) or it means that a single product has two instructions to link X and Y (perhaps as the esult of running ERC Freeze twice without baking between, perhaps as a result of hand editing). At best it's causing a linkage not to work as intended, at worst it may actually be blocking a property from working at all.

    Richard, do you know if there's a way to figure out which formulas/products are causing the conflict? I've been getting the "duplicate formulas" since a long time as well, but with so many products, I wouldn't know where to even begin to figure out what's causing the message.

    Male-M3dia described a way to trace the error, for a different product, in this post, and I traced it through in this next-to-last post. It is a royal pain to trace them and figure out what's going on.

    It also helped that both the corrections for Growing Up and M3D Clayton were relatively recent; it made tracing the first product much simpler, because of the way the error occurred.

    Thank you very much for the links! It should help me get started! :)

  • IsaacNewtonIsaacNewton Posts: 1,300

    Can anyone tell me why, when DAZ Studio can detect this problem, it can't or dosen't point precisely to BOTH items causing the problem so that the problem can be solved immediately?

     

  • Richard HaseltineRichard Haseltine Posts: 102,729

    For one thing the problem can't be solved immediately, if you change the name of one morph presets will not work; if it's a result of double-ERC Freezing (which affects only one file) then removing the second link in the file would leave the link in its unoptimised state (assuming its need for adjustment was what led to the issue in the first place). Duplicate Formulas pretty much always need to be fixed by the content creator.

  • LeanaLeana Posts: 11,835
    edited April 2019
    IsaacNewton said:

    Can anyone tell me why, when DAZ Studio can detect this problem, it can't or dosen't point precisely to BOTH items causing the problem so that the problem can be solved immediately?

    I've never seen DS code but my guess would be that DS uses a standard function which trows a generic "there's a duplicate" error rather than a "this is a duplicate of xxx" error when it tries to add the property it's currently loading to the collection of properties already loaded (or something equivalent)

    I suppose it would be possible to add code to check which property conflicts with the new one though.

    Post edited by Leana on
Sign In or Register to comment.