Measure command returning angle not distance

[billSVWYG]

Perhaps during an update, Fusion 360 stopped returning distance values between faces of 2 unique components and now only returns angles.

[g-andresen · Accepted solution]

Hi,

Please share the file and say which faces are affected.

File > export > save as f3d on local drive  > attach it to the next post.

günther

[davebYYPCU]

Distance is only provided for parallel selections, 

if not parallel, which distance would you be happy with?

[billSVWYG]

The requested distance is from parallel surfaces. If done within the same object, it works. If initiated between 2 unique components, angles are returned. The model is confidential, so not able to share. Did just discover that if edge of one component is selected and the face of the other is selected, the correct distance is returned. Previously, both faces would yield the same result. Will use this as a work around for now.

[davebYYPCU]

So you know it’s not accurate, but you can fudge it.

Sounds like a plan.

[jhackney1972 · Accepted solution]

As you have been told, if the faces you are measuring between are not parallel, you will get an angle measure.  If does not matter if the two faces are from different components, if they are parallel, you will get a distance value.  The video will show this.  I have added the model I used for you to try it for yourself.

If you model is confidential, save out two of the components giving you an issue and attach them.

[billSVWYG]

In fact it is accurate.

[davebYYPCU]

Different selection, correct answer.  

Then what is the original question about, an upgrade?

I noticed some new icons in the Dialogue Box.

Only you know what you are seeing as a result of the selections you made.

[billSVWYG]

I consider it an honor to receive a response + video from you as your YouTube videos have helped me tremendously over the last 10 months.  Thank you.

In this case, the angle returned every time is 0 degrees.  I will attempt to reduce the example to a few key components that will illustrate the issue.

[davebYYPCU]

Then your misalignment is rounded down to Zero, show more decimal places,

but such a small value should not be ignored.

Might help.....

[billSVWYG]

Rounded to 0.00 degrees? And if alternate face is measured for an angle to same part, it yields 90 degrees. I may have tripped a setting somewhere along the way.

[davebYYPCU]

Nope, 0.005 degrees (out) will not provide a distance, until you make the selections parallel.

Might help....

[billSVWYG]

Nope. Even tried the align command to ensure faces are parallel. Still comes back with 0.00 degrees.

[davebYYPCU · Accepted solution]

What is the degree value to 6 or 8 decimal places?

[billSVWYG · Accepted solution]

It was 2 decimal places.  Went back again and re-aligned the respective faces and bingo, a distance is generated.  Thanks all for the persistence.  Now I need to determine why there are components that are not parallel relative to each other.  I never would have landed on this being the root cause of the issue without all of this feedback.

[davebYYPCU · Accepted solution]

Fusion Components are free to move until you prevent it.

Double check all the Capture positions (if any), inadvertent moves being captured is most likely culprit.

Ground, Joints are recommended to prevent inadvertent moves.

Might help.....

[billSVWYG]

Looks like I need to quickly learn how to orient components parallel to the origin planes without moving them to the plane.

[davebYYPCU]

Need a dummy file with examples of what you do when working in the file.

Offset planes from the Origin will always measure as distance.

Orthographic moves will always measure as distance.

One thing I forgot, fully defined sketches - a line that looks vertical but does not have the constraint could do it too.

Such small errors will usually break jointed Assemblies.

Might help.....