[Lionclaw]

I recently began using autocad 2006, and it's doing some quirky things I didn't notice with 2005.

Sometimes when i go to type in a number with a decimal, the decimal doesn't show up until I hit it again. But then I have 2 decimals. For example, I'll type "offset" then ".125", but I get "125" instead.

When I go to create a circle I type "circle", then the origin "0,0". But when I go to type the diameter or radius, it has placed an "e" in the command box. What's with the "e"?

Any help would be appreciated. These aren't show stoppers, but can get a bit annoying.

[ger21]

You didn't mention the WORST thing about 2006. When I want to move an object, I click the basepoint, and say I want to move it to 0,0. I used to be able to just type 0,0 but now have to type #0,0.

I tried to recreate what you're seeing, but don't realy want to mess with the settings that took me a few days to fine tune.

A quick search on the AutopCAD 2006 discussion group says that the dynamic input is a little slow to react, and I'm guessing that's the problem. One option is to turn it off.

A little more reading, and it seems that the dynamic input is definately the culprit. And it seems the only fix is to turn it off. Not sure if it's related to PC speed, but I haven't noticed it on my shiny new dual core Athlon.

[ger21]

Btw, why type "offset" ? I just type "o".

You might want to look at doing some customization to change the way you work. (Although I wouldn't change if someone suggested it).

I use a single toolbar, with a couple simple flyouts. I only type a handful of commands. And I've added quite a few to my right-click menu.

[CNCRob]

You didn't mention the WORST thing about 2006. When I want to move an object, I click the basepoint, and say I want to move it to 0,0. I used to be able to just type 0,0 but now have to type #0,0.

I tried to recreate what you're seeing, but don't realy want to mess with the settings that took me a few days to fine tune.

A quick search on the AutopCAD 2006 discussion group says that the dynamic input is a little slow to react, and I'm guessing that's the problem. One option is to turn it off.

A little more reading, and it seems that the dynamic input is definately the culprit. And it seems the only fix is to turn it off. Not sure if it's related to PC speed, but I haven't noticed it on my shiny new dual core Athlon.

Im glad you pointed that out. I have been having trouble moving objects also, I went back to 2005 for that very reason.

[Lionclaw]

Thanks Gerry. I had dynamic input off, but I guess the problem was somehow related to typing the entire word. I never had that problem with 2005. Just typing "L" or "O" now and no problems.

[JoelDirn]

You didn't mention the WORST thing about 2006. When I want to move an object, I click the basepoint, and say I want to move it to 0,0. I used to be able to just type 0,0 but now have to type #0,0.

You can change back to absolute input without the # by turning Dynamic Input off. Then it goes back to needing to use the @ for relative input.

- Joel -

[joecnc2006]

Anyone get their 2007 yet? I have two of the packages so far and should recieve Civil3d on monday, so will be using it next week.

[ger21]

Not yet, but hopefully soon. Looking forward to the new 3D stuff.