Thu, Nov 28, 10:52 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 28 11:20 am)



Subject: Vicky 3 crosstalk!


Kelderek ( ) posted Mon, 30 December 2002 at 10:02 AM · edited Thu, 28 November 2024 at 10:43 PM

Content Advisory! This message contains nudity

file_38740.jpg

We were told that crosstalk was cured in Poser 5, but obviously Victoria 3 has brought it back... Has anyone else noticed this? I made the following example to show the effect: 1. Loaded the first Vicky 3 2. Injected all full body morphs 3. Set the "Barbarian 1" morph to 1.0 4. Loaded the second Vicky 3 5. Injected all full body morphs to her After doing this, the morph applied to the first figure got transferred to the second one. No morph dials works on the second figure after the morph injection (they still work on the first one) Is there a way around this or do I have to dig up the old null loader again? :-(


rogergordian ( ) posted Mon, 30 December 2002 at 10:12 AM

Why not just inject the actual body morphs you wish to use with each character? Vicky 3 was designed that way.


rbtwhiz ( ) posted Mon, 30 December 2002 at 10:36 AM
  • Load the first V3. - Inject morphs required. - Save cr2 to library. - Delete first V3 from scene. - Load second V3. - Inject morphs required. - Save cr2 to library. - Delete second V3 from scene. -If using p4, follow established use of "Millennium Null". [http://www.rbtwhiz.com/rbtwhiz_ERC.html#CTKillForPZ3] -If using p5, I cannot speak from experience... as I've not used p5, but if crosstalk is solved as claimed you should be able to just load the figures from the library. Why? My thoughts are along the lines of: The morph injections contain, in addition to delta information, the appropriate ERC code. The ERC code points to "Figure 1". When injected into "Figure 2" (the second instance of V3), the ERC code still points to "Figure 1", thus listening to "Figure 1" for commands. -Rob


Roy G ( ) posted Mon, 30 December 2002 at 11:15 AM

This may actually be an opportunity. People have noticed that working the dials in Poser 5 longer transfers morph settings to that same figures clothing morphs. If we can figure out how to have "Controlled Cross-talk" I see that as an advantage. The ideal situation would be that if a figure is conformed it accepts cross talk. If that figure is independent it does not.


Kelderek ( ) posted Mon, 30 December 2002 at 11:43 AM

The method described by Rob works!! Obviously you should not inject the same morphs into two different Vicky 3 while they are in the same scene. By saving and deleting the first Vicky and then adding her again after injecting the morphs to the second Vicky you avoid this "new" version of crosstalk. Thanks Rob :-)


milamber42 ( ) posted Mon, 30 December 2002 at 12:19 PM

I loaded 2 V3 figures that were saved with the morphs injected, and I did not see any crosstalk.


quixote ( ) posted Mon, 30 December 2002 at 4:46 PM

.

Un coup de dés jamais n'abolira le hazard
S Mallarmé


Jim Burton ( ) posted Mon, 30 December 2002 at 6:38 PM

I'm too lazy most of the time to use Rob's Null Loader, or I just don't plan that far ahead, one thing I often do is just run the offending morphs in the second figure backward to remove the unwanted change. You can't use the FBMs (as the master figue is using it), but the individual morph dials can be turned back.


EricTorstenson ( ) posted Mon, 30 December 2002 at 9:51 PM

A trick I use is to save the null loader as the default figure (so when you start a new poser document, there is always a "millinium null" in scene. It does occassionally cause problems, but it can easily be deleted. I almost never use non-mil figs (though JBs enhanced posette might change that :) eric


PabloS ( ) posted Tue, 31 December 2002 at 12:45 AM

.


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.