300mb .duf scene with one V4, one M4, and one Genesis in DS4.6?

something_soon_2fbb9d78d6

Please, why would this be? I read on the forum something about 'saving character presents' and the materials and whatnot, but it really made no sense to me.

Anyone have any ideas why saving such a basic set up would be over 300mb? DS3 would have it at 40mb-ish, if I remember.

Thank you.

JimmyC_2009

I have no idea how it saved so large.

I just tried this as a simple test. I loaded Genesis, then V4, then M4, but I did not add clothing or hair or lights or cameras. I saved the scene as a .DUF scene file, and it saved at 2.32 MB (2,440,261 bytes).

Can you give a list of what is in the Scene?

Please, why would this be? I read on the forum something about ‘saving character presents’ and the materials and whatnot, but it really made no sense to me.

For information on how to save and use Presets in general, you should download the new userguide available here:
http://docs.daz3d.com/doku.php/public/software/dazstudio/4/userguide/start

You can also save single parts of a scene, say a character, clothed, posed and ready to use in any new scene. Select the object you want to save in the Scene pane (a figure, lights, camera etc.) then Go to File > Save As > Scene Subset. You can then merge that saved object into any new scene that you create.

JimmyC_2009

You can also have a look at this thread which may explain how the DUF format is used when loading and saving DS3 .DAZ Scene files, and how to best use it.

http://www.daz3d.com/forums/discussion/13019/

nDelphi

JimmyC_2009 said:

Can you give a list of what is in the Scene?

Yeah, he needs to figure out what is in the scene that might cause such a large file.

I am working on a huge scene with so many different objects, including a section of Stonemason's The Big City; the new Imperium set I bought at Rendo; an ocean; a Skydome; many low poly trees; one V4 character with a high poly Shield, a Spear, parts of two of Val's armor clothing for V4; and two low poly cars, and my file is at 28.6 MBs at the moment. (I might have missed an object or two.)

something_soon_2fbb9d78d6

I went right back to basics on this. If I save Genesis with Genesis clothes, there's a tiny file size. If I save Genesis with a couple of legacy items (hair prop, gloves, top, and bottom), then the file size climbs up to nearly 30mb.

Accepting that it's legacy items which make a bigger file size - how can I lower the size? Something to do with presets? Is it the maps or the geometries? I had a look on the links kindly shown but it seems quite ponderous whereas DS3 had things streamlined.

So confused @__@

Jaderail

Without more info like Which legacy files not much can be suggested. All object files are converted to a DATA file at load in DAZ Studio. Some of the Older content items have a BAD Mesh that includes things such as Ngon's which will cause a much larger file. But that still should not cause a 300mb file. Something in that one file sounds to me like it was writing BAD bad code to the Scene file.

Bejaymac

The problem with using "legacy" content is that it isn't native to DS, even the stuff you autofit to Genesis isn't native until you save it out properly.

By your post I take it your loading Genesis, autofitting V4/M4 clothing to it and then saving it as a scene, this is problematic as the clothing might now be TriAx rigged but it isn't DSON native, what you have is a temp asset file created during autofit and a pile of data in RAM. Saving that as a scene or subset leaves DS 3 choices on where to write all of that data, dump the whole lot into the DUF file, create asset files for it all and dump them in the "data\auto_adapted" folder, or a mixture of both.

What you are "meant" to do is load Genesis/G2, autofit the clothing you plan to use in your scene, then save out each item separately using "File > Save as > Support asset > Figure/Prop asset", this will take those temp files and data in RAM and give you DSON native content instead. Once you have saved out everything in this manner you can delete those autofitted items from the scene, and load in the DSON versions from thier DUF files, working like this will mean your scene files are tiny as only the required data is stored in them, rather than the entire item.

Props also cause big scene files, doesn't matter if it's a PP2, HR2, OBJ or imported formats like DAE or FBX, as DS usually writes the entire mesh data directly into the DUF, so it's usually best to "Figure/prop asset" them as well.

Poser figures aren't native to DS, so our scene formats have never worked well with them, with 4.0 and older you got a hefty DAZ file and several thousand user unfriendly DSO, DSD & DSV files dumped into the data folder, with 4.5+ you can get a fairly hefty DUF file and several thousand DSF asset files dumped into the data folder.

something_soon_2fbb9d78d6

Bejaymac said:

The problem with using "legacy" content is that it isn't native to DS, even the stuff you autofit to Genesis isn't native until you save it out properly.

By your post I take it your loading Genesis, autofitting V4/M4 clothing to it and then saving it as a scene, this is problematic as the clothing might now be TriAx rigged but it isn't DSON native, what you have is a temp asset file created during autofit and a pile of data in RAM. Saving that as a scene or subset leaves DS 3 choices on where to write all of that data, dump the whole lot into the DUF file, create asset files for it all and dump them in the "data\auto_adapted" folder, or a mixture of both.

What you are "meant" to do is load Genesis/G2, autofit the clothing you plan to use in your scene, then save out each item separately using "File > Save as > Support asset > Figure/Prop asset", this will take those temp files and data in RAM and give you DSON native content instead. Once you have saved out everything in this manner you can delete those autofitted items from the scene, and load in the DSON versions from thier DUF files, working like this will mean your scene files are tiny as only the required data is stored in them, rather than the entire item.

Props also cause big scene files, doesn't matter if it's a PP2, HR2, OBJ or imported formats like DAE or FBX, as DS usually writes the entire mesh data directly into the DUF, so it's usually best to "Figure/prop asset" them as well.

Poser figures aren't native to DS, so our scene formats have never worked well with them, with 4.0 and older you got a hefty DAZ file and several thousand user unfriendly DSO, DSD & DSV files dumped into the data folder, with 4.5+ you can get a fairly hefty DUF file and several thousand DSF asset files dumped into the data folder.

Bejaymac, you just won the internet. Thank you so much for your advice!

Richard Haseltine

If the clothing is a figure, AutoFit it to Genesis or Genesis 2. Props and converted clothing can be saved as assets - File>Save as>Support Asset>Figure Prop Asset. That will reduce the size of saved scenes, though of course the data is still on your system so for items that are used only once there is no net saving.

something_soon_2fbb9d78d6

Richard Haseltine said:

If the clothing is a figure, AutoFit it to Genesis or Genesis 2. Props and converted clothing can be saved as assets - File>Save as>Support Asset>Figure Prop Asset. That will reduce the size of saved scenes, though of course the data is still on your system so for items that are used only once there is no net saving.

Thank you so much for your help. So for figure clothing I should just load it, Autofit it to Genesis, then save the scene in DSD4.6 - none of this conversion malarkey?

As for converting Props (and Materials for that matter) the process just seems a little 'clunky' to me - like it's something that should happen behind the scenes of the program. I'm really not sure if I have much use for Daz 4 atm, unless it's specifically for Genesis usage.

Thanks again for your time!