Hi everyone, I posted here a few days ago about converting files from OBJ/MTL to DUF for Daz users. I want to make my products DAZ friendly. 

I am currently in the process of doing this and I have hit a stumbling block that I cant quite fathom. 

I am creating a DUF file from my items. 

The 'textures' path names however are pointing to a place on MY hard drive. 

So the question is... When you 'save as' DUF do the textures get included in the file? And if they don't, what do I do about the path names? 

I have concerns about this because with OBJ/MTL format for example, you have to edit the MTL file to point to a 'texture' within the 'zip' Do I have to do the same with DUF?

Thanks in advance for your help. 

Kutter

Hi again all... I have half answered this myself. 

I now know the DUF file does not hold the textures (as it's too small) but the duf file does indeed still point to the location of textures on MY hard drive. 

I can't edit the DUF file, so I am stuck.. Anyone?

Thanks

Kutter

You can edit a DUF, it is a text file, unless you chose the compress option when you created it.

It is easier to create a new DUF with the proper references.
Textures should go in "runtimetexturesYOUR_UNIQUE_FOLDER_NAME"

You should then zip all the files you created in appropriate structure so user can point to their content directory when unzipping

Thanks a lot Medzinatar,  I can do that. 

So tell me:

A daz user would be used to receiving a zip file that includes a DUF file and a runtime folder (with "textures-my_name" in it) that contains those textures.

IE:

ZIP-

Myname.duf
"runtime-textures-My_name" <---- Where this folder contains all the textures.

This would make sense to a Daz user? 

This all makes sense to me... However, I still don't understand how the DUF file will not point to MY hard drive? 

My Daz for example is installed on my D: drive... my customers may well have thiers on C:?

Would my pathname still not be "D:Daz3d-runtimes-textures-My_name ?"

Thanks for elaborating, I just want to make sure I get this right. 

Kutter

when you create a DUF, it uses relative paths.
It only creates absolute paths for items outside the content folder.
You should look at items zipped up for DS use, there are probably some in free stuff.

Content Folder
       |
Library Folder (Default is "My Library")
            |
    Other Folders (like data, People, Props, etc.)
            |
       Runtime

Make sure, when you apply the textures, that they are in RuntimeTexturesSomefolder and that that Runtime is in an active (selected in Content Directory Manager) DAZ Studio or Poser Content Directory (not in a sub-folder). If that is the case the .duf file should use relative paths.

Ok, so as long as I have my textures re-applied from the -runtime-textures-myfolder, when I create the DUF it will use relative paths?

So when a customer unzips the file they will just be able to slot textures into THEIR runtime-textures-myfolder and then Daz will know to look for them there?

Thanks again, 

Kutter

+1 for both of the above. When creating content, it also comes in handy to save a series of default folders with empty folders inside named appropriately. Many of the contents that are DS and Poser-compatible have a path as such:

Content--Runtime--Libraries, Geometry and Textures (in same subfolder of Runtime but they are their own folders) Character--Poses (inside Character). You get the idea. That way when a user unzips the package, they just Merge it to their base Runtime folder and those merge with existing folders. Bing Bang Boom, easy peezy. (In Windows at least. Haven't done for a mac but its gotta be close, right? =)  ) 

That way when you're ready to package a new product, just copy your default setup and name the interior folders appropriate to your new product. And have a default copy just in case. If you work when you're sleep-deprived (like I do) it's easy to forget! 

Do not put your product files inside a "Content" or "My Library" in the zip.  For a simple prop the structure would be like the following.

Prop

   |

   [Vendor's Name]

      |

      [Product here]

Runtime

   |

   Textures

      |

      [Vendor's Name]

          |

          [Product's Name]

             |

             [Product's textures here]

90% or more of the thousands of files ive used over the years includes a Content file. I dont with my products but its not a deal killer. it will still install to the same place. The OP said its for Daz Studio, and that is how the old libraries are set up to be both Studio and Poser friendly. 

Those 90% are wrong and so are the however many percent that have "My Library" folders.  Studio has never needed these, they are not like Poser's Runtime folder that is needed by Poser and Studio for Poser content.  By adding them you just increase the likelihood of the end user creating nested content folders and then wondering why they can't find their newly installed product.  And don't point to DAZ's new zip files having a "Content" folder, they where made to work in DIM which doesn't extract the "Content" folder only what is in it.  I suspect the "Content" folder was added to simplify coding DIM so it has a clear distinction between instructions and content.

Fair point, however, my own suspicions are that the majority of content creators (and sellers) path their files to be dual compatible. Granted, Studio is a bit easier to navigate in my experience, but even my own library of junk is mainly compiled in the Poser style. And yes, it's absolute hell to navigate, another reason of support for proper path names, but to open up created content to both programs, at some point the merch shops began requiring a certain path style and the one mainly used has a primary Poser Runtime setup (not Content), but everything else is attached to the heirarchy I noted. 

Is it optimum? Not by a long shot. Is it what what sites like Rendo and Daz want the file structure to be in order to sell content? Yes, and that is because a lot of people prefer one program or the other, so to make it easer (and because Studio reads a Poser library structure too), the jacked up 'legacy' style of folders is still employed. 

I'm not denouncing you by any means, but if a merch shop wants a certain style to be able to sell to both program parties, that's what they'll require at the end of the day. 

Hey again guys, 

I don't need to tell you I'm sure that I couldn't be any more confused. 

As a non DS user and after downloading 'lots' of different free stuff items I am no wiser than when I started asking this question.

I have downloaded at least 8 products, and not one of them is the same as the last.

Some of them have Docs & Settings and My Library folders, with HYPER complex paths in each!

Some just have Runtime folder with libraries and pose following in the path names

and yet others are just in their own named folder (such as 'books') with textures outside. 

I am not only confused about the pathing structure, but how does one actually put this together for a zip file?

Do I literally make blank folders (starting with for instance Runtime) then 'make the structure' inside that folder with empty folders?

Then in turn fill those folders with my product? Then zip THAT and post it?

I am so confused right now, and I have absolutely ZERO confidence that I could package this product and make it work for other DS or even Poser users?

And that's ANOTHER thing.. whats this about Poser? Is that different again?

I really need some clarity folks, else I'm just going to have to leave this product as it is as OBJ/MTL.

So far... I have created a DUF file that lines the books up nice and neat in DS, so that a user loading them in will have them in a convinient set up. But thats as far as I can go without some clarity. 

Thanks,

Kutter

Ok so further experimentation has led me to this point... 

I currently have my DUF file in 'C:---users-public---documents---My DAZ3D Library---Runtime---libraries---Props---books'

(i cant use a back-slash it seems it always disappears for some reason I take it thats because it's 'code?' Anyway you get my point)

and my textures in C:**---**users---public---documents---My DAZ3D Library---Runtime---Textures---books---texture_name

So when I 'save' this will the DUF file not point to these EXACT paths? 

If thats true what about people who, like myself, would organise this differently?

The similarity I see here is 'RUNTIME' and it seems sensible to somehow package my product in a 'RUNTIME' folder?? Yet the product will STILL look at the pathname above wont it?

I am still very foggy on this whole deal. But I AM trying! lol.

Please help! 

Kutter

Hi,

Generally DS products are installed outside Runtime folder with (almost) the single exception of textures. Your structure looks sound. If I have a folder "My DS Library" for all the DS and Poser stuff, then I would place the DS version of Books into:

"My DS Library | Props | Kutter | Books"

and textures to

"My DS Library | Runtime | Textures | Kutter | Books"

As Richard said if you set up these things within DS using an active library, then the saved paths should be relative, i.e. your disk letters and names will be subsituted on client system automatically. I am Mac user, I won't survive if products would have hard references to disk letter, but I'm using hundreds of DS and Poser products without problem. :)

The understanding of the difference between absolute and relative addressing is vital.  Relative is like getting GPS navigation instructions from where you are to where you want to go, therefore it alway works no matter where you are.  Absolute is like getting instructions that start at the largest airport in your region and going from there,  if you aren't actually at that airport the instructions are useless.  Studio and Poser have been told where your library or libraries start so files for them can use relative addressing.  If you add a "Content", "My Library" or any other folder as the top level folder you brake relative addressing so don't do it.  The examples above should read as follows to be proper:

Props | Kutter | Books

Runtime | Textures | Kutter | Books

You are correct, Jetsmart. In my example I tried to show where I would place my files before saving them with relative paths. :) Sorry for the confusion.

Thanks for your help guys, really.

But the question still remains.. How do I package this? 

I just don't understand the process. I have my DUF and textures as I have mentioned and you have told me they are good... 

Ok great, so I have them in the right folders.. But how do I package this in a zip file?

I'm sorry if I appear dumb but it seems all these replies are great but each time they seem to miss what I'm actually asking lol. 

Thanks again.

When you saved the project not only was a .duf file written most likely one or more 'assets' where written to the "data" folder.  The easiest way to get just the files you need for a project is to use a specific project library folder.  In your case make a "My Book Project" folder in c:/Users/[user's name]/My Documents/ and map the folder in Content Directory Manager as both Studio and Poser.  Now the important bit, move that library to the top of both Studio and Poser listing.  Copy the Runtime/Texture/... folders/files to the project library and add "Props" folder the project folder.  Under the Props folder you should add a [vendors name] folder and under that a [name of product] folder  Load your object(s) in to Studio and set up the surfaces.  Once everything is ready to save go to File Save as Support Asset Figure/Prop Assets and navigate to the [product name] folder and save.  In the pop-up make sure the Asset Directory is correct (in this example "My Book Project") fill in Vendor Name, Product Name, and Item Name.  For a simple prop you can ignore the metadata stuff.  Hit Accept and everything you need to zip up is all in this one folder with nothing you don't need.  Before closing Studio open Content Directory Manager and move the project library to the bottom of both Studio and Poser lists.