Ever since she came out people have been saying how much more of a drag on their system V3 is compared to V2. I don't understand this at all, I must be missing something. My experience has been the opposite. In the above pic, I put one Vicky2 in an empty scene and saved it, please see the results below the left image. Then I put THREE Vicky3's in an empty scene and saved it. Note: it is the same cr2 with the same morphs injected; enough morphs to make her look like different characters and give her a wide range of expressions. Then I put three V2's in an empty scene and saved it. You can see the results below each image. (I'm betting there will be similar results between M2 and M3.) So what am I missing? Why do people keep saying they're sticking with V2 because V3 is such a system hog?

Probably because the injection system is not what they are used to. It takes some time to browse through the libraries to find the good morph injection, and it takes some experience to figure which morphs you'll use, more than is needed for just toggling the dials. BTW : the main issue I have with buying V3 is that I spent quite some money on accessories and characters for V2 and I don't see the point in spending a lot more for V3 (V3+morph packs+textures/universal texture converter, new clothes, etc...) since I don't do close-up portraits nor am I a professional artist (and I have yet to see a non-portrait V3 image that could not be done with V2 and some postwork). When I see a V3 outfit that I like, I grab/buy it and convert it for V2. Back to the topic : the morph injection system is quite interesting (I have microcosm based on this), but it may be more easy to handle in Poser5 or with PBoost since they both offer an easier library management.

You can make V3 pretty lean by loading only the injections you want to use. If you select all available injections on V3, she can go well beyond 100 Mb. With V2 all "injections" are fixed in the cr, so you can't "remove" them without having to go the cr2 and do it manually.

I don't even bother to work out which morphs I will need on V3. Life is too short, so I inject the whole lot every time. :)

I'd say the opposite, life is too short for sorting through all those dials, I only inject what I expect I'll need. Actually, with Glamorous Vickie or Ingenue Vickie I hardly need any addittional body morphs anyway! ;-)

I'm with Jim on that. Have you counted the morhps available? Oh wait, life is too short to count them. ;D

Thing is, I never know what I'm going to want from a character when I make a render, so I would rather have all the morphs available than have to keep switching banks, selecting the appropriate morphs and so on. I keep a fully loaded V3 in my Characters folder, and the strange thing is, the whole assembly seems to load quicker than an empty V3, then the head morphs, then the body morphs.

SamTherapy, so do I :o) I have a V3 named V3AllMorphs in my character folder. And when I say All morphs, I MEAN ALL morphs. I like to make characters, but like you I never know in advance WHAT character I'm about to make. Actually it's like my characters take a life of their own once they're released into Poser. THEY decide how they want to lok :o)

I've got a fully loaded V3 also, everytime I get some new morphs I add it and resave. Also have it with all White color and neutral highlights w/ lash & brow trans set, ready and waiting to go.

yours are all naked.....try putting some clothes on V3 and where I have the problem most of the time of it freezing up when I render is when V3 has hair...I can render a naked V3 just fine all the time....but I don't do nudes....it's when I add hair and clothes that she bogs down my system...

INJections also don't work very well in my experience in Poser 5 (they are at least INCREDIBLY slow) unless you ignore the Poser 5 library improvements and place the character in the "root" runtime folder. So if you want to use her in P4 and P5 you get real slow performance, have to have 2 copies installed (and patched, and patched again, and...) or save fully INJected copy, which is a RAM hog. IMHO.

Mine are all naked? Really? I don't think so. Last time I looked, over 90% of my renders were not nudes.

ahhh, why do you think I was talking to you? I was replying to the original post....

Hehe, my mistake.

I've been using a Vicky 2 character for online comics for the last 2 years. The character fully dressed is 17.7mb as I've created a unique body morph for her and only keep in necessary morphs for expressions and body movements in action scenes. I created a Vicky 3 version of the same character, created a unique body morph for her as well and removed all unnecessary body morphs as I had with Vicky 2. The character is 42.4mb in size. I can bring in 8 versions of the V2 character and have it render. I can bring in 2 versions of the V3 character and have it render. That makes V3 useless to me. Guess I'm waiting for Pentium 5 with 10GB RAM for less than $2000 before I can make the switch.

Yep, I have everything injected too - except maybe ears or something. I want to have everything at my disposal when I create something. Just like I always have for Vicki2. With her I have nearly 1400 MTs loaded.... and she's still less of a hog than ordinary V3 injected. The only true advantage I have yet seen with V3 is her better joints - hip, shoulder and so on. :] Fish

Who3d: I'm a Poser 4 user, but I'm pretty sure I remember Traveler (in reference to the MicroCosm injectors) saying that only the deltas (the !DAZ folder for V3) need to go in the base Runtime under P5, the actual add/remove poses can be put in any Pose library folder.

hmm... cheers, might have to try that - even if only to find out if it make smuch of an improvement. V3 has lain largely unused becaus eshe just doesn't work well enough for me "out of the box", as it were.

Dizzie: I believe adding hair and/or clothing to any figure bogs things down the same amount, that's why I didn't bother with them in this comparison. who3d: RHaseltine is correct about the folders. In fact, if you use P5 exclusively, you can even put the folders inside other folders. As an example, you could have all the INJ poses in "V3 INJ" and the REM poses in "V3 REM." Like Jim and JV, I find scrolling through V2's morph dials much more of a pain than finding the morphs I need and injecting them. You only do that once, with v2 you're constantly scrolling through those dials. Anyway, I think I found my answer: V3 is a system hog because users make her that way. To each her/his own, I guess. Maybe someday I'll actually need that "toes curl" morph or the "ear fin" one ;) Thanks all.

We've been able (morph manager?) to strip out morphs (e.g. to make a lighter V2) for a while too - one could say that V2 is "heavy" only because we don't (tend to) optimise each character :( Persoinally I like a lot of the P5 improvements - including the ability to organise morphs (installed, available) into categories.

WAIT... Nobody has addressed what was in the first post. Why do 3 Vicky3 figures take only 1 Vicky3 worth of bytes in a pz3 whereas 3 Vicky2 figures take 3 times as many bytes as 1 Vicky2? Is there something fishy here? I don't understand.

Spit, it's because I only injected the morphs into V3 that I needed. Enough to give her a variety of shapes, faces, and expressions. Her cr2 file is only 7.1 megs. That's true Who, about Morph Manager. But it's a separate program and you have to save another cr2 with the morphs stripped. With v3 you add and remove morphs on the fly right in Poser with the same cr2 you started with.

And the size of the PZ3 is misleading as the OBJ and textures are still external references, which will matter when you load the file into memory.

Just a note on dial scrolling : Poser 5 can make groups of dials that you can expand or collapse, which has changed my life ! (unfortunately, you cannot delete all the dials belonging to a group at once...)

But...uhm...does Poser uses the actual mesh in visualizing and rendering rather than count all the morph points in the CR2? I mean: all the morphs, until used by moving their dials, are nothing for Poser, as it uses only the mesh for the visualizations in the viewports or the rendering. V2 has a less defined mesh against V3, and THIS is what hogs down some machines, not the CR2 size or the number of morphs loaded, at least if you have 512+ Mb memory (a standard today). Oh well, if you have Poser on a 128 Mb machine, you can bet that even Posette hogs it down ;-)

I used to use Posette on a 96MB Pentium (233MHz) and don't recall it feeling "hogged down" at the time. Mind you, I also did my lip-synching in Microsoft Excel back then so...

I used V1/2 (and occasionally Dina) on a PII 400...so what? :-))) I was only kidding :-)