I still use P4 Pro. Majority of the charcters I've assembled are save as Pz3 files that I open individually. Now if I import one Pz3 into another I'm sure I will get the Crosstalk problem with morphs. If I save characters as Cr2 and load the Null Loader prior to the second assembled charcter. I shouldn't get any errors, right? Does cross talk affect only the same MIKEs or can I can have different mikes in same scene (Mega Mike, M2, M1) and have no crosstalk problem?

IIRC, cross talk affects anything with full body morphs where they share the same internal name. If you have a "muscular" morph for Stephanie, Mike 1, or Beefybullwinkle, and they all share the same internal names, then the fbms would talk to each other. Poser 5 eliminates cross talk. The advantage is that you don't have to deal with loading null figures before each character comes into a scene. The disadvantage is that DAZ has made use of cross talk to get all the clothes to fit on the morph injected figures of Vicky 3 and most likely Michael 3. Carolly

Yes... I wish P5 had a switch - crosstalk on/off. That would be so cool! :] Fish

? Can you put it all together in P4, for the crosstalk. Save it as a figure, then import it into P5? Or does P5 correct it still.

Actually, I have been able to trigger the cross-talk in P5, not on purpose, not reliably, and not in a useful way. It does happen, though. Occasionally, if I load the clothing first, then load the figure, then conform the clothes to the figure, the clothing will end up with the same morph settings as the figure even if I don't want them to. The clothing shows the morphs at 0, but they're obviously set to the same values as the figure they're conformed to. Weird, huh?

Load the clothing first? blink That might be something to try deliberately. Did you have a figure, then load the clothing, and then delete the figure and replace it with another? Carolly

No. I was testing some clothing textures and played with the clothing for a bit then loaded the figure to test stretching with morphs. I morphed the figure and the clothes were morphed as well. (And sometimes I'm senile and toss the clothes in first because I know what I'm looking for and realize, "Oh, yeah, I should have someone actual wear it!") I can't get it to work every time. I don't know if I accidentally trigger something, if it's certain clothing, etc. It always happens when I'm in the middle of something else and I don't think to write down which outfits and which figures. I think the V3 Morphing Fantasy Dress is one I've had this happen with.

Actually, there are still traces of cross talk left in Poser 5... If you load several Vicky 3 and inject the same full body morphs into more than one of them, the morph settings will cross talk. But this is easily avoided by injecting the morphs to the figures while they are alone in the scene, save them in the figure library and load them into the same scene after the injection.

Kelderek, I could see some instances where this would be useful. Suppose you were doing a scene from Nutcracker where you had the Sugar Plum Fairy and a corp of dancers behind her. If they all had the same body shape, it would look right. Nobody nice chooses bridesmaids for their uniformity, but ballerinas are another matter! Women in a maternity ward or longshoremen or temple guards could be tweaked this way for starters, too. Carolly

I was about to pose a question about this. I just found in P5 that if I: 1 - load the stock v3, no morphs, then 2 - load a second v3 and inject the Fairy body morph then 3 - Set the dial to 1, nothing happens. Then 4 - inject the Fairy morph into the first v3 (Fig 1) then 5 - set the dial to 1, both figures turn to fairies. Then 6 - set the second v3's dial to zero, nothing happens. I even tried the mill null character, following the instructions, and it didn't help. Is there a null character for v3?

The ERC code chunks for Victoria 3 are contained within external files in the !DAZ directory. The Control Figure entry in each ERC chunk is directed to "Figure 1". As such, when an injection is applied, the figure receiving the information is being told to look for direction from the channels in "Figure 1."

By default, Victoria 3 is named "Figure 1"... which is used for producing predictable results, in code, for ERC, NULLS and the like. Each time you load Victoria 3 into a new, blank, scene... in memory she occupies instance 1 (:1). As I stated above, when an injection is applied, the figure receiving the information is being directed to look to "Figure 1" for instructions; which in this scenario is the correct figure. Saving to the library records all the information in a single, albeit larger than the original, file. Stored as "Figure 1" with instances of 1 (:1) in the library, a NULL can then be used to buffer crosstalk (in Poser4, 5 doesn't need the buffer). The "Millennium NULL" works for any figure that uses the groups (identically named) used in a Millennium figure, or any subset thereof... so yes, it'll work for V3.

Basically, what it boils down to is the way Poser assigns [and stores] name and instance information in memory... and subsequently, files. Remember... ERC is a hack, delta injection is a hack, readScript is a hack, NULLS are hacks; all of which give Poser much more functionality than was intended, considered or available from its creators... but hacks nonetheless.

-Rob

It does cross talk with magnets however. I use Volup Vicky 2 magnets and two figures will always inherit the settings from the first loaded figure. Plus any pose file called up will set both figures so I have to set each manually. Also p5 and p4 still have a bug in which magnet dials are duplicated when saving a figure. This occurs with clothes that inherit magnets from a base figure ie volup vicky magnets effecting clothing.

"5 doesn't need the buffer" But I was using Poser 5 in my above scenario. Why did I get crosstalk? "The "Millennium NULL" works for any figure ... so yes, it'll work for V3" It didn't work for me and I followed the instructions from the DAZ page on the subject. Could it be because I was using Poser 5? Mason: multiplying magnets was one of the things they were going to fix in 5 and didn't. Until now, I thought crosstalk was the only P4 bug I thought they'd fixed in 5. Apparantly, they didn't fix that either.

You didn't get "crosstalk". What you got, was information intended for a figure named "Figure 1" (with an instance of 1) injected into a figure named "Figure 2" (with instances of 2). Again, the external ERC chunks in the source files indicate that, when injected, the selected figure (regardless of what that figure is named) should listen to "Figure 1" (instance 1) for instructions.

The way around this is to change your approach. Think of the processes as separate steps. First build each character... then build the scene. To do this, use new, blank, scenes to build each character independently... and save them as such into the library. When all of your characters contain all of the morphs you will be using in said character, and have been saved to the library, you can load them into the scene, in Poser5 without a NULL and pose them to your hearts content.

Using the NULL in Poser 5 is pointless, it doesn't serve it's intended purpose.

-Rob

Hmmm, it sure seemed like crosstalk. Anyway, thanks for the explanation and workaround (Poser's just full of those, ain't it?)