Mon, Nov 25, 4:44 AM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 24 8:11 pm)



Subject: Saving multi-figures as figures question.


kuroyume0161 ( ) posted Sun, 15 February 2004 at 4:55 PM · edited Sat, 23 November 2024 at 4:39 PM

When trying to save a multi-figure into the Figure library, Poser asks whether or not it should be saved as "Whole Group" or "Single Group". For a product that is to be sold, which do you recommend? Thanks Kuroyume

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


maclean ( ) posted Sun, 15 February 2004 at 5:56 PM

I suppose it depends a lot on the product. If the figures are inter-linked in some way, it might make sense to save them all together. Also, how many figures are there? A lot of users prefer to assemble the set themselves, if there aren't too many. If you do save them together, they must all be parented to one main figure. Just make sure that they're all parented and they all save properly. mac


kuroyume0161 ( ) posted Sun, 15 February 2004 at 8:10 PM

Yes, that's the ticket! :) Immediately after posting this message, the idea of a sort of "Null figure" entered my thick skull. I made a figure with only BODY and no geometry. Dumped all of the figures and props into that and it saved and loads properly. In this case, I want the user to have the option of constructing from parts (figures and props) or using preassembled objects (figures and props). The reason that I can't just parent everything together and avoid using the Null figure is that the main figures have Poserbones (see BL Render) for curving their geometries, which makes parenting useless for keeping the children attached, and are lengthened by scaling (since Poserbones require propagatingScale to keep up with the parent geometry), which deforms any parented parts in ways undesired. There are 8 props and 8 figures. All in all, serendipitous advantages in Poser seem to always have their disadvantages.

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


Tintifax ( ) posted Tue, 17 February 2004 at 6:00 AM

Hi kuroyume0161, this seems to be a great idea. Can you tell me how you created this NULL figure and how you dumped all the other figures in. I need that for my own product. Thanks in advance - Walter


kuroyume0161 ( ) posted Tue, 17 February 2004 at 8:58 AM

Copy a CR2, any CR2 should do. Delete the following: "figureResFile ..." statements (there is no geometry associated with it). All actors except the two BODY actors. Any references to other actors in second actor BODY section, although there shouldn't be any, but just in case. In the Figure section, delete all materials, Weld section, and AddChild section. Set "defaultPick BODY:1" if not already in Figure section. One caveat: If you parent Props to this NULL figure and save to the Figure library, Poser will drop in a "figureResFile none" statement for the BODY and no geometry references for the Props at all. So far, the only solution is to edit this CR2 by removing that statement and adding in the "figureResFile ..." references for external-geometry props or copying the "geomCustom" for internal-geometry props. Kuroyume

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


Tintifax ( ) posted Tue, 17 February 2004 at 9:04 AM

Thanks works great. After making this NULL file, I added all my figures in the hierarchy editor and saved them all together. Thanks - Walter


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.