LOL, Ian! Good points! Our only "mistake" is that we think like Humans ;-) In a nutshell, you are partially correct in that ANYTHING reduced to UNITY will equal 1. Mathematically speaking, "ANYTHING multiplied by its inverse" = 1. All this "prooves" is that "One Poser unit" = 1 or, more precisely 1 = 1. This is what has tripped up many attempts to "prove" various Poser scale theories, and is why I have tried to refrain from calling this "mathematical proof". What I have posted above is, of course not the entire proof, most of which is contained in other threads; rather it is more like supporting evidence based on testing an assumption - what is important to note is not necessarily that the box comes in at 1 PU tall (because we already know that it was reduced to unit value, mathematically in MAX), but that when compared to a P4 male figure (at 6 feet tall) it is 8 feet tall IN POSER even though it is 1 UNIT tall in the 3DS or OBJ file. You are correct that fundamentally it is based on the FACT that the Poser4 Male figure is 6 feet tall, and would be meaningless without that KNOWN value (the 6' parameter has been verified by Curious Labs, and is observable in Poser5 with units set to feet or inches - see my note on the Poser5 scale bug above). So far, so good, but where your logic fails you is when you suggest "Does this not mean that 1 Poser unit is actually 1 inch in MAX?" Here you are confusing the meanings of "units" and "scale" which I have illustrated in previous posts, but will try to briefly explain here. In any 3D file document (3DS, OBJ, C4D, LWO etc.) all dimensions (vertex coordinates) are recorded as a series of numbers without any reference to units of measurement (except as a single notation line in SOME file formats). For example, the box we described above is 1 UNIT x 1 UNIT x 1 UNIT in length, width and height in the FILE that is passed from the modeling program to Poser(NOT 1"x1"x1"). If you import that SAME file into a program (or even back into MAX) while using a different SCALE than the one we used to create the box, it could appear to be a 1 foot cube, a 1 inch cube, a 1 meter cube, etc. based on what the internal SCALE of the importing program is currently using at the time of import. In other words, ONE UNIT is meaningless without SCALE information and the two are not always the same (such as architectural scales like 1/4" = 1 foot). Just remember that UNITS are relative values and SCALE is the RATIO or conversion factor for translating one measuring unit standard to another. Poser does not use "inches" or "feet" or "meters" as its UNIT of measurement, it uses a measuring unit called the "Standard Poser Unit". All numbers are recorded in these units, including the numbers used in exporting and importing files with other applications. To translate these numbers to meanignful units in other applications, we need the SCALE information (1 Poser Unit = 8 if your program is using FEET as UNITS -- 1 PU = 96 if your program is using INCHES as UNITS -- 1 PU = 2.4384 if your program is using METERS as UNITS). Also note that this has nothing to do with 3DS MAX except that I used it in my example. The same thing applies to ANY modeling program, using ANY unit of measurement. As long as you know the correct conversion factors, you can model precisely and bring your model into Poser to be EXACTLY the dimensions you expect them to be. This is not just about making a 96" box that JUST HAPPENS to come into Poser at 1 PU, but it is about making a chair that has a seat height of 17.5" in your modeling program and having it properly FIT a POSER figure just like the SAME chair would fit a 6' tall person in OUR world. For exact conversion standards between any program and Poser, see my next post.