pikesPit posted at 7:02AM Wed, 26 April 2017 - #4303467

However, I think working with smaller-scale units is better. Poser produces rounding errors in the last one or two decimal places when saving or loading (that's why you sometimes see dials which have a value of -0,000). So the less decimal places are necessary for maximum precision the less this matters.

This is not an accurate recommendation. The Poser DISPLAY Unit set to inches has only an effect on the GUI. Internally and in every file format, geometry coordinates are exclusively stored in Poser Native Units, which is because the native or "internal" unit is, by definition, the Poser Native Unit and NOT the Poser Display Unit. (PNU vs. PDU)

Furthermore, the disparity between 103.2 vs. 103.20000458 is the result of truncation of precision when the data is stored as a 32-bit float vs. a 64-bit double, compounded then by additional issues when converting to decimal representation for your viewing pleasure.

By way of demonstration, I made a scene with a box, which I moved to yTran = 103.2 inch and saved. I also reset and then moved to yTran = 1 PNU and saved. The two files were identical, except for the movie file name (which is the file name so they were different). The value written in the file was 1 - just the digit, no 1.0000 etc.

As well one should note that the internal unit for the material system is inches, not PNU. No explanation is given as this detail isn't in the manual - instead it is something I learned from saving Poser materials and looking at what they have in them.

---

Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)