Ok… Campbell, would like to summon you here, meshes/curves/metas make a specific call to WM_operator_view3d_unit_defaults() which counter balance the scale effect, so that they get still created with there default size (1 meter of radius). Other objects (cameras, empties, lamps, etc.) do not.

Imho, with a scale, of 0.01, one should expect objects with default radius of 1cm, so I would just get rid of that func. Would be consistent with what you get in existing scene when you change unit scale, too.

What do you say?

To describe the use case here..

I am making models to export to a game engine that uses centimeters as it's units. It seems like it would be a good idea to set units to "metric" (which in blender appears to mean meters) and use scale of 0.01 to scale everything into centimeters. This works well for me, if i set 100cm or 1m in blender then i get a 100cm object in my game engine.

Here is the process i end up having to go through to make this work..

1. Set units to metric
2. change scale to 0.01
3. Change view clipping from 1mm to 10m, to 10cm to 1000m
4. Change camera clipping from 1mm to 1m, to 10cm to 100m
5. Scale the camera from 1,1,1 to 100,100,100

Not sure if this is the intended use case for the "scale" factor, but as you can see, i just want to work in centimeters instead of meters. It works pretty well but have to go around and tweak the clipping and camera values as they don't change when the scaling is altered.

Other alternative workflows to this are...

• Make everything 100 times bigger than default (but this ends up amounting to the same problem)
• Scale everything by 100 on export, but then this means having to remember to work in meters instead of centimeters in the editor.