Piercings Pack for Genesis 9 missing files?
butterflyfish
Posts: 1,268
in The Commons
I installed Piercings Pack for Genesis 9 via DIM, and there is nothing there. It's a 367 kb file. The manual .zip file is 22 mb. So I guess I can install it that way. But can anybody else confirm this? Or did I just screw something up? Do I need to open a ticket?
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
I don't have that product but that does not sound right. I would try uninstalling the product in DIM and removing the zip file from your hard drive. Then if you click the Install Manager Ready button it should queue up the DIM product for re-download and installation again. When it's re-installed you can right click it and check package contents - make sure the list of files matches that from the wiki: http://docs.daz3d.com/doku.php/public/read_me/index/88571/file_list
If you get a tiny file again which is missing the files in that list then I suggest filing a ticket with support with as much info as you can gather.
OK, I just tried that. After I uninstalled and deleted the file, it showed up in DIM as ready for download. And DIM said it was going to be 22 mb. But then when it downloaded, it only says it's a 367 kb file. Frustrating. Thanks for the idea, though. I guess I will file a ticket.
Filed a ticket, and now I had to update it. I looked in my download folder, and it did download the whole 22 mb file. But DIM still thinks it's 367 kb, and only installs that much of it. So weird. I'm surprised this hasn't happened to anyone else. Or maybe nobody else bought this?
Well, it's a pretty new product so perhaps others who bought it have not got round to trying to use it in a product yet. Also, it may only be an issue with the combination of that product and DIM so anyone using Central or Connect may not have any trouble and as you have seen the manual zip seems fine so those that like to install stuff manually would not have noticed.
I'm interested to know what does DIM show if you right click on the product and select "Show Installed Files" - this should give you a list of all the files that it has installed and a hyperlink to them in the filesystem. If the files should be there but are not they will be "greyed-out". How does this list of files compare to the ones in the wiki link? Also is it the same (possibly truncated) list of files that DIM shows in the "Show Package Files" option. It does seem odd that it's downloading a file that is much smaller but still more than an empty file would be and is seemingly installing what it has without error. Due to the difference in filesize I would guess that perhaps all the images are missing from that zip - but then if it is downloading the full 22mb it seems odd that it is not "seeing" it all.
Show installed files shows most of the files greyed out and italicized (see image). There are 3 more hyperlinked files at the bottom of the list, but they didn't fit in the screenshot. Those are all from the support folder.
Show package files appears to be the same list as show installed files.
Looking in the zip, it looks like all the files are there.
I even checked the manifest file in case there was a typo, but if there is, I couldn't tell.
If I go ahead and install from the manual zip, will it screw up DIM if it ever gets fixed?
Ahh, right. If "Show Package Files" has the full list of 505 files then that indicates to me that it IS seeing the 22mb zip. This, combined with the screenshot which indicates that ONLY the files inside data and Runtime/Support are ACTUALLY installed, suggests that perhaps the issue is with the Manifest.dsx file.
If you manually extract the DIM-downloaded zip file (not the actual manual zip) into a temporary location. I believe you should see a Content folder and two other dsx files. If you first look inside the Content folder and check that this appears to have the correct structure - for example, does "People/Genesis 9/Accessories/Piercings Pack/Ears/PP - Ball Left Ear Anti-Tragus.duf" exist in that EXACT folder structure. If everything looks fine there then open the Manifest.dsx file in a text editor. Don't worry about the format but just focus on the parts that say VALUE= and look at the bit in quotes - those should list those relative paths EXACTLY. If there are any misspellings between the two then that is likely the isue and should be reported to Daz support.
My guess is that the first four lines beginning with "/data/Nikisatez/G9PiercingsPack" and the last three beginning with "/Runtime/Support" will match between the filestructure inside that zip and the VALUE entries in the Manifest.dsx and the rest will have some error on one side or the other. Or those lines may be missing altogether.
It doesn't look like there's anything missing or misplaced in the zip file.
I think I may have figure out the problem with the manifest file.
Example of code for working files:
<File TARGET="Content" ACTION="Install" VALUE="Content/data/Nikisatez/G9PiercingsPack/PP - Ball Stud Zero/Ball Piercing Zero.dsf"/>
Example of not working files:
<File TARGET="Content" ACTION="Install" VALUE="Content/People/Genesis 9/Accessories/Piercings Pack/Ears/PP - Ball Left Ear Anti-Tragus.duf"/>
The second one is missing the Nikisatez folder between Accessories and Piercings Pack. And that's where the files actually are.
You know, this is like the 4th product I've had to file a ticket on in the past week or so. What does QA even do?
edit: Ugh, never use the code tag. Fixed it.
Ahh, that looks like it's the cause of the issue then - that one change will have broken the installation for everything except the 5 other files that are there. Hopefully, if you update your ticket with your findings then they will be able to get the package fixed. Although unfortunately it's now the weekend so you may have to wait till Monday :(
It does sometimes seem that QA are really not doing a very good job when such obvious errors are slipping through. I guess we don't see anything that they do reject so don't really have the full picture.
Updated the ticket. Looks like they will have gone home by now, so yeah. Monday at the soonest.
I do hope QA is doing something. PAs are paying for it, and it's a disservice to everyone when they don't catch things like this.
Just fyi, this product has been updated and appears to be working correctly now. Yay for the tech support team and whoever fixed it!
Awesome, glad you were able to get it sorted :)