Out of scale when exporting to obj?

Need help? We are here.
1

I want to use some of my designs in other 3D softwares (i.e. CLO, which need .obj format). My design seems to be correct in scale (using metric/mm), but for some reason, the exportet .obj is tiny!
When trying to open in “Windows 3D buider”, I have to select “meters” as a scale, which results in the correct size of the design. Unfortunately that means a lot of manual scaling in CLO, which isn’t great.
Is there something I am doing wrong, or how can I solve the issue?
Thanks!

(I tried to attach a test design, that according to my shapr3D should be 8.6 x 5.1 x 2 mm, but the system doesn’t allow me to upload since I am a new user :wink: )

2

Hi, OBJ is a unitless file type, so getting the expected scale is a balance between the source application’s set protocol for embedding numbers into the file, and how those numbers are read when imported.

For now scaling after import will be the workaround until we decide if we will implement a unit selection box on Import and Export for unitless file types. This way you can match units when sharing unitless file between CAD tools
I found a doc on quick CLO scaling tips:

3

i’ve had the same issue with the tutorial part going to obj. i thought it wasn’t exported, but it was just tiny. to import into Codea, i upscaled it by 1000, so it goes from about 50mm to 5m and is good sized.

can i upscale the object in Shapr? Will that change the perceived size in other apps? I’ve not found a way to scale the whole thing.

thanks!

4

Hi Ron,

You can try upscaling the file first in Shapr before exporting.
To Scale:
Tap on Transform
Tap on Scale
Select the body and pull up the scale icon to upscale.

Let me know if this helps!

5

thanks, that helped somewhat, but i set that bracket to a height of about half a meter, exported to .obj, converted that to dae with convertmesh.com, imported the dae into second life and the resulting object was about one centimeter or less.

is there any general guidance on this topic or is it just trial and error?

thanks!

6

Hi Ron,

Please can you set the units to MM in the app before exporting and also in Codea before you import the file?

Most apps seem to read entered dimension numbers for unitless file formats like the OBJ when importing with the unit set as MM.

7

OK. I have created several cubes in various sizes. What Shapr seems to do is to equate 1 meter of Shapr size with a coordinate of 1.0 in the Obj file. So a one meter cube will have corners at 0,0,0, 1,1,1 and so on. If you scale in mm or meters or cm it remains true: 1 meter = 1.0.

If you scale in ft, 1 ft = .3408, which is exactly the number of meters in a foot.

Codea seems to have its internal coordinates in meters, so a standard Codea cube is 1 meter.

Someone should document this :slight_smile:

I suspect that the problem when I went thru mesh converter.com may have been an issue with that program, or with my mistaken interpretation of what I did.

Anyway Shapr makes sense once you realize its native outlook is meters.

Now if we just had texturing and UV maps …

Great program!

1 Like