STL files import in cm, instead of my working units

STL files import in cm, instead of my working units

cristiprefac
Explorer Explorer
5,784 Views
27 Replies
Message 1 of 28

STL files import in cm, instead of my working units

cristiprefac
Explorer
Explorer

Hi,

 

After the latest update, it looks like no matter what stl file I'm uploading into my account, it gets imported in cm, instead of my working units (mm), so 10 times bigger. The workaround is to create a brep after import and scale it down ten times, but it won't work with models with more than 10k polys.

Strange enough, the files uploaded prior to the current update (2.0.2016) import just fine.

 

0 Likes
5,785 Views
27 Replies
Replies (27)
Message 21 of 28

Anonymous
Not applicable

I meant meshmixer... I know import works.

 

"People know" is hardly documentation, or good practice for software engineers..

0 Likes
Message 22 of 28

Anonymous
Not applicable

Now in Technicolor...  First one is the cm/mm problem from opening from 'File'.  Second is the way people are telling you to open it.  Dimension in this video should be approx. 40mm not 398mm.

0 Likes
Message 23 of 28

dclaar
Participant
Participant

Thanks for the workaround!
7 years, and still no direct "open & specify units" 😞

I'd throw stones, but I work for a software company, and we have some of those "shouting into the void" bugs, too.

0 Likes
Message 24 of 28

TrippyLighting
Consultant
Consultant

The Insert->Mesh dialogue takes the same amount of clicks as the open file dialogue, but offers the ability to select a unit type.

 

TrippyLighting_0-1682766866085.png

 

That isn't a workaround, it's simply a different workflow.


EESignature

0 Likes
Message 25 of 28

dclaar
Participant
Participant

re: message 24 (warning, philosophy ahead😉😞


It's really not. According to message 3, insert looks like this:

1) open a blank model.

2) go into a Direct Modeling Environment. This can mean either create a sculpt, turn off the design history (right-click the top-level component in the browser tree and select "Do Not Capture Design History"), or Create a Base Feature. 

3) Insert Mesh. 

 

Where step 2 is a bit "magic-y".

 

Vs.

1) Open mesh.

 

To be fair, the magic-y step may not always be required, or required any more--I seemed to be able to skip it--but it's still just bad UX to have the most obvious path for a critical user journey only "kind of" work. It would be better for open to not work with STL at all, because that would drive people to the more full-featured import route, rather than communicating "Fusion doesn't handle this well".

 

But that's philosophy. I appreciate the answers here!

 

EDIT: I did reply "wrong", so it says that I'm replying to the OP, rather than message 24. 

0 Likes
Message 26 of 28

TheCADWhisperer
Consultant
Consultant

@dclaar 

Why are you doing your Step 2?

0 Likes
Message 27 of 28

laughingcreek
Mentor
Mentor

@dclaar - the instructions in message 3 are from 2016.  a lot has changed since then.  those steps are no longer relevant to the question.  bottom line- use "insert mesh" instead of "file/open".

0 Likes
Message 28 of 28

dclaar
Participant
Participant

Re: 26 ... and 27: Because when one tries to open a mesh in mm instead of cm, and there's no help to suggest insert, one does a web search, and this thread--which also has several "use the method in message 3" responses--comes up.

 

Bad UX leads to sub-optimal solutions, like relying on an answer from 2016.

 

Re 27: I know that now. But I'm only one of many who have to waste a lot of time--since 2016--trying to figure out "why open doesn't work", when either making open work the way it should (yes, should: The most common, straightforward path should be the best one), or by taking the ability to open .stl away to drive users to insert.

0 Likes