Dim commande snapping to other extension lines

[Anonymous]

Hi there,

I'm not new to AutoCAD and I'm facing a strenge issue since 2019 update.

Since the new version 2019, when I work on paperspace the dimensions on Paper Space are no longer associated exclusively with the object drawn on the Model Space despite the fact that DIMASSOC variable = 2

Result: If an object drawn on the model Space is shown on the paper space (Mview) with a scale different from 1/1 then some dimansions are false (see image attached) using Dim, or Diml commande.

Explanation: the dim commande is snapping to the extension lines of other dimensions resulting in dimensions scaled to the paperSpace, when it should normally be associated with the model drawn on the ModelSpace.

Please take a look on the attached image for a better understanding of the issue.

Please tell me the solution if you know it? (for info, I have already explored  DIMASSOC, DIMSCALE, DIMLFAC etc. and everything is well setup)

Cheers.dim commande on paper space issue

[ian.mag]

Hey @Anonymous 

What items in your OSNAP setting are checked?

"..Result: If an object drawn on the model Space is shown on the paper space (Mview) with a scale different from 1/1 then some dimansions are false (see image attached) using Dim, or Diml commande..."

But this should be the case when you specify a different scale, since your drawing is scaled either way

---

[Anonymous]

Thanks for your quick answer, 

All my 2D objet snaps are ticked, but I've always worked this way and never had any problem with previous Autocad versions.

I would like to keep all my 2D osnaps ticked. 

Cheers 

[ian.mag]

Hey @Anonymous 

I would suggest you turn off all the snaps you don't require and keep them to a bare minimum like endpoint, node etc (when you are attempting to do this on the paper-space; you can always turn them back on when you switch to model)

Just to add on what I said earlier, the dimension on the paper space is as per the scale chosen. That would be the reason why your 3/4 scale gives 45 instead of 60, since 60 is the scale of 1/1. So I don't think there is a problem with that.

[Anonymous]

Hi @ian.mag ,

Thanks for your followup. Yes, I fully agree with you 

as I've always worked with all my Osnaps ticked and never had this issue before, I'm wondering why this problem appeared with my Installation of AutoCAD2019.

Indeed, a possible solution is to only tick the necessary 2D Osnaps.

But I'm trying to find a solution to keep all my Osnaps ticked and avoid this paperspace dimension issue  (in fact prefer not to change my work routines VS former versions of AutoCAD)

[ian.mag]

@Anonymous 

Was just thinking, a good work around maybe to save the current workspace and always switch to the one that has less snaps whenever you want to do your paper-space thing, and back to your original/preferred workspace. Ill leave that for you to decide though

[Anonymous]

Thanks @ian.mag 

Could be a solution also. 

I'm still looking to understand why this was working in previous versions ands not now with 2019.

Thanks again 🙂

[GrantsPirate]

Are you on plain AutoCAD 2019 or one of the verticals like 2019 Mechanical, etc?

Previously were you working in plain AutoCAD 2018 or one of the verticals like 20xx Mechanical, etc?

If you have always worked in plain AutoCAD then I can't give you a magic setting that will 'fix' this for you.  Running all Osnaps is something I never do, I rarely have any of them on preferring to call them when needed through temp overrides with a quick touch of a key or two.  

At a bare minimum stop picking on the actual end of a line because the dimension node also resides there, instead pick the line anywhere beyond the half way point.  Even that might not work since you have all the Osnaps on all the time.

[Anonymous]

Hi @GrantsPirate ,

thanks for your answer,

Unfortunatly I'm working with the plain educational version of AutoCAD as I'm a drafting teacher, and I've always been working with the plain version.

I agree and know I can select my Osnaps with a shift right click but the strenge thing I've noticed is that this issue is new to version 2019. I've always used all my Osnaps ticked in the past and never faced this problem.

On the other hand OSOPTIONS set to 7 or 4 so Osnaps should ignore extension lines,

It's like the variable OSOPTIONS is not working in AutoCAD 2019.

[GrantsPirate]

I get the same wrong dimensions in 2019, 2018, and 2001 (yes 2001 runs on my Win10 64 machine).  If I place two dimensions and then dimension between them I will get PS values, grabbing one dim and one endpoint in MS will give me MS values.

So I have confirmed on my end that previous versions also give the PS value under the sequence described by you and tested by me.  I still maintain having all Osnaps on at once is not a good idea, this illustrating my point for me.  Others may disagree but if I hired someone that did that they would have to unlearn that behavior (all Osnaps on) really quick. 

[Anonymous]

Hi @GrantsPirate 

Ok fine thanks for testing, you convinced me.

So there's something I could not figure. What is the variable OSOPTIONS = 4 or =7 used for ?

In my understanding, OSOPTIONS = 4 should force autocad (dim commande) to ignore extension lines on the PS to avoid such issues.

besides, I never found an explanation about OSOPTIONS=7.

[GrantsPirate]

From help and also Express Tools, System Variables,

Controls whether objects snaps are suppressed on hatch objects, geometry with negative Z values when using dynamic UCS, or dimension extension lines.

The setting is stored as a bitcode using the sum of the following values:

Value Description
0  Object snaps operate on patterned hatch objects, on geometry with negative Z values when using a dynamic UCS, and on endpoints of dimension extension lines.  A REGEN is required for snapping to hatch intersections after changing to this setting.  A REGEN is recommended for performance reasons after changing from this setting to a value that includes 1.
1  Object snaps ignore hatch objects.
2  Object snaps ignore geometry with negative Z values during use of a dynamic UCS. (Not available in AutoCAD LT.)
4  Object snaps ignore endpoints of dimension extension lines.

NOTE: In AutoCAD LT, the default value is 5.

The 4 bit will ignore the endpoints of dim ext lines but apparently only in a limited way, if at all, so I wouldn't try relying on it. 

Add the bitcodes together, 1+2+4=7.

[Anonymous]

Okay , I get the 7 now, many thanks @ian.mag 

So that's it : it seems OSOPTIONS=4 is not reliable. 

really strenge.

Thanks for the follow up