this is weird, i just did this a few weeks ago, but what happens now is if i add a second figure its mangled, even when i select body on the null and do it right. the only exception is if i use 2 base vicki 2's, in other words no vicki cr2 that i have modified will work anymore, which REALLY sucks as i have very little use for the waif and weird base vicki model. i checked the readme and made sure instances are 1 for all the cr2 figure's parts; but no matter what i do ANY cr2 that has been changed or had props added or anything cannot abide the presence of a second vicki character. I sure wish CL would patch this, its insane that you cant simply use multiple figures. any help would be really appreciated ive tried every possible combination here lol thanks!

I'm afraid I don't have the millenium figures. So I have to rely on the info I see passed around to use as a guide for troubleshooting. Have you tried using a new copy of the null figure? Maybe something got added or deleted from it? Afraid I'm not much help with those figures. I don't own them. ScottA

well i think i found a work around... it seems that if you import 2 figures of any kind, even if you use the normal vicki, you can use her as a place holder, and the third, fourth, fifth, etc can be anybody... then i can just delete the first two figures. i think its an error that occurs because the null doesn't know what to rename the new figures, unless you use an unmodified vicki.

Brian,
When you save Vic back to the library, Poser doesn't necessarily write figure names and instance numbers as 1. There are a number of factors that have an effect on what gets written. The null needs "Figure 1" and ":1" in the loading cr2 to work as intended. The two+ like (same naming conventions for groups) figure method has a major downfall, and that is, system resources, which is the point of the null. The null accomplishes the same thing, in one figure, with very little overhead. Also, the null doesn't name anything except itself. It is poser who assigns names/instances. The null just occupies "Figure 1" instance ":1" so Poser will assign the next sequential number to the loading figure.

-Rob
rbtwhiz.com

actually it doesn't seem to quite work like that, because one figure that wont work i checked the cr2, it was named figure 1, and all instances in the cr2 were :1 but when i added that figure as a second figure, or used it first and just brought in a second copy of itself, or any other figure for that matter, it was mangled. i have a hefty system so i dont mind importing a couple figures extra then deleting one or two. actually yesterday it seemed to work fine with only one extra figure; as long as the first one was hunky dory the second, third, and so on would work fine. not sure why one of the figures with the correct cr2 setup worked and one didn't, but for now i have a good workaround. thanks :)

Actually, the null does work as I've said. When loaded first, it occupies Figure 1 (although it is named "Millennium Null") and instance :1. Upon loading the second figure, Poser sees that 1 is taken and inserts 2 in it's place. And so on with 3,4,5,etc...

When you saved these modified figures back to your library, did you start making the mods with a clean slate? (ie: File -> New) If not, this will often cause the number poser uses when saved, to climb.

When you say that the cr2 was checked and that both, the figure and instances, were/are 1, are you also saying you checked the ERC code in the various groups to ensure the same? In Vic2, there are a plethora of places that must be "fixed" in the event that the saved cr2 had anything other than 1. The only way to catch them all (without driving yourself mad) is to do a global replace of ":#" to ":1", the same applies to "Figure #".

If you'd like, (provided it is V2 based) I can call DAZ and request that approval be given for you to send the cr2 to me. Or perhaps send it to them [DAZ] and I'll get it that way, to take a close look at it and find a solution. Up to you...

-Rob
rbtwhiz.com

hmm, i will try to do the global replace, it's not that big a deal since i can still get to where i need to go; but the odd thing is some of the figures when saved to the library under a name, like "demon" for example, actually DO work with the null... seems weird since they aren't all named figure 1, and the ones that are don't always work hehe. In general i always seem to be able to get the null to work for me in the end though; i really appreciate the help :)

"Figure 1" isn't a necessity; because of what is going on behind the scenes. One of the reasons I make a point to include "Figure 1" in my write up is, it helps keep confusion to a minimum, simply because it keeps all instance names and figure names in sync. I also make mention of it for the sake of future compatibility. There is no doubt crosstalk needs to be fixed in the next version. With that in mind, who's knows how Curious is going to do it (I don't think they even know how they'll address it at this point). With "Figure 1" being the default in both ver3 and ver4 (I'd have to re-install ver2 to tell you if its the same there), chances are it'll be the same in ver5. So, playing it a little safe now may save you (the collective "you", not you specifically) from having to re-build/edit the files again later. Believe it or not, there is method to my madness and reason to my rhyme :).

-Rob
rbtwhiz.com

Seems like Curious must be dealing with a huge conflict this time between unleashing the features we want and they need to remain competitive and expand their market, and maintaining backward compatibility with all the stuff that's been developed in the unusually long stretch since the last upgrade. At least with P4 stuff. Folks will be mad if they don't push the envelope to the max, but upset if they can't get optimum results from time and money they've invested. If they had unlimited resources, they could do a "classic mode" like Mac OSX. Of course, I have both a copy of the patched Poser and Poser with ProPack on my Mac already. Let's hope that's an option with P5 without a copyright checking mess, if it proves necessary. Thank goodness big hard drives don't cost thousands anymore.