One Library for both, Poser and DS ! How can i do it ?

jan_8a6b444a69

Hello at all,

i´m using DS 4.9 Pro for a longer time now. But i also have Poser 11 Pro, and for both i have a Library-Directory.
The Poser Standart-Content, which will be delivered with Poser is about 7 GB and my DS Content is about 20 GB.
On my DAZ Product-Download Page on the DAZ Website are about 300 Products. Some are with a native Poser-Installer,
Some With Native Poser Installer and DS Companion Files, Some are with DS Installer and Poser Companion Files, Some are DSON-Compatible, Some are not DSON compatible and some very old ones are with DS installer only. Now i thought, it would be great to have only one big library onto an external Drive, which i can use on my notebook too.
Here are my questions:

How does these Companion Files work ?
How does the DSON importer work     ?
How can bring it all together in ONE Library-Directory ?

 

Has someone an Idea ?

Any tipp is welcome.

Greets
Jan

Richard Haseltine

Just point Poser to your install directory from DIM (e.g. C:\users\Public\Public Documents\My Daz 3D Library) and point DS to the Poser content (the folder that holds the Runtime). In Poser, unless it's chnaged in 11, use the folder icon with a + at the top of the Library panel; in DS right-click Poser Fomrats in the Content Library pane and choose Add a Runtime Directory.

DSON is the native Daz Studio format  -the DSON Importer allows native DS files to be imported, though not all will work. Where theer are Poser CFs you need both the main DS filse and the Poser CFs installed to a library folder Poser know about - the PoserCF calls a Python script, the Python script tells the DSON Importer to load the native DS files; some Poser CFs will then apply native Poser materials.

 

jan_8a6b444a69

If i understand that right i have to put the Poser-Runtime in the same folder that holds the DATA-Folder of Daz-Studio.

If i maybe want to install "niceDSwoman1", given that it is DS compatible, than i have to install her in ../Runtime/Library/People/Female/niceStudioWoman/niceDSwoman1.duf !
After that i add the Poser Companion Files to the same folder where niceDSwoman1.duf resides in ?
And than i can use her in Poser, and in DS, when i implemented the Path to Poserformat in my DS-Preferences ?

If i maybe want to install "nicePoserWoman1" i have to install her in ../Runtime/Library/People/Female/nicePoserWoman/nicePoserWoman1.cr2 !
And then i install the Studio Companion Files to the Directory where "nicePoserWoman1.cr2 resides in. 
After that i can use it in DS and Poser ? 

All other DS-Files with neither poser- nor DS-Companion Files i install to the DATA-Folder given by the structure of DAZ Studios Library-Format because they are only usable in DS ?
But all that stuff wich is either native-Poser Content without companion-files or any other Content with companion files, i install in ../Runtime/../..

Is that correct ?

Or do i have to install only the Poser Companion files to the ../Runtime, while niceDSwoman1.duf resides somewhere in ../Data/../..
and install only the DS Companion Files ../Data/.. while nicePoserWoman1.cr2 resides in ../Runtime/Library/People/Female/nicePoserWoman/

Greets
Jan 

Richard Haseltine

The PoserCF files have all of the stuff that needs to go in the poser library folder, including a copy of the .duf file. What they lack are the textures and the asset files from the data folder, which come from the DSON core package (the native DS files).

Padone

Personally I would not advise to mix Poser and DS both in the same folder. Their structures are similar and compatible, but different. I'd rather point Poser to DS and DS to Poser as Richard explained in his first post. This way things are cleaner in my opinion. Because you have a folder for Poser only, and a folder for DS also containing Poser compatible assets.

Daywalker Designs

Also, DAZ Studio 4 and later cannot read Poser PMD files, so any Poser content that uses them wouldn't work in DS.

Richard Haseltine

DS has had problems with .pmd files for props and injected via poses, I believe it still works for figures. The problem was that every Poser service release seemed to change the syntax (which also broke backward compatibility in Poser).

pwiecek

Daywalker Designs said:

Also, DAZ Studio 4 and later cannot read Poser PMD files, so any Poser content that uses them wouldn't work in DS.

 

