Tue, Nov 19, 11:07 PM CST

Renderosity Forums / Poser Technical



Welcome to the Poser Technical Forum

Forum Moderators: Staff

Poser Technical F.A.Q (Last Updated: 2024 Nov 13 12:50 am)

Welcome to the Poser Technical Forum.

Where computer nerds can Pull out their slide rules and not get laughed at. Pocket protectors are not required. ;-)

This is the place you come to ask questions and share new ideas about using the internal file structure of Poser to push the program past it's normal limits.

New users are encouraged to read the FAQ sections here and on the Poser forum before asking questions.



Checkout the Renderosity MarketPlace - Your source for digital art content!



Subject: attachFBMdial 'internal name' or 'display name'


kuroyume0161 ( ) posted Tue, 13 November 2007 at 1:34 PM · edited Sun, 28 July 2024 at 5:42 AM

Nerd3D is about the only source for this Poser 6+ FBM keyword but details are sometimes a bit lacking.  It appears that the FBM dial itself will use the name (from createFullBodyMorph) as both internal and display name.  But what name is expected for the morph dial being attached to the FBM dial - internal or display or either?

Also, Nerd3D mentions that ALL dials with that name will be 'attached' to the FBM dial.  I take it that this means throughout the entire figure?

Finally, Nerd3D mentions ability to create PBM (Partial Body Morphs) with this tech, but I don't see an example or a method how - unless there is a way to specifiy which body part receives the createFullBodyMorph objective.

Danke! :)

C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, you blow your whole leg off.

 -- Bjarne Stroustrup

Contact Me | Kuroyume's DevelopmentZone


lesbentley ( ) posted Tue, 13 November 2007 at 4:11 PM

With respect to 'attachFBMdial' it seems you must use the internal name of the prospective slave channel, eg with:

                targetGeom tgA
                        {
                        name tgB

You must use: attachFBMdial vpX tgA


lesbentley ( ) posted Tue, 13 November 2007 at 4:58 PM

Quote "Also, Nerd3D mentions that ALL dials with that name will be 'attached' to the FBM dial.  I take it that this means throughout the entire figure?"

Not only throughout the entire figure, it seems this also applies to any parented props, but not to parented figures (probably applies to any parented item that shares the actor number). But it's not ALL channels with that name, you can't use this to slave 'ytran', so I assume it only applies to targetGeom channels.

Quote "Finally, Nerd3D mentions ability to create PBM (Partial Body Morphs) with this tech, but I don't see an example or a method how - unless there is a way to specifiy which body part receives the createFullBodyMorph objective."

I am not aware of any way to make 'createFullBodyMorph' place the valueParm in another actor, though it would be nice if such a way existed. I assume the root actor is always used rather than the name "BODY", though I have not tested this. What I would really love to see is a pz2 way to create any type of channel in any actor.


lesbentley ( ) posted Tue, 13 November 2007 at 5:32 PM

Another other point of intrest. Say you have a figure with this FBM channel in the BODY:

                valueParm vpX
                        {
                        name DialName

You can use "attachFBMdial vpX tgA". But if you use "attachFBMdial DialName tgA" a new valueParm channel will be created with the internal and dial name "DialName". So you should use the internal name for the master valueParm channel as well as for the targetGeom channel. And if you use 'attachFBMdial' it seems you don't need to use 'createFullBodyMorph' first.


kuroyume0161 ( ) posted Tue, 13 November 2007 at 5:34 PM

Thank you, lesbentley! :)

These are the details not included by Nerd3D - and it can be somewhat vague when certain information is omitted.

Including parented props is extremely interesting.  What about conformed figures?  Do they follow the same 'same actor number' situation?  targetGeom only is also interesting and probably a good thing to know to avoid possible odd behavior for my purposes.

That is my feeling on PBM here.  I scoured my Runtime to find a possible instance without any results.  Also, a check of the Poser.exe itself doesn't show any other keywords that would allude to such support.  Either Nerd3D isn't coughing up the details ;) or this was included incorrectly.

C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, you blow your whole leg off.

 -- Bjarne Stroustrup

Contact Me | Kuroyume's DevelopmentZone


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.