Newly opened drawing requires saving

[SRSDS]

Normally, a drawing won't require saving unless something has been modified.

My problem is that when the drawing contains a constrained dynamic block it does.

The DBMOD system variable (drawing modification status) should be 0, but for some reason it's not.

An asterix appears in the drawing tab, which is another indication.

Is this just a bug in  AutoCAD that I have to accept?

A simple constrained block in a drawing attached.

I'm running ACAD 2018. Could someone let me know if it has been fixed in a newer version?

[pendean]

Your R2018 startup(s) and perhaps even add-ons are the likely culprit, not your DWG file.

I can open and close your DWG file consistently and frequently without getting prompted to QSAVE here in an OOTB setup of AutoCAD2023.

[TheCADnoob · Accepted solution]

I got the asterisk intermittently.  

I changed the precision to just whole numbers and the issue seems to stop. Is there a reason you need such high precision?

[SRSDS]

Thank for your replies! I did think to uninstall any addons. Didn't think about startup(s) though, but just tried and that didn't help either.

Glad it's not just my system. Can you explain where to access the precision you are talking about? Whole numbers is fine. Only needs the nearest mm.

[TheCADnoob]

UNITS command. 

Generally at high precision things can get funky. That said the precision you have isn't too high, but its likely outside of significant digits for your objects. I'm just guessing that since the precision is higher than needed, the constraints might shift ever so slightly causing the issue. 

[cadffm]

---

@TheCADnoob  schrieb:

I changed the precision

One of the stupiest things I ever read, but you are right lol 😮 😂

>>"Is there a reason you need such high precision?"

Why using a display precision lower than the possible 8 ? (except because the (for me) really new information from this post)

---

@SRSDS 

>>" where to access the precision you are talking about? "

LUPREC - what is also reachable oby command UNITS (plain ACAD/LT)

>>"The DBMOD system variable (drawing modification status) should be 0, but for some reason it's not."

Not means WHAT value? I guess you are talking about value 1 instead 0!?

>>"Is this just a bug"

Yes. (and the precision dependency is another bug)

>>"in AutoCAD that I have to accept?

Yes (or if that is okay for you, see cadnoob and set luprec to 0 (what I would never use)

>>"I'm running ACAD 2018"

Without Tools on startup or similar, this is how AutoCAD works on my side with your drawing file (and your luprec>0):

Open the file: DBMOD is 0 as it should!

MARK(highlight) your blockreference..

At this point, or after de-selection by[ESC] for example, dbmod is set to 1

I would use a Tool for "close file without saving, no matter what dbmod is current"

but this is a tear maker too, pushed in the wrong moment&file

[SRSDS]

Thank you all. Took me a while just to find the culprit.

And I am impressed that solution was thought up.

[TheCADnoob]

---

@cadffm wrote:

---

@TheCADnoob  schrieb:

I changed the precision

One of the stupiest things I ever read, but you are right lol 😮 😂

---

If there is something stupid to be done, im your guy haha 😅

>>"Is there a reason you need such high precision?"

Why using a display precision lower than the possible 8 ? (except because the (for me) really new information from this post)

---

Its the same reason we distinguish between real and integer variable and longs etcs.  The right tool for the job. Computers aren't perfect and its better not to tempt fate when not necessary. There is no sense in using precision beyond the significant digits needed otherwise you bring in conditions that could impact calculations that would never be within the scale of the items being designed. ... all that said this is definitely one of those wtf moments haha.  My thinking is that perhaps the display may trigger a parametric recalculation and if the calculation goes from 100.00000001 to 100.00000000 its technically a change... but its all a guess haha. 

[TheCADnoob]

be mindful that your precision should be set to the items significant digits. So change that to what the designers are working with. you don't want to solve one problem by causing another. 

[cadffm]

---

@TheCADnoob  schrieb:

---

Its the same reason we distinguish between real and integer variable

---

But in my head Luprec is stored like documented from AutoDESK: It has nothing to do with the file content (except the storage of the system variable themself and fields which using the current precision).

And this it not "the same" like real&ints.

You really found a horrible connection there (many thanks).