Offset Command Rounds Values on Second Enter

[l-schultz]

I enter the Offset command and key in a value of 58.25 inches.

I can then offset a line or polyline and it will do so with the correct value.

When I run the Offset command again without entering a value, it changes to 58 inches even.

It seems to occur randomly. Sometimes the 58.25 stays on subsequent command execution, other times it does not. No particular sequence to narrow it down.

Had 2014 previously and 2023 now. never had this on 2014.

?

[Kent1Cooper]

Is what you describe as the rounded value just a matter of your precision-in-display setting in Units?  I set the precision to 0 [all displayed values rounded to nearest whole number].  I started an Offset command, and gave it 1.234 for the distance, and Offset something.  I measured the distance between the original object and the Offset one, and it "showed" 1 unit, not 1.234, because of the displayed-precision setting.  And I recalled the Offset command, and the default value it offered was 1 unit, for the same reason.  But it really knows it's 1.234.  If I increase the precision in Units, the measured distance between those objects and the offered default value in Offset both show correctly at 1.234.

[Patchy]

LUPREC

type in 4 and see

[l-schultz]

That is not my case. I'm working in architectural units with a precision of 1/256". If I offset a line 58.25 inches and then offset the same line again and it reads 58 inches, then the second offset is .25 inches short of the first. I can measure using Dist command and see the first one offsetted is 58.25 and the second one is 58.

[Michiel.Valcke]

Can you provide a screencast of the issue and share the dwg. I for one cannot reproduce the issue in my installation.

[pendean]

@Anonymous Show us this DWG file with the very different DIST measurements due to OFFSET command auto-changing please, I am unable to replicate you issue in R2023.0.1 with no 3rd party add-ons in my own DWG files at all

[cadffm]

@Kent1Cooper 

"But it really knows it's 1.234"

That should be and it was in your Test with the right settings, yes - but not always

@l-schultz

see Patchys post and set LUPREC to 4 8 (why 4, if you can have 8 digits) and try it again 😉

Never had in 2014? That's coincidence of settings and workflow, because this bug is older than 2015, perhaps since the begin of dynamic input (I am not sure).

It is an old unsolved parlous bug in the program

1. a problem of dynmode only

2. depending of luprec, offset value and object location in wcs

    Everyone can reproduce it near to 0,0,0 and also far away from there.

Attached a sample, so we can talk about one conrete one, let us offset 50.58

and the second time we just confirm the 51 by enter

While dynmode off = no problem

while dynmode on and luprec is 1 or higher = no problem

we can move the objects to ~ >100000-999999,>100000-999999

while dynmode on and luprec is 2 or higher = no problem

while dynmode on and luprec is 1 or 0 = problem

EDIT: Forgot to attach the DWG

[l-schultz]

Working on deadlines, finally looked at the sample drawing.

First, LUPREC was already set to 8. That was default install value, I never changed it.

Your sample.dwg file worked for all values that I tried. Always displayed full decimal points to the right.

I took the drawing I was having issues with and deleted just about everything. Issue still shows up after entering offset value and then just hitting return once and then once again without entering a value.

Does not seem to matter if decimal or fraction is entered.

I even tried setting the units to architectural on your drawing and could not the get the rounded value issue to replicate.

See Offset_Issue.dwg attached.

[cadffm]

Hi,

1. >>"First, LUPREC was already set to 8. That was default install value, I never changed it."

    This is a file setting, stored per file.

2. >>"Your sample.dwg file worked for all values that I tried. Always displayed full decimal points to the right."

    I can't imagine or you are using a custom tool to change things in the background.

    If you open my file, you shouldn't see the 50.58 again by enter hit, because luprec is set to 0

3. >>"Does not seem to matter if decimal or fraction is entered."

    I took your last uploaded file and it does matter. I don't have a problem in DECIMAL length units.

4. >>>"I even tried setting the units to architectural on your drawing and could not the get the rounded value issue to replicate."

     I can reproduce it

 5.>>  "I can reproduce it also in my sample with architectural"

     I too, looks strange 😄

- - -

We can talk about a lot, but we can not change the program!

Send a bugreport to autodesk and don't use this workflow, that's all you we  users can do.

[cadffm]

2. >>"Your sample.dwg file worked for all values that I tried. Always displayed full decimal points to the right."

    I can't imagine or you are using a custom tool to change things in the background.

    If you open my file, you shouldn't see the 50.58 again by enter hit, because luprec is set to 0

3. >>"Does not seem to matter if decimal or fraction is entered."

    I took your last uploaded file and it does matter. I don't have a problem in DECIMAL length units.

4. >>>"I even tried setting the units to architectural on your drawing and could not the get the rounded value issue to replicate."

     I can reproduce it

 5.>>  "I can reproduce it also in my sample with architectural"

     I too, looks strange 😄

- - -

We can talk about a lot, but we can not change the program!

Send a bugreport to autodesk and don't use this workflow, that's all you we  users can do.