I purchased V3 this summer and found I couldn't use her with either V2 or M2 because of "crosstalk" (or so i understand the problem is called.) Needless to say this was pretty annoying and I went back to using V2 pretty quickly. Now I'm wondering if M3 will mix with V3 without any annoying problems. Anyone know? I asked Daz, but they haven't responded yet.

Use an ERC remover. Nerd has one on his site. You can find it by searching the freestuff here.

In Poser 4, there are several work arounds, the Null figure being one of them. In Poser 5,There is no morph to morph cross-talk, but the readScript function happens at a vulnerable level. You need to prepare each character -solo- save it as an "injected" cr2. Then in the render scene, bring in the pre-prepared characters. I would bet that readScript would cause problems with multiple figures in P4 also. I don't know if the Null will fix this. The code in Poser 4 or 5 was not written to accomodate the more sophisticated ERC functions that we are doing now. Because of this, scenes must be planned. Doing multiple characters can cause problems if not done correctly. Poser has a function - that in P5 takes care of these problems - it is: Spawn Morph Target. If you make a character be a single unique new morph (a morph for every group, that is) and this morph has its own name, you can use it with V1 or V3 (depending on which one you are using) and not have any other shape morphs in there. Poser 4 also has this function. The difference is: The JCM will still be open to cross-talk and this must be planned for. But Poser 4 will allow JCM in conformed clothing to be automatic because there is cross-talk. This is what we have to live with - with Poser code, it is not anything DAZ can do anything about.

Thanks Jaager, that may be the answer to my question down below. Scarab

Scarab, it is why you are having problems. A second injection figure -V3 or M3 - will not function properly. This was noted fairly early with V3 and DAZ has directions on their site about it. Rob talked about here early on. It is not as likely that two V3 figures will be used in a scene as it is that a V3 and a M3 will be used, so the problem has been not their problem by many up to now. It is like watching a train wreck = those who say they use a V3 figure with all morphs injected. While the body is not much different from V2 in size. The head is a whole 'nother universe. V3 with just the expression morphs - morphs that you need for every character - is 20,000,000 V2 with all stock DAZ morphs is 22,000,000 and V2 is a stress on many systems V3 with expressions and all body morphs - is 44,000,000 V3 with every morph - is 121,000,000 You can use a spawned charater (one morph/group) and set an expression, remove all morphs, save the charater, use IPB on it to get an injection pose for the expression, open the character again, inject just the expression morphs needed for the render and have a figure that is 6-8,000,000 - which is about as lean as you can get V3 (or M3). If your system is groaning, draging, nor freezing during a render - or you just want it to run as fast as possible, these steps many be worth the effort.

Hey....I injected everything and saved the .cr2....solved all my problems... I won't say you're a genius (you may be...) but you is a handy fellow to have around... I would have figured it out myself.....in a few months.. Thanks...I owes ya a few months.... Scarab

Attached Link: http://www.renderosity.com/messages.ez?ForumID=12356&Form.ShowMessage=1431670

Hi all, How about my solution? Thanks, Mav :)

Jaager, "I would bet that readScript would cause problems with multiple figures in P4 also. I don't know if the Null will fix this." No Jaager, your guess is right, it doesn't - unfortunately. The readscript() process can load the actual morphs in to the correct figure if you handle the Nulls very very carefully, but readscript() appears to place all the ERC/FBM stuff into the first figure loaded in the scene, regardless of which figure you have as current the figure. So the Null can't save you in P4 unless it's the first figure in the scene - which doesn't need the Null either. This seems to be the primary reason why a figure has to be the first loaded in a scene if you want to use readscript() injection. I would guess this state originates from readscript() being incorporated into Poser a release before the FBM stuff was, and never being brought up-to-date with the newer methods.

Thanks for confirming my suspicion. I would be willing to guess that readScript was in Poser 3 - the same guy was the default opener. Which would mean that it does pre-date ERC. ERC happens outside of much a buffer - the controlling figure is wild wild west sort of assignment - so readScript must really be dancing on the top of the berm. It would not surprise me if some more gottachas show up as hard as this is going to be pushed. The sophistication of these functions - inside this rickety structure - has already taken things beyond the fire and forget level. Maintance is required, and there is much resistance to that.