I tried to scale one of the people models to a drawing unit of 90cm (from 1 meter). And she doesn't quite 'hold it together';-) I also don't seem to be able to break the group to tighten her up. I am loosing hair trying to solve this problem...
Surely you’d have to export her to a 3D CAD program to do this..?
Rhino should be able to deal with it well, or maybe even sketchup?
In general there are a lot of requests here to do some alteration or to build something that is not at all what Capture should or can be doing.
I don’t believe it was built as a program that should be a one stop shop for everything, including sets or building models etc - it’s ‘just’ for lighting visualisation.
Years ago ‘another program’ tried to include CAD elements within its core; it was a complete mess; while the lighting visualisation was very good for the time, its so called CAD was a disaster . There were plenty of CAD programs, some of them even free that could do a much much better job.
And the same is true now…
( I'll try to do it for you here if you don't have access to a cad program...? )
cheers
Tony
Posted By rabbit on 8/21/2026 9:54 PM Surely you’d have to export her to a 3D CAD program to do this..?
Well. When you import a 3d model into capture, in the dialog that appears you can set the drawing unit used by the model (so it's correctly scaled to the capture world.
After import, you can change this value, in the object's properties, if you got it wrong, or mis-typed the value. So this is a kind-of valid workflow, but not recommended.
This does work,for simple models that are a single element, but when objects are imported in sections, it scales each individual section around their individual origins, rather than the origin of the combined model (or the origin of the model before they were exported and imported). If you go to a more aggressive scale factor (e.g 0.5) you'll see that the shoes and feet also separate from the rest of the body. If the model hierarchy was flattened before bringing it into capture then the model would likely behave correctly. But it looks like the import has maintained some file structure to the model.
For most internal library objects you wouldn't have this option, but some of the more complex items (like the newer people that are fixed sizes) are clearly imported models and have this user defined scale.