Mixing runtimes?

EportsBlade

Hi guys,

This may have being asked before. If it has, direct me in the right direction.

The questions? I have up til this time, being using Poser for my work. But now I would like to start using both programs, Studio and Poser. But I don't want to have too install to two runtimes. Can the studio and poser runtimes be combined? Can I put them into categories? What I mean by categories, is, shoes runtime, characters runtime, clothing, sci-fi, etc. And can this all be put on one hard-drive, separate from the programs themselves? Also can I find an example of the file structure for Studio's runtimes and their basic set up?

Note: I'm proficient with Poser's runtimes. My main interest is the Studio runtimes and any conflict that could come from the above lack of knowledge.

Any help would be good, I'm sure I can sort this out on my own, but little know how can go a long way before I start experimenting.

Thanks

Jaderail

DAZ Studio Runtime is 100% a Poser runtime structure. Nothing different at all. As long as all the Runtimes are pointed to in the Paths in DAZ Studio your method will work. BUT the Smart Content and Search function in DS might not. The Old Content Library Tab view will work as normal.

The DAZ Studio only content can go into its own folder. And then all should work fine.

Lissa_xyz

See my attachments. One is my libraries, the other is how they're added to Daz Studio. Not all are added, for instance I only use Apollo inside Poser, and the Bryce library is, well, for Bryce and is symlinked in the Bryce folder. You'll also notice that not all Poser folders are added to the Daz Studio Format section of the library manager- those libraries have no DS content in them at all.

Jaderail said:

DAZ Studio Runtime is 100% a Poser runtime structure. Nothing different at all.

Unless I'm just interpreting what you're saying wrong, that's completely false. The ONLY part of a Daz Studio library structure that is the same as a Poser runtime is what's actually in the \Runtime folder. Outside of it is a whole different animal.

Jaderail

Which is what I meant. The Runtime FOLDER in a DS content folder is 100% poser format. That was all.
Notice I did SAY the DS content Needed to go into a DS folder.

You can MOVE the Runtime folder Out of the DS content folder and as Long as its listed as a Poser Format Path it will still work.

Lissa_xyz

Jaderail said:

You can MOVE the Runtime folder Out of the DS content folder and as Long as its listed as a Poser Format Path it will still work.

Unless you have DSON Importer PoserCF. I think those need to be in the same library as the DS equivalents.

Jaderail

I was not addressing beyond standard loading of items, such as DS content used only in DS and Poser content used in both DS and Poser. Nothing more. To use DSON you must jump through hoops just as the DSON and PoserCF setup says in the Knowledge Base.

Richard Haseltine

Vaskania said:

Jaderail said:

You can MOVE the Runtime folder Out of the DS content folder and as Long as its listed as a Poser Format Path it will still work.

Unless you have DSON Importer PoserCF. I think those need to be in the same library as the DS equivalents.

As long as both paths are available to Poser they should work separated, but having them in the same folder is certainly safer and may be faster.

JonnyRay

Another thing to keep in mind when working with a LOT of content library / runtime folders is that there can be some cases where if DAZ Studio doesn't find a file, it will search the FIRST library of that type only.

This comes into play where maybe you have a material setting saved as a pose (pz2) file which refers to a texture, but the texture file isn't in the path that the pz2 refers to. DS will try to find the file for you, but it's only going to look at the first library in each list.

The practical impact is that if it can't find the file on its own, you'll have to find it yourself.

Admittedly, this is a somewhat rare occurrence, but it is something that I've had happen to me (especially with older content that may be using absolute paths to things).

mjc1016

JonnyRay said:

Another thing to keep in mind when working with a LOT of content library / runtime folders is that there can be some cases where if DAZ Studio doesn't find a file, it will search the FIRST library of that type only.

This comes into play where maybe you have a material setting saved as a pose (pz2) file which refers to a texture, but the texture file isn't in the path that the pz2 refers to. DS will try to find the file for you, but it's only going to look at the first library in each list.

The practical impact is that if it can't find the file on its own, you'll have to find it yourself.

Admittedly, this is a somewhat rare occurrence, but it is something that I've had happen to me (especially with older content that may be using absolute paths to things).

And 'nested' folders will cause the 'search' to stop dead in its tracks. Basically, if you have a Runtime > Runtime, only the 'top' runtime will be searched.

Another rarity, as in you need a case sensitive file system for this to matter...but Textures and textures, on a file system/OS that is aware of case will cause problems.

EportsBlade

Hi guys,

Sorry for taking so long to respond.

All of your info has being helpful and informative. I can see where this will be taking me. My plans are to redo my runtime files. Make them more ordered and get rid of the years of junk/unused and sitting there doing nothing stuff. Yup! I can see lots of work ahead of me.

But all in all, I'm happy to know I can combine the runtimes without too much trouble. The DSON importer is not a problem, just wished it worked faster for me, but that in its self is another story.

Thanks guys.