Richard Haseltine said:

DS has had problems with .pmd files for props and injected via poses, I believe it still works for figures. The problem was that every Poser service release seemed to change the syntax (which also broke backward compatibility in Poser).

If you're using poser also, load the model with PMD problems. Turm binary morphs off. Resave the files with a different name. Now thwy should be usable in poser

jan_8a6b444a69

Hello again,
i have done it. I first loaded my complete Product-Library from the Daz-Product-Servers via DIM in one Directory by setting it to "selected directory".
Than i had a big Daz-Library in that directory. And then i put my poser-stuff into the Runtime, which was automaticly created by the DIM for the Poser-Compatible files, i bought from daz.
It works great in Daz and Poser. If i buy new files, i tested it with some Freebees, it comes to the right place and works fine. When i download it with DIM.

Big thanks to Richard

Greets
Jan

Mattymanx

Padone said:

Personally I would not advise to mix Poser and DS both in the same folder. Their structures are similar and compatible, but different. I'd rather point Poser to DS and DS to Poser as Richard explained in his first post. This way things are cleaner in my opinion. Because you have a folder for Poser only, and a folder for DS also containing Poser compatible assets.

 

To each their own, but I have had mine combined for over 10 years.  Having them combined helps to eliminate duplicate textures that are shared between Poser and DS versions of the same product.  Also makes installing content easy, as one can mass select multiple zip files and target a single location without having to worry about what zip file is for poser and which file is for DS.

JQP

Mattymanx said:

Padone said:

Personally I would not advise to mix Poser and DS both in the same folder. Their structures are similar and compatible, but different. I'd rather point Poser to DS and DS to Poser as Richard explained in his first post. This way things are cleaner in my opinion. Because you have a folder for Poser only, and a folder for DS also containing Poser compatible assets.

 

To each their own, but I have had mine combined for over 10 years.  Having them combined helps to eliminate duplicate textures that are shared between Poser and DS versions of the same product.  Also makes installing content easy, as one can mass select multiple zip files and target a single location without having to worry about what zip file is for poser and which file is for DS.

I'd rather be dragged across a road full of broken glass than unzip product files directly into my content folder. I don't think I've done that since the Poser 5 days, when I started with 3d. I always extract to a temporary folder first, and inspect the contents and how they're organized (which is frequently poorly, or in an obsolete way).

I don't even like batch-extracting multiple products to a temp folder. Far too often the products' folders get mixed up and I have no idea what belongs to what.

My beef with DS library is the "oh, this side can't see Poser content, only DS content, and oh, that side can't see DS content, only Poser content." There may have been a good reason to do it this way, but I sure as hell can't think of what it could be. Seems like a horrible idea; it's one of the main reasons I'm still using creaky old Advanced Library for Poser, instead of the DS library, 99.9% of the time.

Richard Haseltine

JQP said:

Mattymanx said:

Padone said:

Personally I would not advise to mix Poser and DS both in the same folder. Their structures are similar and compatible, but different. I'd rather point Poser to DS and DS to Poser as Richard explained in his first post. This way things are cleaner in my opinion. Because you have a folder for Poser only, and a folder for DS also containing Poser compatible assets.

 

To each their own, but I have had mine combined for over 10 years.  Having them combined helps to eliminate duplicate textures that are shared between Poser and DS versions of the same product.  Also makes installing content easy, as one can mass select multiple zip files and target a single location without having to worry about what zip file is for poser and which file is for DS.

I'd rather be dragged across a road full of broken glass than unzip product files directly into my content folder. I don't think I've done that since the Poser 5 days, when I started with 3d. I always extract to a temporary folder first, and inspect the contents and how they're organized (which is frequently poorly, or in an obsolete way).

I don't even like batch-extracting multiple products to a temp folder. Far too often the products' folders get mixed up and I have no idea what belongs to what.

