How to prevent decimals from jumping back to 3

[marcel.vandenoosterkamp]

I have a d5 command that changes both unit and angle decimals to 5. I also have d2, d4 and d8 and it worked like a charm for 25+ years. Now however autocad seems to know what's best for me and it keeps going back to 3 and 2 for angles. How can I stop that unwanted autocorrect feature?

[pendean]

D5 command? What's that please?

Are you asking about this by chance (it's been around for some time now) or something else

https://autodesk.blogs.com/between_the_lines/2013/07/autocad-tip-disable-or-delay-autocomplete.html

[cadffm]

Hi,

there is nothing in plain autocad what's changing luprec and auprec.

It's storing in in drawing files.

If it happen, there must be an custom command/function what forces this.

[marcel.vandenoosterkamp]

d5 and d8 are these

(defun c:d5 (/) (command "-units" "2" "5" "1" "5" "0" "n" "GRAPHSCR"))
(defun c:d8 (/) (command "-units" "2" "8" "1" "8" "0" "n" "GRAPHSCR"))

d0-d4 I made as well

freaking insane, that absurd feature seems to be gone now. I thought it was gone few days ago already but it came back today. Now after a restart it's gone again. Can't wait for tomorrow lol.

No new or weird lisps are loaded. When it's there I can set 5 dec places, stretch an object and literally check just before I left click the destination point the decimals on the bottom of the screen and see it's still at 5 and after the leftclick see it jump to 3. Totally insane lol

[apjones]

Those strings there are lisp definitions.  If they are not working, they are not loading.  You need to determine how they are loaded and why they are not loading.

[vandenoosterkamp]

And it's back again. After I opened a template with all kinds of blocks / dimstyles leaders etc that I use a lot.

I added luprec and auprec to the, imo completely useless timewasting invention called sysvarmonitor and see that those have preferred values. I have no idea where those come from nor why we need that anyway.

so here we go... strect a rectangle

and after i lefclick:

it jumps back to 3 decimals and tells me that there are now less sysvar's with unpreferred values.

So just stretching something makes that happen.

I normally have that sysvar switched off btw because I think it's completely useless and just a sad result of the neverending horendous need of Autodesk to pile up more unwanted features

[vandenoosterkamp]

I'm pretty sure it's caused by this thicked option wich, I guess, only takes effect AFTER you closed and reloaded the dwg.

New features. Keep 'm coming please Autodesk and don't bother if they work or we need them.

[pendean]

---

@vandenoosterkamp wrote:

I'm pretty sure it's caused by this thicked option..

---

This is not the C3D forum: and you seem to be running an older year version: where is that setting in plain AutoCAD please (topic of this forum)

[pendean]

Why not make this much taller so we can see what else is going on please

[cadffm]

too late again, but it was already wrote:

Hi,

>>"I added luprec and auprec to the, imo completely useless timewasting invention called sysvarmonitor"
If you don't want to monitor a sysvar, turn it off (I know, that is what you do for usual)
and it waste zero seconds anymore.
!?

>>"and see that those have preferred values"
>>"I have no idea where those come from"
Beside the listed sample variables of a standard installation, YOU set the default value.
If you add a variable to the list, the default value is the current one of this moment, but you can set it different.

>>"nor why we need that anyway."
Because of two things
1. If you can't remember your favorite value, you see it directly, but there is one more reason:
2. one option of sysvarmonitor is, you can set all variables to your favorite value by one click [Reset all]

-

Note your picture showing that you don't talk about Autocad (what we discuss here, in the AutoCAD board. C3D is the next door with a dedicated board)
It's always good to inform the community about the used software, Productname and Version!
Share your detailed Productversion of AutoCAD and Civil3D, command: ABOUT

>>"it jumps back to 3 decimals and tells me that there are now less sysvar's with unpreferred values."
>>"So just stretching something makes that happen.

>>"I'm pretty sure it's caused by this thicked option
AECDWGSETUP incl. automatism which are not in AutoCAD (I am familiar with ACAD, not with C3D)

(I was not able to reproduce this issue by grip-stretch option, I tried it with a closed polyline from command rectang)

[vandenoosterkamp]

I'm sorry for spamming the autocad section. To me it seems it has nothing to do with C3D.

The utmost bizar part is that it randomly is doing that correcting.Just now it junped back. I close the program, restart it, load the dwg that the issue and now it stopped doing it.

lol, in the meantime I get spammend by my vendor that they offer assistance for 600 a year to save me from losing time on issues.

I guess reinstalling AGAIN is the only option? I had unexplanable issues few months ago also that were gone after a reinstall. For some reason this expensive software (lol that for my single use is paid twice) needs half a day now and then for a reinstall. It's getting worse and worse!!!!

Insane issues just keep coming. It's their policy. If you nag hard enough about insane stuff they give you half a year free subscription. Should I start spamming them again directly and never pay for this software again? The insane issues simply never stop and just learn to live with it seems to be the preferred system value for everyone.

Trying to find solutions usually is also just a waste of time.

And autodesk employees do not read here. They just promote more new stuff roflol

@vandenoosterkamp - this post has been edited due to Community Rules & Etiquette violation.

[TomBeauford]

The fact that all AutoCAD products are all built to be easily customized is it's greatest feature to most of us.

You need to understand any modification to system variables that isn't reset to the previous value in your code affects other command results afterwards.

Most of the code I use is loaded as needed the first time it's used in a Ribbon macro or entered at the command line making debugging issues easier to spot when they happen.

Remember some system variables are saved in the Windows Registry, some are saved in the drawing and others aren't saved and must be set every time you use AutoCAD. 

Avoid using system variables or AutoCAD command names as variables or commands in your code. Before defining a command name in your code enter it on the command line to see if it's already defined as a command name by code already loaded.

Most importantly understand if you've customized AutoCAD and something no longer works the way it did before lots of people here are willing to help but only you can fix what you've done.

We've all been there (I know I have many times) and have found ways to get through it.

I use acad.lsp for loading a little code that loads with each AutoCAD session and acaddoc.lsp for loading any code the loads in each drawing as they're opened. Should either cause an issue I cannot figure out right away placing ;| before a section of code and |; after the last line of that section of code comments it out so it doesn't load. Then restart AutoCAD and see if that helped. If not try another section to see if that helped. Testing with the first half, then the second  will either narrow down where I caused an issue or let me know it's something else maybe loaded in the other lsp file or a mnl (menu lisp) file I've added or modified. The more code you have loaded when a drawing is opened the more you have to debug so having code that only loads when you use it the easier it will be to find and fix any issues you have.

Also since you mentioned Civil 3D keep in mind there's 13 lisp functions added in Civil.mnl whose command names you need to avoid using in any of your code.

[vandenoosterkamp]

---

@TomBeauford wrote:

We've all been there (I know I have many times) and have found ways to get through it.

I use acad.lsp for loading a little code that loads with each AutoCAD session and acaddoc.lsp for loading any code the loads in each drawing as they're opened.

I found a way around things as well. Always. I have invented literally hundreds of workarounds for slow default behaviour and my startup lisp is past 1000 lines now and it keeps growing. By now I spend more than a full working day on trying to find out how to disable this unwanted feature and I simply give up because that's better for my blood pressure.

I also think I know the answer because it must be the same as the one time I got half a year subscription for free from Autodesk and the reason must be that it has to do with a Windows update. I never had this insane issue before and next to R2022 I also still have 2020 and 2018 running and I cannot reproduce this in 2018 but I can in 2020.

The most worrying part on all of this is that there must be thousands out there that have the same issue but they do not care if stuff is drawn exactly right or not. I see those dwg's all the time, max 5% is flawless and that percentage is decreasing rapidly over the years.

[TomBeauford]

Does you code make use of AutoCAD commands and system variables? Look in Help for "Updated AutoCAD Commands and System Variables Reference" for changes made in them between the 2018 and 2020 versions. Huge changes were made in 2020 when the Blocks palette was introduced and the insert command was changed completely. Took a moment for many of us to adjust but useful commands like
-INSERTCONTENT added in 2023 more than made up for it.