Amazingly, not only do they work, BUT despite the fact that I’ve not yet added ANY Poser companion files for any other Genesis products, such as the gorilla, M5, Gen3 and 4 shapes, all of those show up and work under the parameters dials!!!
Now, I DO have all these items in my DS folder (and I have things set up so that my main Runtime folder-which I use for DS & Poser-is at the same level as my data and people etc folders, so maybe that’s why?)
I was surprised to see that I didn’t have to install anything else in order to use all these in Poser.
No, there are no companion files for things like Genesis morph packs like M5, genesis Evolution morphs, gorilla etc. They just work.
As to why they work ...
In DS, with Genesis (and completely unlike V4, V3 etc which were supplied as Poser format files and used a completely different system), when you install morphs, each morph is just a .dsf file that goes into subfolders in the Genesis subfolder in the data folder (which should NOT be mucked around with until/unless you really fully understand the system).
When you load Genesis in DS, DS is directed to look in the Genesis sub-directory in the data folder and it simply scans every .dsf file in the morphs subfolder and reads in all the morphs. (It does the same thing to the UV sub-folder and so Genesis loads up ready with all UV sets you have available.) So, once you’ve installed morph packs, next load of Genesis in DS it just appears with all morphs you have there in it. (There’s no re-initialising the figure like with V4 after adding new morphs, or injecting morphs after loading the figure like in V4 and V3>
Now, when you use Poser and go to load Genesis, you click on a cr2 file which actually just contains one line calling which calls a python script, which in turn calls the DSON importer plugin (that cr2 file and the python script being two of the companion files), and the importer plugin does EXACTLY the same thing DS does ... it’s pointed to the Genesis sub-directory in teh data folder, and scans all the .dsf files it finds in the morphs sub-folder, and starts the Genesis up with all the morphs you have in it.
So for morphs (and alternate UV map sets), installing for DS is also installing for Poser. No extra files are needed in Poser for the morphs. When either DS or the Poser importer plugin go to load Genesis they simply scan the (same) data folder for all morphs (and UV sets) that are in there, and whatever morphs load up in DS will also load up in Poser.
So, to someone from corporate or someone who does use Metadata, what exactly is the purpose of the 3 metadata related Poser Companion files that go into the Support folder? What does the metadata do? I already HAVE James for M5 in my smart content folder from the initial installation of the product….
presuming you mean the dsx files that go into runtime/support ...
They contain, in a DS format used by the DS content database, the information on the products for the database. For each one, it contains things like what kind of product it is (poses, materials, figure, prop), more detail on the kind of thing (like it’s a figure - clothing - a skirt), and what things it works with (like it’s a material preset for particular skirt X). (I’m not looking up the actual categories so those are just ‘that kind of thing’ examples, not actual categories). and it also contains the path to where the figure or preset or whatever is.
All for use in the DS content database when using categories or the Smart content pane.
So. for anyone who is using Poser only - ignore.
For anyone using DS who doesn’t use the Smart Content pane or the category or product entries in the content library tab - i.e. just uses the file views in the content library pane and doesn’t use the content database that powers the Smart content and category views (like me) - ignore.
If you are someone who is intending to use Genesis in DS and Poser, for when you are using it in Poser, ignore because Poser does not use DS metadata (although it can use its own kind).
It only matters if:
(a) you are using DS, with the content database running, and
(b) are using the smart content tab or the category or product views in the content library tab.
Now, if both apply above, you will previosuly have installed Genesis in DS, and loaded it from the Genesis file that was installed to My Library/People/Genesis. The dsx file that was put into the My Library/runtime/support when you installed Genesis had all the metadata for the DS content database as described above, including the location of it being in people/Genesis. If you, moved the Genesis file to another folder, then the content database will have lost track of it until/unless you edit the .dsx file, or use the content database tools to tell it where the files gone to from inside DS.
The new extra stuff for Poser makes no difference to this.
However, if you’ve installed the Poser companion files, it will be into a runtime you have mapped into DS, so in DS, in the content library, there are now two different files that will launch Genesis in different places. assuming you haven’t moved them, in the content library pane you can, as before, go to the DS Fornats section, then down to People>Genesis where there is the pre-exisitng genesis.duf and launch Genesis. but you cna also go to the Poser Formats part of the content library pane, open the runtime you installed the Poser companion files to (likely My Library again) and go to Figures>DAZ People and find the Genesis.cr2 you would use in Poser. If you click on that. again genesis will launch.
The extra .dsx file installed into runtime/support for the companion files goes with THAT genesis.cr2. Most of it is exactl the same info as the other .dsx file. It’s all about the same Genesis figure, so all the categoriesin the meta data are the same. But this one has the path to the GEnesis.cr2 in the content.
So now the content database in DS, when you are using DS, knows you have TWO different Genesis loaders you cna use, one in the DS Fornats section, one in the Poser Formats section and where they are. Just as for the one in the DAZ formats section as described above, if you move the Genesis.cr2 (and the other three files with it) from, say, characters/DAZ people into characters/People/DAZ people, then the content database will have lost track of where the Genesis.cr2 is for using THAT, rather than the normal DAZ genesis file to load Genesis. and again to get the content database to know where the file has gone you can edit the .dsx file, but more easily just use the tolls in the content database to tell it where you moved the file to.
First, remember this makes no difference at all to your use of the Genesis.cr2 in Poser. as far as Poser is concerned, as long as you keep the cr2, py, png and duf together, doesn’t matter where in the character library you put them.
For your use in DS, it will only matter IF ypou intend to launch Genesis by using the genesis.cr2 in the Poser Format section rather than the Genesis.duf in the DAZ format section of the content library as previously.
If - in DS - you are going to carry on loading genesis from the DAZ format part fo the libary as you have done previously, then (if you use the content database in DS as described above) it only matters that you correct the content database after you ,move the Genesis.duf from the My Library/People/Genesis location. It doesn’t matter if you move the Genesis.cr2 (plus the other three files) around in the runtime character folder and DON’T tell the content database if you are never actually going to use the Genesis.cr2 in the Poser format section of the content library to load Genesis in DS (and in Poser it doesn’t matter).
Hope that makes some sense. I know what I’m trying to say, but permanent pain and permanent prescription painkiller haze rather interfere between deep-brain knowledge and expression through keyboard. To think I used to be a teacher renowned for being able to explain complicated things simply before becoming disabled.
Anyway, off to bed now ...