Thanks, I made some progress, I'm able to load the morph now, but the fitting room seem to be changing the vertex order or something, because the morph gets distorted.

Is that documented? I don't have Poser at hand to check.

And which features get shared? everything? lights, figures and all?

Glad you figured it out. You should report it as a bug because to me it seems Poser is looking in the whole runtime first for the PDM file before looking inside the folder of the figure you just loaded, since it's finding a Ryan PDM file somewhere else, it takes that one.

Copy joints is not as bad for me as it is for Zanzo aparenly, I use it all the time without problem.

But I think the question is how deep inside? I think modeling and texturing the insole would be overkill since it's a high cut boot, shadows won't let you see that far inside anyway.

Generally I don't care much about the inside of shoes, like you said, a few inches in should be enough. I do apreciate when there are some material zones though, setting material zones for the tip of the shoes gives me the abitlity to turn normal boots into an open-toe model by setting said material transparent, for example. For the model in the picture, I could use the upper part of the shoe (where the laces go) as some ankle-garment of sorts by hiding the rest of the shoe. Can't tell you how many people use material zones for this kind of things though, but it can give you a lot of variations.

I didn't read the whole thread, but just wanted to add my 2 cents.

Genesis expands the ability of morphing and mix matching characters beyond any other figure, but if Victoria 4 works for you right now, and there isn't a point for you in which you say "I REALLY can't do this with Victoria 4" (like turning her into a Troll, along with her 6 years old child),  then I don't see there's a reason for switching to Genesis other than trying a new figure.

All that flexibility obviously comes at a cost, you have to buy every morph pack again, muscle morphs, detail moprhs, etc. Or buy tools that allow you to convert old stuff to Genesis.

To me, it all comes down to real "need". For example, I'm working on some sort of bestiary of fantasy creatures, and up until now, I had to create a creature twice, male and female, using V4 and M4 (M4 not being WM yet), now I have to create it only once and dial the female and male dials on Genesis up and down. It's a very particular need, but that's the point.

I used to be a die-hard linux user back in college, nowdays, I only use it when I have to, and mostly by terminal, still love it, but I'm not as up-to-date as I once was.

Last distro I tried for desktop use was openSuse. Recently I tried Ubuntu and didn't quite like the new look and interface.

The abs look odd, otherwise, great character.

Actually I used the Blakes 7 as a movie camera for a few renders too. Thank you for your freebies :)

http://www.targetmap.com/viewer.aspx?reportId=3073

...

I'm from one of those green zones ;)

As for the thread subject, I really don't mind, thankfuly we can dial spin those up and down as we see fit.

Aha! thank you guys, that's what I thought, being such a trivial issue I was certain there were libraries or classes ready to do the job.

Most apreciated.

Thank you.

I do know this has to be handled with a config file, what I'm wondering is if Poser has any undocumented features to do that, or if I have to do things manually.

The script is very very simple, adding a config handler class and parsing config files would require more effort than writing the script itself lol, but if there's no other way...

Same here, I certainly noticed that in many many packages, and it's anoying to say the least, it turns a one click solution to an edit-and-try situation.

If there are texture creators reading this, of character packages or merchant resources, please consider making sure the skin color is mostly even across the body.

Not an issue with SR3, I'm having this issue since Poser 7, it could be a problem with every other version of Poser too, idk.

Very anoying, but I've been wondering if that's the intended behavior, it's a bug, or we are just doing something wrong.