I forgot about the breast bones. Sometimes they are a nuisance on the male characters though and i have to adjust the bones back on some poses.

Also about the file structure in DS:

Yes, the structure takes some getting used to because you have to set up a character in two places: under the data folder which is where the actual definition of the morphs and clothing go, then specific places for where the user actually accesses:

People - this would be where you generally would find each figure and their respective characters, clothing, hair, materials, etc.

Props - this would be the props and sets for a scene (things get mixed up here)

Lights - This would be for ds-specific lights

Environments - these would be full sets for a scene (though props get mixed up here)

(The above items are generally define as user facing files, so you can generally move these anywhere you want, but unless you understand how things are set up you probably shouldn't. Anything in the data directory should NOT be moved... that's like trying to organize your geometry directory which is kind of a no-no since it would be like organizing your obj files where the cr2s and props can't find them)

Runtime - generally textures would fall under this directory though if you have any poser items, they would fall under this directory as well. This is generally why I would keep Genesis items in their separate runtime from other Poser items so you don't get the urge to start organizing things like you would regular poser runtimes because you'll quickly foul up your genesis set up. Because your DSON/Genesis items are sitting above the runtime structure, you can mess up your set up here as well, so it's good to just keep Genesis items separated from Poser items)

If you do organize the Poser companion files, all four files with the same name and different extensions have to move with it. (for example, a pz2 companion file would have a .duf, .py, and .png file that all need to be moved together with it. The pz2 would have a python call in it to the .py which calls into Poser's plugin architecture and the .duf is the actual file with the information. A companion file with the .mc6 extension may have Poser-specific shader information in it in addition to the calls mentioned previously)