Daz Packager

Comments

• Unseen Posts: 816

  August 9

  An excellent utility, very easy to use and works perfectly. Very quick. Thank you! :)
• raphaelbouvigne Posts: 12

  August 10

  Unseen said:

  An excellent utility, very easy to use and works perfectly. Very quick. Thank you! :)

  Thanks.
• rbeann_3771967b79 Posts: 19

  August 11

  Holy batman, I cant seem to get this to work. It looks like a winner but until I can get my hands around her. I still love the idea of this script. Maybe a little more info or video on getting it to work. Thanks anyway for your contribution.
• raphaelbouvigne Posts: 12

  August 11

  You have .NET 8 installed ?
  Did you run it from the command line?
• rbeann_3771967b79 Posts: 19

  August 11

  I didn't have the .NET installed yet. I tried but I'm having an issue installing it ie. the Net 8. I'll see whats the issue and try running the Packager again. Thanks.

   
• raphaelbouvigne Posts: 12

  August 28

  Hey, just checking back in — were you able to get .NET 8 installed and get DazPackager running? Happy to help troubleshoot if you're still stuck.

  For reference, here's the direct download page: https://dotnet.microsoft.com/en-us/download/dotnet/8.0 — you just need the ".NET Runtime" (not the SDK) for your OS/architecture (x64 on most Windows PCs).
  
  ---

  Update v1.0.1 is out!

  DazPackager now also detects two more common (and messier) zip structures found in third-party products:

  - Content folder nested inside another custom-named folder instead of being at the root
  - Known Daz folders (People, Runtime, data...) buried deep inside a custom-named library folder, with no Content folder at all

  Thanks to a community contributor for this addition!

  Grab the update on GitHub, RenderHub, or Renderosity (links in the first post).
• rbeann_3771967b79 Posts: 19

  August 28

  Still haven't gotten .net to work. i'll try the link that you referenced. Thanks
• jmucchiello Posts: 2,147

  August 29

  This is good. It would be even better if there were a parameter for setting the output directory. I'd rather the DIM zips not be in the same folder as the source zips when it finishes running.

  Thanks for listening.
• barbult Posts: 27,528

  August 29

  I would think that you would want the output zips to go into your DIM Downloads folder, so you could open DIM and install the products. 
• jmucchiello Posts: 2,147

  August 30

  barbult said:

  I would think that you would want the output zips to go into your DIM Downloads folder, so you could open DIM and install the products. 

  I have a directory with Renderhub download zips, for example. I don't want the output DIM files there. And I don't want to move them manually

  Also, I wouldn't put the DIM zips in with the Daz Shop DIM zips. I would changed the directory where DIM looks for the zips. This way DIM isn't constantly reading the files and trying to compare them to the Daz shop. My Daz Shop zips folder is 11864 File(s)  and 2.4 TB.  DIM takes over 2 minutes to reconcile those zips against "what's new" every time I load or hit reload in DIM. I don't need to make that set of zips bigger for no reason.
• Zicon Posts: 398

  August 30

  The assumptions made for naming install manager ready files are wrong. The correct naming scheme is documented:

  ^([A-Z][0-9A-Z]{0,6})(?=\d{8})(\d{8})(-(\d{2}))?_([0-9A-Za-z]+)\.zip$

  Do also note that the IM prefix is reserved for use by Daz 3D, packages from other sources should use a different prefix.
• raphaelbouvigne Posts: 12

  September 1

  Update v1.1.0 is out, thanks to your feedback!

  @jmucchiello — you can now choose where generated packages are written with a new --output <folder> option, instead of always next to the source file. Point it straight at DIM's watched Downloads folder if you want, or anywhere else. Works in single-item, batch, and multi-drop modes.

  @Zicon — you were right about the naming convention. Generated packages now use a DP prefix instead of IM, since IM is reserved for official Daz3D Store packages. Thanks for pointing that out with the exact regex, that made it an easy fix.

  As always, keep the feedback coming — it directly shapes what gets improved next.

  Grab the update on GitHub, RenderHub, or Renderosity (links in the first post).
• jmucchiello Posts: 2,147

  September 1 edited September 1

  Cool. Thanks. Now to find all my original downloads of 3rd party stuff. :) :)

  BTW, The Github readme still mentions the IM prefix.

  Post edited by jmucchiello on September 1
