Problem with VERY SMALL offsets

[Anonymous]

Hi,

I just tried to offset a line in sketch by 0.05mm on the other-side of the original line from the initial indicated offset direction.

I.E. I selected the line to offset, then dragged the red offset line back across my original line and then typed in my offset.

I entered ".0" and the red line went back to overlap the original line - not a problem so far.

Then I typed in the "5" part of the offset, and the offset line moved away from the original - IN THE SAME DIRECTION AS THE ORIGINAL INDICATION.

Now I am pretty sure that this is not supposed to happen.

I got around this by typing in ".5" then clicking between the "." and the "5" and inserting a "0".

Please note that this is not a solution to the problem, it is just a way around it.

Any comments?

Regards,

Brett

[whittakerdw]

Ive had this issue as well. The only way I've seen to fix this is like you said by adding .5 then adding the 0. A few other ways I've done it is by typing -.05 for example without thinking and when the "-" is there it turns red so when I go back to correct it it stays on the desired side. Another way is by typing it faster than it takes for the program to register the .0 and automatically go back to the original line.

[mavigogun]

Ya, I've ran into something similar, too- in my case, at times, a value will not relocate relative to a new position unless it is first zeroed out; sometimes these dances back and forth become so disconnected from the original position I have to quit the operation to reset, start over.    It's almost like after the first value, the second value can become a fractional division of the first- and not the base units!    I should have documented it- but, you know, time.   Could you make a screencast?

[mbostonsprint]

I have also had similar issues with Offset; my opinion based on its behavior over some couple of years of periodic usage of Fusion 360 is that it seems to have some "limitations" in its performance. It does appear to me that data entry in the active box that shows up close to the site of the offset is often somehow delayed (for lack of a better term) in its recognition, and misses the first couple of characters of the dimension, especially where you might be entering "0.00xx" or something similar. I have seen many times that the offset command then operates using the first non-zero integer, which then offsets the feature by "miles", comparatively speaking. All this oddness is probably a symptom of some fundamental issue somewhere deep in the code, but the flakiness doesn't yet seem to be high-visibility.