Mon, Nov 25, 1:52 AM 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: morphPmdFile keyword?


kuroyume0161 ( ) posted Tue, 28 November 2006 at 5:40 PM · edited Wed, 07 August 2024 at 9:38 PM

Has anyone encountered this keyword, morphPmdFile, before and any information to relate on it?

I am already aware of the morphBinaryFile keyword that is usually coupled to figureResFile.  This new keyword has only been encountered in one set of props (Siro-Guma/E Fundoshi) and also includes a new keyword at the end of the prop definition, attribute   pmd_1.  As usual, why simplify the format when you can add fifty thousand new and exciting keywords! ;)

This keyword is pretty much identical to morphBinaryFile except that it is inside the prop declaratory section:

version
    {
    number 6
    }
prop –¼Ì–¢Ý’è 1
    {
    morphPmdFile :Downloads:Runtime:libraries:props:kousuke_made:Guma-Bora:David:E Fun_David_020.pmd
    geomCustom
        {
        numbVerts    1882
...

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


kuroyume0161 ( ) posted Thu, 30 November 2006 at 10:47 PM

To add to my own sounding here. :)

Well, haven't e-frontier been busy beavers!  I note that previously saved PZ3 files have something like this:

prop RHCap_1
 {
 storageOffset 0 0.3487 0
 objFileGeom 0 0 :Runtime:Geometries:ZygoteCostumes:Hats:blRHCap.obj
 }

whereas the newer save has this added (even though there is still a PZ3 PMD file):

prop RHCap
 {
 morphPmdFile :Runtime:libraries:props:!Test:ArcherCaps.pmd
 storageOffset 0 0.3487 0
 objFileGeom 0 0 :Runtime:Geometries:ZygoteCostumes:Hats:blRHCap.obj
 }

Maybe it was an SR or maybe I resaved this prop to the library and the morphs were placed in PMD (but I'm rather certain that it has had a PMD for some time for testing purposes).

This meant a complete update to my code, but rather simple in the end.  Still can't understand why this is placed in the declarative section instead of the definitive section (where the morphs are filled).  Makes my life difficult since I don't maintain a 'prop structure' proper as it were.  I reuse a prop/actor parsing class and the permanent representation is a tag on the object which doesn't carry file info - just active info.  Oh well.

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.