• raphaelbouvigne Posts: 12

  September 1

  A mistake, I will update Readme/doc. later.
• raphaelbouvigne Posts: 12

  September 2

  DazPackager v1.2.0 is out!

  Optionally auto-delete the source after a successful package, and save a full run log to a text file. README also fully updated to cover everything the tool now does.
• raphaelbouvigne Posts: 12

  September 5

  DazPackager v1.3.0 is out!

  Fixed a detection bug affecting some products with loose preview/readme files at the zip root, extracted-folder scanning now matches zip scanning, and dropping a folder full of zips onto the app now automatically batches them instead of failing.
  Console window also stays open after a drag-and-drop run so you can read the result.
• jmucchiello Posts: 2,147

  September 5 edited September 5

  Is there any way to have this handle the same product spread out across multiple zip files? Many large products are spread out among multiple zips for download size issues and I'd rather they weren't all added as separate products.

  Post edited by jmucchiello on September 5
• raphaelbouvigne Posts: 12

  September 5

  That's an interesting one, but I don't have any example of a multi-zip product on hand to work from. Could you point me to a specific product (or two) that ships that way? I'd like to see how the zips are actually split before figuring out the best approach — e.g. do they each have their own full Content/ structure, or do they share/complement each other's files?
• jmucchiello Posts: 2,147

  September 5

  I don't want to link directly to a random off site product. I've sent you a DM.
• raphaelbouvigne Posts: 12

  September 6

  Thanks for the example! Since these are 3 separate full zips (not split archive parts) that each contain a portion of the same product's folder structure — likely due to Renderosity's upload size limits — there's actually a simple way to handle this already:

  Extract all 3 zips into the same folder (so the body files and both texture sets end up merged together on disk), then drop that single merged folder onto DazPackager instead of the zips. It scans the actual folder structure regardless of which zip a file originally came from, so it'll see it as one product and generate a single package for it.

  This only works when the split is purely about file/folder content (as in your example) — it wouldn't apply to an actual bundle of separate products (body + hair + clothing sold together), since those genuinely are different products and should stay as separate packages.
• jmucchiello Posts: 2,147

  September 6

  raphaelbouvigne said:

  Extract all 3 zips into the same folder (so the body files and both texture sets end up merged together on disk), then drop that single merged folder onto DazPackager instead of the zips. It scans the actual folder structure regardless of which zip a file originally came from, so it'll see it as one product and generate a single package for it.

  I know how to get it to work. I was asking if your app could handle it without my intervention. For an automatic tool, there's already a lot of steps for normal zips. (Such as processing things one at a time to set the author parameter.) If I had been making DIM compatible zips from the beginning, fixing one or two products downloaded today would be no problem. I have a daunting set of existing products to go through and this is just more steps in the process.

  My problems are mine. I know. Thanks.
• barbult Posts: 27,528

  September 6

  @jmucchiello if this freebie doesn't work out for you, take a look at Content Package Assist (Windows PC only). It is old, but still functional.You can drag multiple zip files onto it to create a single consolidated DIM ready ZIP file. It isn't free, but it is 80% off before other discounts right now, so pretty reasonable priced.
• raphaelbouvigne Posts: 12

  September 6 edited September 6

  I'm not sure if we can merge / combine multiple zip into one, but also in a scripted way...

  Post edited by raphaelbouvigne on September 6
• raphaelbouvigne Posts: 12

  September 6

  If you have many products split across multiple zips like this, here's a small PowerShell script that extracts every zip found in each subfolder into that same subfolder — no manual extraction needed one by one. Once done, just drop the parent folder onto DazPackager (or run --batch on it) to process everything.

  Requires PowerShell 5.1+ (built into Windows 10/11 by default).
  Test it on a copy of a few folders first before running it on your whole library, just to be safe.

  One caveat: this only works cleanly if all the zips for a given product share the same internal structure (all with Content/ at their root, for example). If one zip has Content/ at the root and another wraps it in a different parent folder, they'll extract as separate top-level folders and DazPackager won't recognize them as one product.

  txt

  txt

  powershell.txt

  894B