Thu, Jan 9, 5:41 AM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2025 Jan 09 3:46 am)



Subject: What is poser7contentFile?


smalll ( ) posted Sat, 19 April 2008 at 5:58 AM · edited Wed, 04 December 2024 at 9:27 AM

Hi.
I saved my work as 'test'
And there was born test.pz3 and test.pmd file.
test.pmd file is Poser7contentFile.
What is poser7contentFile?
How can I use it?
Can you help me?
Please.


PhilC ( ) posted Sat, 19 April 2008 at 6:16 AM · edited Sat, 19 April 2008 at 6:17 AM

It contains the morph data in binary form. You can opt to have it saved like that or alternatively within the PZ3 file by going to the Poser menu Edit > General Preferences > Misc.

You do not need to do anything with it other than keep it with the PZ3. When you load the PZ3 it will auto load the PMD.

Hope that helps :)


smalll ( ) posted Sat, 19 April 2008 at 6:39 AM

Hi, PhilC
I know you.
You are great poser.
The honor is more than I deserve.
I´d like to express my heartfelt thanks to you


Daymond42 ( ) posted Sat, 19 April 2008 at 8:01 AM

Hey PhilC! About this topic of conversation... is there any real benefit to having the morph data as an external file? I mean.. sure it makes the PZ3 file smaller, but you still need the PMD file anyhow.

I'm just trying to understand the option, myself. :D

 

Currently using Poser Pro 2012 (Display Units = feet)

AMD Phenom II 3.2ghz (6 cores)

8gb RAM

Windows 10 Pro 64bit


svdl ( ) posted Sat, 19 April 2008 at 9:41 AM

There is some benefit to using external morph data. If you have two figures (say two Sydney G2 figures) in the scene, the actual morph data will be stored only once. This saves both hard disk space and memory.
The two Sydney figures can have different morph dial settings, but the actual morph data remains the same, that is why this works.
Second, a PMD file contains the morph data in binary format, which is far more efficient than in text format. The total disk usage with PMD files is significantly less than incorporating everything in the .pz3.
Third, using PMD files to distribute morph data is one of the legally acceptable ways to do so (see the e-frontier EULA). Distributing them as .OBJ files can land you in hot water.

The pen is mightier than the sword. But if you literally want to have some impact, use a typewriter

My gallery   My freestuff


Daymond42 ( ) posted Sat, 19 April 2008 at 9:47 AM

Ahhh, that makes a lot of sense! I think I understand now. I have my stuff set as external morph data anyhow.

Thanks for  the quick response. :D

 

Currently using Poser Pro 2012 (Display Units = feet)

AMD Phenom II 3.2ghz (6 cores)

8gb RAM

Windows 10 Pro 64bit


svdl ( ) posted Sat, 19 April 2008 at 10:43 AM

A disadvantage of external morph files: if you want to import your .pz3 file into another application (Vue, Carrara), it won't work. And somehow .pmd files tend to make Poser less stable, at least on my systems. I've got enough disk space (2x500GB) so I don't use external morph files.

The pen is mightier than the sword. But if you literally want to have some impact, use a typewriter

My gallery   My freestuff


kuroyume0161 ( ) posted Sat, 19 April 2008 at 12:08 PM · edited Sat, 19 April 2008 at 12:09 PM

To add to svdl's warnings, beware of using certain DAZ figures (e.g: V4) with PMD morphs as you end up with a PMD file that doesn't work at all even though only a morph or two are corrupted.  When stored in the PZ3 these corrupted morphs are ignored by Poser allowing the rest to be read properly.  interPoser Pro for Cinema 4D imports morphs from PMD files and ignores the corrupted ones. ;)

As noted, binary storage of floating point numbers is far smaller than using text.  All floating point numbers (currently) are stored binarily as 4 bytes each.  Although 0s only take one byte in text, most floating point values are more like 1.008909830298 (which is a lot of bytes for one value - each character, including the '.' is a byte).  The morph indices are only 4 bytes in binary as well.  If the indices go beyond 9999, then text storage is using more bytes.

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.