My beef with DS library is the "oh, this side can't see Poser content, only DS content, and oh, that side can't see DS content, only Poser content." There may have been a good reason to do it this way, but I sure as hell can't think of what it could be. Seems like a horrible idea; it's one of the main reasons I'm still using creaky old Advanced Library for Poser, instead of the DS library, 99.9% of the time.

The Poser content, like the fiels in Othre Import Fomrats, is Imported rather than being opened - if you save it the result is a modified version, not the original. That - and the other ways in which import is different from iopen - is why imported content is kept separate from native (Daz Studio Formats) content, with poser content being separated again as it requires a particular directory structure that genral geometry imports and native DS fiels don't.

Mattymanx

JQP said:

Mattymanx said:

Padone said:

Personally I would not advise to mix Poser and DS both in the same folder. Their structures are similar and compatible, but different. I'd rather point Poser to DS and DS to Poser as Richard explained in his first post. This way things are cleaner in my opinion. Because you have a folder for Poser only, and a folder for DS also containing Poser compatible assets.

 

To each their own, but I have had mine combined for over 10 years.  Having them combined helps to eliminate duplicate textures that are shared between Poser and DS versions of the same product.  Also makes installing content easy, as one can mass select multiple zip files and target a single location without having to worry about what zip file is for poser and which file is for DS.

I'd rather be dragged across a road full of broken glass than unzip product files directly into my content folder. I don't think I've done that since the Poser 5 days, when I started with 3d. I always extract to a temporary folder first, and inspect the contents and how they're organized (which is frequently poorly, or in an obsolete way).

I don't even like batch-extracting multiple products to a temp folder. Far too often the products' folders get mixed up and I have no idea what belongs to what.

My beef with DS library is the "oh, this side can't see Poser content, only DS content, and oh, that side can't see DS content, only Poser content." There may have been a good reason to do it this way, but I sure as hell can't think of what it could be. Seems like a horrible idea; it's one of the main reasons I'm still using creaky old Advanced Library for Poser, instead of the DS library, 99.9% of the time.

 

One bit of information I left out is that I custom organize my content first.  In Windows (XP to 10), using 7zip, I can extract every Daz product zip file to its own folder (named after the product zip file), individually or as a mass operation.  Then I go into each folder and custom organize each, sometimes combining morph packs and clothing with thier related texture addons.  I also delete the mata data.  Personal preference as I dont use smart content, just the standard folder view.  After the oranization is complete, the folders within the content folder are compressed using 7zip to a new 7z file.  This is then named accordingly and then I tell 7zip to extract the contents of that new file into my content directory.  Having custom organized content in this fashion allows me to mass install content in the future if needed.  This is something I started doing back in 2005 when Aiko 3 was my main figure of choice and the only content we had available was in Poser format.  When Daz Studio specific content started to come out, I simply learned how to combine the two.  Its rather simple to be honest.

 

I can understand the need to have the DS content library seperate DS content from Poser content, as poser content needs to be in a specific folder layout as it was defined by the program years ago.  Whereas user facing files for DS content is not restricted in its layout but extremely customizable.

JQP

I don't care that poser and ds files are STORED in different places. That's to be expected, due to the legacy of poser's horrible library structure decisions back in the day. What I don't understand is why DS won't just display it all in the same way; I should be able to display my poser stuff with the same library window that I display Daz content with. Instead I'm treated to an "empty" window because the DS content library doesn't display poser file types. I have to navigate to the "poser content" tree to see poser content.

This has recently become a huge PITA for me again because Advanced Library has suddenly stopped working for no apparent reason, and nothing I do will make it run again.

For the hundredth time I wish Daz would implement Advanced Library's functionality; let user set up "virtual folders" that we can assign the contents of real folders (and their subfolders) to. That way I can sort my content however I like without touching a hair on my content folder's head.

 

Richard Haseltine

How would you want them integrated - most of the ways i can think of doing it, based on file-location, would be just as clunky - and if you try doing some kind of group by function you are into a metadata-based approach, which we already have in Categories.

JQP

I found a way to get virtual folders working in DS, thought it was worth its own thread:

https://www.daz3d.com/forums/discussion/268381/symbolic-links-double-commander-and-daz-studio