Well as someone who works on the content side of things changing the “relative” scale of an object is not a good idea as far as map objects goes.
A unit is not a true form of measurement but a means by which a form of measurement can be applied that is true no matter what 3d environment is being used. One (1) unit is the same in 3ds Max, Maya, Blender and even Unreal 4 and is considered an absolute value.
World scale is where you tell your application what a unit represents as a form of measurement and the most common form of measurement is what would be considered a real world value. Metric is generally used as it is a ten based measurement that’s easy to convert from a unit value and is usually the first value looked at as far as physics based lighting and simulations requirements goes.
To match up with Unreal 4 best practice is to set the edit environment to 1 unit = 1 centimeter and build all objects using it’s real world equivalent as the reference as to size.
Local scale is the true size of the object at 100% of it true world measurement and is a seed value as to physics based requirements that would included simulations, lighting, and materials. If you make a box 12cmx12cmx12cm then the world scale will look at it’s local value as being absolute once again as to that value.
Relative scale is where things usually goes wrong as it is not an absolute value as represented by local or world values but a change in the visual representation of one object as compared to another. You could easily change our 12cmx12cmx12cmx box to the size of a Death Star but the World will still see our Death Star as being a 12cmx box. What I do know is this is where 90% of all problems related to the creation begins at it’s root cause and “does” create unusual problems as to proper rendering with out artifacts and unusual behavior as to simulations.
I also know that the same issues can be transferred to other applications and is why I would not suggest changing the scale of an static model in Unreal 4 as I’m assuming that I’m only changing the “relative” scale of the object and not the true local scale.
Created content are designed to snap together and if mixed with edit in place objects is almost impossible to scale up by selection after the fact.
Assuming as imported the object imported into Unreal 4 is based on it’s local scale, as I’ve tried to import an object based on it’s relative scale and has always snapped back to it’s local scale, the ability to change the scale of the object is based on it’s relative scale and local as well as world scale are fixed values that can not be changed.
No matter how much you change the scale of an object it’s local scale will always remain 100% as imported so things like physics will still behave as expected of an object who’s relative scale has not been changed. So one can only imagine what would happen if trying to render a toy box the size of a Death Star.
This is why I would option to scale down the “relative” size of a skeletal character, as the change is inherited from the capsule down, and is at the least a much easier test to preform to see if it will work via discovery rather than trying to up size a static model already set to it’s true world scale.
This is not to say that things will be problem free but I think it’s a better option to play around with 1 solution than a possible 10,000 objects doing their own thing.
Overall though not a new subject as UDK did have it’s more serious issues as to properly scaling with no true form of scaling at all.
Please explain “official”