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
Ah that's what you meant @jestmart, I missunderstood than, sorry :)
And that do sound concerning for sure AprilYSH... oh well, we'll see how it goes. Still installing the thingies and likely will be doing that all darn night hahah
The above (2021-11 Hair for Genesis 8 and 8.1 Females) was updated on the 30th with the compatibility metadata.
http://docs.daz3d.com/doku.php/public/read_me/index/81555/start
I haven't tested it yet though, so no idea if it works or breaks something else.
UPDATE: the metadata for all my live products that had this issue were updated and should all show up in Smart Content properly, please redownload or refresh your metadata.
Update since I submitted my ticket:
QA have confirmed bad metadata via Connect (ie if installing by Connect or if you let DS update metadata.)
I have sent the list of 12 of my products affected. (See text file below for list.)
Awaiting fix.
Separate topic: Wilona Hair G3 metadata added, update available for download.
Sorry to necro this thread, but there is still a little problem with the Ursula Hair (just got it myself). Being so large a product, it has been split into two parts. Nothing wrong with that, happens all the time. Thing is, when this is done, all user-facing files are usually placed in the first part, and the overflow goes in the other part(s), usually the gagillion geometry or texture files needed, but not this time. The first part has GEnesis 8, the second has Genesis 3.
The one-and-only-one metadata file should only be inserted into the first part, and cover all the user-facing files. This is also okay, and will catch everything in the product that should be there. The problem is that if a second file has user-facing files, and no metadata file (which should never be repeated unless you are asking for trouble), DIM, or Studio, I don't know who does it, will create a default metadata file to handle what it thinks are orphaned assets, with little more than a Product name and Asset declarations. No Content Type, no default categories (hence Lost and Found), no Compatibilities, no CompatibilityBase, no ObjectCompatibilities and so on.
So, what has happened is that the second metadata file overrides any assets it has in common with the first metadata file. In this case, the Genesis 3 version of the hair gets cuts off, even if it has been properly defined in the first metadata file. A quick workaround is to re-import the metadata from the first part to replace that intruding from the second, or install the second part, then the first part. To avoid the problem initially, the user-facing files in the second part should be moved to the first part, then no second metadata file will be generated.
Thanks @NorthOf45 :)
Strange one, I can't replicate the issue. I'd like to get Daz to repair Ursula metadata but I'm not sure what the best solution is.
To illustrate: In the DIM zips there is only one support metadata dsx file, none for part 2. After DIM install, the hairs and their presets show up in DS Smart Content tab for both G8 and G3 versions of the hair. Then I make DS login and update metadata from Connect database (*shudder*) and that is where the dsx for part 2 comes from (weird!) This update didn't over-ride or disappear the hairs or preset compatibilities for me*. I restarted DS to be sure (as usual I don't let it login) and reloading G3 version the material and shaping presets still show up in Smart Content tab when filtered by context and having the hair selected. I checked G8F also and that hair version still has its presets also showing in Smart Content tab. DS 4.20.0.17
* it didn't disappear for me so this is why I'm not sure what the best solution is - if I ask them to remove the g3 asset line from the metadata dsx part 2 might that break smart content a different way? I'd guess not since it's already in part 1... But why isn't it disappearing for me but it did for you? I wonder if anyone else has experienced the same as you. Is your connection updating from part 2 last and somehow luckily mine loads part 1 metadata last? I can believe that since connect seems to glitch differently for different people lol sigh.
Agreed, there is no metadata file included in part 2, it is generated automatically by either DIM or Studio because there are user-facing files without any metadata support (old Poser products do this all the time to at least place the assets in a Product, but little else). The problem depends on which order the metadata files are processed. (I only use DIM, so I can control which one gets installed first. Connect? Never had it, never will). In my initial installation, the Genesis 3 version of the hair had no Content Type, no ObjectCompatibility, no CompatibilityBase, etc., but was part of the Product. All the material presets are djl links anyway, so they show the metadata from the original file from part 1. I didn't really go further than that, I don't really use Smart Content, but the omission bugged me. So, I scratched a little deeper and found what I believed was the source of the problem (the second generated metadata file), which was re-defining Genesis 3 hair with no metadata. I can reproduce it easily by installing part 2 after part 1. Re-installing part 1, or just re-importing the metadata from part 1, restores it properly (for some reason, you have to re-import twice before it changes in the content library).
There is nothing inherently wrong with the metadata file in part 1, it is, well, perfect. It's the content in part 2 that muddies the water. I will try moving the Genesis 3 hair .duf file to part 1 and see if everything works out regardless of the order (i.e., no second metadata file).
Okay, that worked out. I just moved the "Ursula Hair Genesis 3 Female.duf" and its two thumbnail files, and the folder icon file, into their own "People\Genesis 3 Female\Hair\Ursula Hair" folder in the first archive, and updated the manifest to make sure they got installed (and removed them from the second archive and its manifest). The rest of the files I left in place in part 2. No second metadata file was generated by part 2 when installed, so no impact on the metadata from part 1. G3 Ursula Hair's metadata was complete (Content Type, CompatibilityBase, etc.). Loaded a Genesis 3 Female and Smart Content showed Ursula Hair as compatible. Ursula Hair showed its materials and shaping presets as compatible, so I would say: all clear.
Well that was interesting. I didn't know DIM generated that part 2 support metadata dsx - seemingly because there was a user facing file (not counting djl files) in the second zip, even though the first zip had the complete metadata. Plus I thought that auto-generated dsx happened because I logged into Connect (the usual suspect.)
I have done as you did and moved the g3f duf to zip 1 and will request Daz to update it this way. I will note it for future products also, to have all user facing files in one zip, ie the first zip, which tends to contain the complete DazQA-made metadata. It seemed to be an issue with that autogenerated dsx but so long as there's a preventive measure I can deal with this. :)
Thanks very much @NorthOf45 for your troubleshooting and isolating the cause of this issue!
You are very welcome. May you never be troubled by this again...
The .djl files are meant to get their metadata, and everything else, from, the file to which they are pointing.
All packages should ahve the same metadata, when it is process only the entries matching files instaled from the current zip will be added to the database as part of the instyallation or reimporting of metadata - otherwise there would be no guard against bad data entering the database.
Yes, the djl files are not meant to get metadata directly - djl are irrelevant in the Smart Content tab anyway, they are "shortcuts" (asset links) for use in the Content Library tab. Actually assigning compatibility metadata to djl files caused a lot of problems with my past products resulting in most files getting dumped to lost and found (as discussed originally in this thread.) Since those were removed the metadata has behaved properly. ---> If anyone hasn't checked for updates to my past products, please do so :)
So if zip 2 had the identical metadata dsx in it as the complete one present in zip 1 this wouldn't have happened. That's a good point but not reliable during packaging as seen here (and evidenced by the auto-generation of the missing dsx file!) So I think making sure all user facing duf files are in the primary zip is a good way to hedge my bets ;)
You have always had it and will have it until DAZ decides to remove it (unlikely to happen).
DAZ Connect is the one inside DS and integrated into DS and if one is logging into DS, that is all DAZ Connect needs to start messing with the metadata.
But the metadata isn't in the manifest, it is in the /Content/Runtime/Support/ folder in the zip - the manifest in the zip just lists the included files and what to do with them. The file in the support folder should be present and the same for all packages as I understand it, and if it were missing from one (so that it wasn't actioned) reimporting the metadata from the other package should fix the issue - unless the paths were wrong in the package (or the metadata) in which case, as I said above, orphaned files don't get entered at all.
I am not quibbling over what is being seen or needs to be chnaged - just trying to avoid any misunderstanding of what it represents and why it is an issue.
That's missing entirely from the 2nd zip. It's not the only product I see it missing, I just checked a few multi part products in my DIM downloads folder... BUT it isn't a problem for these other products because their subsequent zips mostly contained texture images, no user facing dufs. I don't know if QA are told/required to copy the support dsx across all zips.
Yes, I believe North did that but other users might not know this workaround, so still need to fix at the source. :)
Oh, I know all about that. The first thought I had was the old 7-UP commercial. Crisp and clean, no caffeine, nevah haddit, nevah will...
I did an informal check of multi-part products in my collection, and found most had only one metadata file, in the first part, by a margin of about 4 or 5 to one. If it is a standard, it is not being applied very well. Personally, I am against repeating information, in case, for some reason, they diverge.
There are some cases, though, like with older Poser and StudioCF files where user-facing content must be included in each part of the product. Sometimes there is one metadata file in the Companion file, sometimes it is in both, and sometimes, when in both, they are different. But, those were early days, so maybe the process wasn't clear.
There are many other products which end up in Lost and Found. I make it a habit to cruise Lost and Found, and just go in the Category edit screen, find the product/articles, and uncheck them, and then make a category and check into the category I want. Gives a lot of flexibility and so much easier than wrangling a ticket or the metadata directly. I try to do this after each download, so I don't forget the original product. I find the Lost and Found most often goes by the Title given to a product, which is awkward to find, if you can't remember was it "Boho" or "Dark Ishkabibble" or "Glamourous Night" or "Night of the Iguana" or "Leslies Lovley Gala". I tie all such products togeter in a Category of my own making that I can remember, using the root product. Doensnt hurt the product, the metadata, or title, just forms an easy search term in Smart Content. If I had asked for tickets on all the products I have found in Lost and Found, I could have clogged up the ticket system.