Is there a way to make the scale an actual representation of the measure system (metric) I use? I don't know why this is made as it is because it's totally not making ANY sense and broken as well. Why is scale a multiplication factor instead of a representation of real world values? [Metric system:] Why is a cube 2 meters at a scale of one?
I chose metric and set the unit scale to 0.5 so it would actually be what I enter it to be, but this blender is doing what it wants. First it acts like I want. Doing a cube of 20 x 12 x 1 meter works. Then I save everything open the project up a day later and when I add a second cube of the same size, it's not the same size as the object I created a day before. Even though the settings are still the same (metric and unit scale of 0.5). I can't believe that crap. i mean I understand it in a game engine like unity or unreal engine to be a factor instead of a unit, but not in a 3D modelling tool -.-

what is also not understandable is that when I create a cube of height (z) 4, I actually have to put in 4 into the location z field so it is on top of the grid even though the origin is in it's middle. so actually shouldn't i have to enter for the location just 2... 

Is there any way to correct this so scale can actually be set in meters instead of a multiplication factor??? Can't understand that implementation at all, especially annoying when it's not working as it should
If you set up a unit scale for Blender, inputs will parse the strings you enter in any field which expects length.

Supposing you have set the units to meters, and the Unit Scale to .5 (at least, in my build)..


If you enter '1', Blender will always interpret that as 1 Blender Unit (50cm)
If you enter '1m' Blender will interpret that as 1 meter
You can enter '25cm' or '250mm' or '.25m' etc. to refer to that length
If you enter '1in' Blender will interpret that as 1 inch. Because you have declared your dimensions to be in meters, that will be translated to 2.54cm
You can even enter an expression like '25m / 4' to get 6.25 meters


I'm open to correction, but it is true that the last-used radius for object creation can not be made to persist in the .blend file, and reverts to 1 of your declared base unit when you reopen it. However, the last creation size requested (in the tool region) does persist within sessions, on a per-primitive basis.

These are deliberate choices on the part of the developers, not careless. There are many choices in Blender that I don't personally agree with, but in the vast majority of cases, if I stop to think about them, I can see the arguments for the choices having been made that way. Usually it's to do with 'cleanliness'.. i.e. consistency between different parts of what is, after all,  a large application. I have been pleasantly surprised by that consistency in Blender's way of thinking, compared to many proprietary applications, especially those with a long history of accretions .. :)