Thanks Evan- That's great to know and makes total sense. I tried your suggestion (in Rhino) and created a workspace in meters than imported my .obj file, which now came in at what appears to be at full scale.
Thanks again for your help and fast reply!
evan firstname.lastname@example.org 8/21/2014 2:26 PM >>>
The Scanner app exports obj files scaled such that 1 unit in the file = 1 meter in the real world. OBJ file coordinates are unit-less, so most CAD & modelling tools which import them will just assign the default system unit to the imported mesh, often scaling it like crazy.
In Rhino the default unit is millimeters, an imported scan of 1.85m-tall me would probably end up looking a bit like an ant =] Similarly, in Blender, I'd be a bit shorter than the 2-unit-tall default cube.
So what can you do about this right now?
- Check the import dialog for a "units" or "scale" option - some tools have this for unit-less formats.
- Try changing the system unit to meters before importing.
- Most CAD & modeling tools will allow you to scale the model appropriately after importing as Damien suggests, or...
- If all else fails, you can scale and re-export using another tool before using your primary tool. Meshlab and Blender are both free tools that can do this.
Posted by evan on 08/21/2014