Drawing Dimensions over broken views (Break view) incorrect on edge extension

[b.affa]

Please be very careful when dimensioning broken views – if you pick an edge extension as one of your points and span over a broken view, the dimension will be wrong as seen in the image below.

The dimension value is equal to the actual scaled distance in the drawing, which is arbitrary.

It is very easy to miss especially if you do ordinate dimensions.

[jhackney1972]

I cannot replicate the issue you are pointing out.  I have attached my model, try it out in a drawing and see if you see the issue.  Also, please attach your model so I can do the same.  Open your model, select the File menu, then Export and save to your hard drive.  Attach it to a reply post using the attachment section.  Model is attached.

[-KyleWilliams-]

Hey @b.affa 
I've also tried to recreate your issue and don't seem to be having unexpected results.
This part is symmetrical and as you can see the extension side gives the same value as the non.

If you are able to share your drawing with the incorrect value we may be able to dig deeper to solve this.
You can send it directly to me kyle.williams@autodesk.com

[g.buckleyZPK86]

Hi Kyle,

  I can replicate the issue from b.affa - came across this recently.

It also does the same behavior for ordinate or normal dimensioning. You need to select the edge extension and dimension anything over a break view..

This also one seems to happen "some of the time".. re-do it a couple of times and you'll get some scaled dimensions.

Thanks,
Gareth

[b.affa]

Hi,
This bug applies on models with filleted (& possibly chamfered) corners that have the edge extension tool applied to the corner.

[jhackney1972]

Yes, you are correct.  The Edge Extensions DO cause the Broken View to dimension incorrectly.  The highlighted dimension should be 20.00.  Good catch!

@ClintBrown3D, Model and Drawing are attached.

[Pramod.kadam]

Hi All,

Thanks for reporting. This is known limitation. We have item logged in our backlog to enhance this. We will update you as soon as this gets prioritised.

Regards,

[saso_grinaver]

Maybe it's time to fix this now?
I mean it's basic tool and we need this...

Thanks...

[CGBenner]

@RajkumarIlanchelian has there been any update on this?

[Pramod.kadam]

Hi All,

Unfortunately, This is not fixed yet. The problem little complex than expected, we will update you as soon as we plan this. 

Thanks,