This comes from the way that Floating Point (IE numbers which contain a decimal point) numbers are held in memory. This oddity shows up in all sorts of applications, not just Poser (and here I'm talking about anything from games through the operating system itself through to financial software. Although the last have to take extra-special precautions to avoid problems..) The values which are actually saved are (probably) close enough to to the value you typed for it not to make any noticible difference to the final render (or to anything else, for that matter). Ignore it. EG: 64.99998 (from the example above) is "wrong" by about 2/100,000. Anybody render in sizes which exceed 500,000 (in any direction)?? Cheers, Diolma (and yeah, I know, there are very, very occasional times when it really does matter. In that case, enter the ".0" as pteryx suggested..)