Sharing is Caring.

ghastlycomic

So I set up a Share CG account and I thought I might share some of the models I've created. If I share a piece of clothing I created for DAZ is the .DUF file a self contained file or are there other resources needed in order for someone to use it in DAZ? I know the texture maps are a separate file.

mjc1016

Did you save it as a compressed file?

If you didn't then you can open it in a text editor and see what other files are needed and where they are located. Minimally you need the actual geometry file, the 'item' (duf file) and the textures.

If you did, either load it and save an uncompressed copy somewhere (don't overwrite the compressed one, as the compressed version makes a nicer download) and look.

Miss B

I agree you need the geometry file (.OBJ), because if you modeled the clothing for Genesis, only DS 4.5.x could use the .DUF file, but those using DS 4.0.x couldn't, or at least I don't think so.

ghastlycomic

So maybe when it comes to sharing it would be best just to share the .obj file since it's self contained and then people can fit it to the figure themselves?

mjc1016

Most people don't want to do that...they want a ready to use item...

That means, in the case of clothing a working, boned, fitted figure, at least a texture set and UV template. That assumes including the geometry...in whatever format.

Poser format files (cr2 and pp2) could contain 'internal' geometry, but are definitely not 'weight mapped' friendly formats used in DS4.x. The dsf can be a 'geometry' file, is weight map friendly and 'native' to 4.

I like geometry in an external obj, as that is probably the most compatible format there is.

Now, here's an item I made, earlier tonight...as an experiment. This is the top part of the duf file. I don't have any textures for it so there aren't any entries for them. The bold line is the geometry...

{
 "file_version" : "0.6.0.0",
 "asset_info" : {
  "id" : "/People/Genesis/Clothing/mjc/tshirtlo.duf",
  "type" : "wearable",
  "contributor" : {
   "author" : "mjc",
   "email" : "",
   "website" : ""
  },
  "revision" : "1.0",
  "modified" : "2012-10-29T03:31:09Z"
 },
 "modifier_library" : [
  {
   "id" : "Offset",
   "name" : "Offset",
   "parent" : "/data/mjc/thshirt/tshirtlo/tshirt.dsf#tshirt",
   "extra" : [

This is the 'info' portion of the dsf file...

{
 "file_version" : "0.6.0.0",
 "asset_info" : {
  "id" : "/data/mjc/thshirt/tshirtlo/tshirt.dsf",
  "type" : "figure",
  "contributor" : {
   "author" : "mjc",
   "email" : "",
   "website" : ""
  },
  "revision" : "0.0",
  "modified" : "2012-10-29T03:31:09Z"
 },
 "geometry_library" : [
  {
   "id" : "tshirt-1",
   "name" : "tshirt",
   "type" : "subdivision_surface",
   "edge_interpolation_mode" : "edges_only",
   "vertices" : {
    "count" : 254,

The vertex info follows that.

Here's the first few vertex lines from the obj...

o tshirt
v -5.42282 145.871 5.6475
v -5.73345 142.631 8.04852
v -0.006615 143.164 7.79256
v -0.006435 145.812 5.95584

Here's the same vertex lines from the dsf...

     [ -5.42282, 145.871, 5.6475 ],
     [ -5.73345, 142.631, 8.04852 ],
     [ -0.006615, 143.164, 7.79256 ],
     [ -0.006435, 145.812, 5.955841 ],

I suppose that it would be possible for the 'user' to just export the obj...but I like to include it in the zip anyway. Yeah, it's kind of redundant..,to me, it's 'complete'.