Forum Coordinators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 26 1:43 pm)
I have a Python script for P5, used to set the distance for the focus option in Firefly, which uses a value of 8.85 feet to one Poser Unit. This is 106.2 inches. Dr. Geep uses the simple-to-calculate 100 inch value. Some versions of Poser are believed to have used the simple 96 inch value. If the strange Imperial meadurements came to some nice round figure in metres, it'd make sense, but they don't.
People vary. Things don't. There is, for instance, a standard width for doorways in modern houses. So if you have a model scaled according to Geep, or Poser 5, or whatever, that's what sets the size of the scene. The only significance to the scale which Poser defines is if you're set to use feet or inches or metres, instead of Poser Units, on all the parameter dials. And I know Poser 5 had settings which used Poser Units even when everything else used feet.
Remember ... "With Poser, all things are possible, and poseable!"
cheers,
dr geep ... :o]
edited 10/5/2019
Any conversion between Poser and real world units is a matter of convention. The standard convention has been that one foot = 0.125 Poser units, one inch = 0.0104166... Poser units. On this same convention 1 meter = aprox 0.410 Poser units. On this convention a Poser unit is 96 inches, and 96 inches = 8 feet. Poser 5 introduced the option to display units in inches, and it seems that the convention they used in the first release was that one Poser unit = 103.23 inches. I have heard that diffrent releases/service pacs of P5 used diffrent conventions, one of them being 0.125 to the foot, but I haven't verifed this. The standard convention that one foot = 0.125 Poser units is based on work by Freakachu, here is the text of one of his readme files:
Here's the logic behind the prop. TwoMeter.pp2 and Ruler.pp2 are based on a bit of information from the Poser manual* which states that "Poser considers one DFX unit equal to the male figure's height--about six feet." In the Poser universe, the standard poser unit equals one and a third DFX units, or eight feet (which makes for a nice round number.) The poser unit is the distance that the translate tools or parameter dials need to move an object a single unit in Poser. (i.e. A "y-trans" setting of 1.000 would move an object 8 feet above an object with a "y-trans" setting of 0.000) Since the male figure is 0.750 poser units tall it's easy to do the math and divide the units into their English and Metric counterparts. Here's the breakdown: 1 foot = 0.125 poser units (a "box" prop scaled to 125% would be a cubic foot) 1 meter = 0.410 poser units (a "box" prop scaled to 41% would be 10 cubic centimeters) TwoMeter.pp2 and Ruler.pp2 are meant to approximate the heights of your Poser figures. For the TwoMeter.pp2 prop, each segment of the ruler, up to 150 cm, is approximately 50 cm in the Poser universe. Segments past 150 cm are 10 cm high. For the Ruler.pp2 prop, each segment of the ruler, up to five feet, would be approximately 12 inches in the Poser universe. Segments past five feet are 2.4 inches high. Now if someone could build a Poser scale. AMc *p 167 - - - - - -
There are other conventions such as Dr Geeps. Personally I stick with the one Poser unit = 96 inches = 8 feet, one foot = 0.125 Poser units convention.
Since the basic Poser Unit is referencing a human male model, it doesn't have to be absolutely precise to the millimeter. Having dated normal males in a height range of 5'2" to 6'4", it seems obvious that they could all walk through doorways and sit down in a mass-produced chair without too much fretting and worrying about whether their feet would touch the floor. Is Vicky taller than Posette? Does it matter? If a figure converts to 5'6" or to 5'7 1/2" does that make the intended character any more intelligent, feisty, sexy, powerful? What does any number have to do with body language? Carolly
Poser translates 1 Native unit to 103.2 inches.
Do the same thing on Poser5 and the result will be 100 inches.
Hi MarcioAB,
I tried your little experiment with Poser5 (v5.04.325) and the result was 96 inches translated from 1 "Native unit."
Wuzup with that. huh?
BTW -
What version of Poser5 do you have?
PC or Mac?
Coffee, tea, or milk?
cheers,
dr geep
;=]
Remember ... "With Poser, all things are possible, and poseable!"
cheers,
dr geep ... :o]
edited 10/5/2019
Carolly must be a very funny person. She has a point (does 5% matters?), but being pessimist, I think this changes in units may end up in troubles somewhere. In CAD systems, changes in units or tolerances are terrible.
Dr. Geep ... you caught me. I got a new PC and regard Poser, I installed only Poser6 on it, so, I do not have Poser5 installed anymore to test. I got that information (the 100 inches) from my previous notes - but I believe you ... so, title change.
Ducks don't have scales, they have feathers... except the ducks from Orion have metallic plates and the clattering is quite fearsome. The sky darkens and fills with the noise of armies and the guardians of the granaries shudder at their approach. Hmm... 8'6". That is a bit of a stretch, even for the supermodels on stilettos. However, I think a woman's height would have made more sense if Larry had thought ahead to how the program would actually be used. Since the height does keep changing, I'll suggest it to him. :) Considering that folks use CAD, MAX, C4D, Maya, Blender, ZBrush, etc... and not all those programs agree upon a standard height, it really is not essential that Poser conform to any one of them. As long as the native units are always native units and roughly set to human standards, we should be fine. Consider this: the neolithic "yard" was a bit over 29", that didn't stop our primitive forebears from setting up trilithons. If Stonehenge, the Haggia Sopphia, the Parthenon, and the dome of St Paul's manage to stay up despite all having been built to a different standard, then why are we arguing over a virtual sliver? Carolly PS: I know that Orion is a constellation, not a planet.
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.
Full question on the title. Is that correct ? Not tested yet, but can this difference cause problems ? thanks.