Lucy_Fur opened this issue on Aug 02, 2002 ยท 5 posts
Lucy_Fur posted Fri, 02 August 2002 at 1:23 AM
I was going thru ronknights tutoral on crosstalk and got to the point where I needed to spawn morph targets to create a custom character blank. Some of the morphs I have for Luci are fbms - of which Poser will not spawn a morph target for.
My thinking is that now I'll have to go thru Luci and for each body part the fbm applies to, make the necessary adjustments.......
I guess I just want confirmation of that weary sigh
Thanks in advance :)
Peace...
L_F
eirian posted Fri, 02 August 2002 at 3:29 AM
Poser will spawn a FBM. What you have to remember is a FBM is not, technically, a morph. It's a controller for all the other morphs. That means you can't transfer a FBM from one CR2 to another unless the second CR2 has all the relevant morphs. (In other words, you can't use Vicky2 to create an FBM, then transfer it to a Vicky1 CR2 - it won't work.) To create a FBM, don't use the "Spawn morph target" command. There's one called "Create Full Body Morph" - that's the one you want. I've found it best to take the "long" way: spawn a morph target for each body part first, then zero everything and set the new MTs to 1, then create the FBM, then zero everything again and set the FBM to 1. Then save the CR2. Lengthy, but that way I can use morph manager to move it to a V1 CR2, or use Tailor to move it to low-res Vicky...which is easier on the RAM when I render. But you don't have to do it that way. Whatever works :-)
FishNose posted Fri, 02 August 2002 at 3:45 AM
I never use fbms - in fact, I often throw them out of my cr2s. Reason - a pose file doesn't save fbm values. Which, in my view, makes fbms as good as useless. This is one of those silly Poser limitations that I HOPE will be addressed by Poser 5. I rather go in and set individual body parts by hand. Also, Morph Manager can't see or transfer fbms, that I know of. For avoiding crosstalk: In my view, don't do it the long way, like Ron says - instead, use the Millenium Null in between your crosstalk-sensitive figures. So: Load a Null. Load Vicki/Mike etc. Load a new Null. Load another Vicki/Mike etc. Load another Null. Etc, etc. With each new Null, choose the 'Body' so you see 'No Actor' before loading the next Millenium figure. This way you avoid crosstalk, even in PZ3 files. Oh - and remember, pbm morphs are just as sensitive to crosstalk as fbms. :] FishNose
ronknights posted Fri, 02 August 2002 at 5:49 AM
I ran into a problem with Full Body Morphs. My Marlin character had a heavy FBM, and I couldn't find the heavy setting for all parts of his body. He came out with a huge belly, and skinny legs, etc. That was one very frustrating problem. In the end, I still don't trust the other methods of combatting Crosstalk.
Jaager posted Fri, 02 August 2002 at 7:08 AM
"are fbms - of which Poser will not spawn a morph target for." As Eirian says, Poser does indeed Spawn FBM data, in fact, if you hand set the pbm- dials and do not turn the FBM off the values will add. It is the 'combine morph targets' function in MM4 that does not accept FBM data. If you are making a single morph custom character - for its own CR2, it is not necessary to make it a FBM since it will be 'ON' all the time anyway. "Also, Morph Manager can't see or transfer fbms, that I know of." Not from a CR2 - no From a PZ2 - yes Just make the extension on the donor CR2 be PZ2 before you open it in MM4. BODY will show and valueParms can be copied. "a pose file doesn't save fbm values. Which, in my view, makes fbms as good as useless." Something similar applies to pose files. A Poser saved pose file does not save valueParms and in fact has no actor BODY section to take them. You can make a pose file template with this section and empty of morph data to copy into or you can paste the following section into every pose file that you want to have valueParms. actor BODY:1 { channels { } } This should probably be the first actor section. Anyway, once you have the BODY section in the pose file, you can copy the valueParms over from the main CR2 - after you make it a PZ2. If you make the template, what you would do is copy the valueParms from the CR2(PZ2) and the other dial settings from the Poser pose file into a copy of the template. The other thing is = you can also copy scale channels from the CR2/PZ2 into the pose file, because those channels also show in a PZ2 in MM4. Just have a care for which scale dials you use.