duplicate formulas - solved
sfaa69
Posts: 353
I get the "duplicate formulas" notice when I load any G2F or G8F figure, but not on any others. Is this common, is it a problem, or is it only a nuisance?
Post edited by sfaa69 on
Comments
It means that there are either two properties with the same name that link to a common property or there's an error in the set up of the link between a single property and another. If you go to Help>Troubleshooting>View Log File, scroll to the very end, and search backwards for Dupliate you should find the error messages - though if, as is usual, two properties are involved only the second will be listed. It is an issue - it will stop at least one property from working correctly - but it needs fixing on the creator's end (unless it's the result of using some kind of morph transfer tool).
Yes, this is an annoyance and it delays loading the figure. The only way I've found to fix it is either 1) check by loading the figure after installing any new product, and if it starts, uninstall that product and contact the creator, or 2) manually track down the one listed in the log and find out which product it belongs to, then uninstall it and contact the creator.
It sure would be nice if there was as way to analyze these issues in more detail and automate resolving them somehow.
Since this happens with every G8F character, I went back to the G8 Essentials and loaded the base G8F figure and the error appeared. So the developer in question must be DAZ. Considering this happens to everybody, why wouldn't it be fixed? Or is it possible that it is one of the morph packages, and if so, how would one track it down?
That is not a correct intetrpretation of the results. When you load a Genesis figure it reads in all of the morph assets, though ti dicards the actual shape data until it is needed, so an issue with an installed morph or a clash between two morphs will throw the error for every figure or scene that you load which uses the affected figure.
Going back to the question if it is caused by a morph package, how would one track which package it is and how would one be able to correct it? Or is it not worth the trouble?
As I said, look at the log file to identify one of the culprit products and the name of the morph, then it's necessary to figure out which other product has a morph of the same name and then you can report them (if they are both from Daz) or contact one or both of the endors (if not) for a fix. In the meantime you could unisntall ne of the products - at least in part - or it is possible to edit around the issue (but that might clash with any later official fix, so i'd be reluctant to do it).
personaly i read the log to found those "duplicate" and manualy "removed"
note:
all my duplicate moved are back-up is a safe place in case of needs,,
most of the time my duplicate formulas found on "Expressions" - 'smiles"
When your remove a formula, you lose that morph. Keep in mind that just because it shares the same name it doesn't mean it's making the same morphs.
For example, look through your shape parameters and randomly you may notice some with a (2) appended to the name. If you find this, edit the morph parameters and change the labels, then you'll see the two morphs separate in the parameters list. You'll discover there's probably two different morphs, but making the change to the label isn't permanent. They wiill revert back next time you load a character. It's the same issue with formulas. The proper way to resolve it is to ensure the morphs are generated from the start with unique names, but since there's no unique identifiers assigned to morphs during development or loading, the system relies on the morph developers to avoid conflicts.
Very much an annoyance but generally only occurs when there's a LOT of morphs loading or there are older morphs. If you wish to completely clear the issue, you have to start a new Library and install each morph package one at a time while testing the character load, otherwise you're making random sacrifices and hoping to uninstall/reinstall the morph package you want to keep.
So I discovered the culprit was Briallen HD for Alexandra 8. This problem was recognized this past summer and apparently corrected as a result, so that removing the old and reinstalling the new eliminates the problem. Too bad the wheel had to be reinvented, though.