When it comes to Native Poser characters, one of the biggest downfalls is that they only usually work in the latest versions of Poser. That in itself limits who can use it right off the bat. Many of them focus on demonstraiting the newest things in Poser, so they are more geared towards showcasing what you can do over trying to be the next main character in use. Many of them wont work in other programs due to the rigging used as well.

Judy was probably the one that got the most support upon initial release. Ones after that have had issues that made it next to impossible to do much with them.

Sydney is so asymmetrical, that making morphs for the breasts is a challenge in itself. Mirroring weight maps on the wireframe is next to impossible, and using symmetry and copy joints destroys the weight maps. I think her head has more vertices than the rest of her body does. No idea why the inside of her mouth is so detailed....

I have some extensively modified versions of a lot of the Poser characters, including Sydney. But releasing them would not make them popular without an entire library of things to go with it. I know how to use just about anything in my Runtimes with them but the average user may not know how, or want to invest the time to do that. A lot of it can not be done easily from within the Poser itself.

I have played around with code to do so outside of Poser, and you can do a lot to any character that way, including getting it back into Poser. But they way I have been doing it wont work on a Mac or a computer without a Directx11 video card unless you want to wait ages for it to be done on the CPU. When my new workstation is done, there is presently only one GPU that will do what I have in mind to process things. The method I am using is based on a point cloud reconstruction routine and needless to say there is a lot of coding involved, and even more number crunching in the background.

Like I said before, what we really need is a way to use the best of everything, in one character no matter which one you choose to load first. It is a tall order to code something like that, and to date no one has come up with a reliable way of doing so.

Not even me.... I can get BSOD just as well as any other programmer. The other day I forgot to release an a rather complex looping object in the code I tried, and it was still running after I exited the program.... Needless to say, Windows ran out of memory in a freaking hurry.... Opps.... Crash....

---

Some things are easy to explain, other things are not........ <- Store ->   <-Freebies->