Quote - Getting way OT, but.... Here's what I REALLY wish content creators (and I'm thinking of hair, character and clothing creators, in particular) would do: Organize their files so that it was obvious what figure their set was for. In the case of expansions to something existing, nesting the folders for their product inside of the folder for the orginal product.

Here's an example.

Artist 1 creates hairstyle X.

Artist 2 creates an expansion pack for hairstyle X. What this usually means is that the expansion pack is God knows where - perhaps in a folder under Artist 2's name. Anyone with a decent sized runtime has a good chance of forgetting that there are extra textures/morphs/whatever for hairstyle X, because they're nowhere in the vicinity of hairstyle X in the runtime. Much better that when I go to /libraries/pose/Artist 1/hairstyle X, nested inside that I see a directory called Artist 2/hairstyleXpansion or whatever.

The future plans for Poser content and the next-gen library GUI will be taking care of that, along with a few other common problems. Where things are or what they are called will become totally irrelevant.

---

Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)