AutoCAD 2018.1.1 error with coordinate system

[Anonymous]

I can't use coordinates given with x and y or length + angle with any command (f.e. line, rectangle, move, copy and so on) since the latest upgrade!

When I press , or < the text boxes just disappear, so instead of being able to write the 'y' or angle parameter I'm "cut off".

Got around it with DYNMODE -3, but then I always have to write @ before my coordinates - a bit annoying when I have Relative coordinates set in DSETTINGS. And after DYNMODE set to -3 I also no longer see my entrys next to the cursor, only in the command line.

Any one else experiencing this? Or have a solution?

[pendean]

Can you post a video or a series or images to explain the exact nature of the problem?

[john.vellek]

Hi @Anonymous,

I see that you are visiting as a new member to the AutoCAD Architecture forum. Welcome to the Autodesk Community!

I have tried to duplicate this in core AutoCAD  and I am finding it behaves exactly as it did in 2017.

Please list your exact steps and expected display so I can try to duplicate on my side. A video would be helpful as well.

[Anonymous]

Posted some screenshots below 🙂

[dieters]

Hi Pernilla,

Thanks for posting this. The details as I understand them are

- The behavior of coordinate entry changed for you since the upgrade.

- You normally work with DYNMODE turned on (3).

- The problem occurs when you use a comma and < to delimit the values in your coordinates--the entry box disappears, preventing you from entering the next field.

The images you posted ended up here instead:

https://forums.autodesk.com/t5/autocad-forum/re-autocad-2018-1-1-error-with-coordinate-system/td-p/7...

Perhaps you can paste them here in your reply.

Questions that I have include

- What version of the Windows OS are you using?

- Have you specified a comma for the decimal delimiter (European standard)?

Thanks,

Dieter

[john.vellek · Accepted solution]

Hi @Anonymous,

This was resolved in your other thread. The answer to correct this was to make a change in your Dimension Input settings. Change the Pointer Input Setting for Visibility to "When a command asks for a point" and that will return the behavior to normal.

Please select the Accept as Solution button if my post solves your issue or answers your question.

[Victoria.Studley]

Thanks for following up over here, @john.vellek!

I've marked your post as the solution here, since it describes the solution you arrived at in the other thread.

@Anonymous, if you feel that this is not the solution and you need more help with the issue, please let us know and we'll be happy to unmark it and continue assisting you.