Topic: Demonstrable Bugs and Deficiencies List ( AutoCAD )

[Kerry]

I've noticed a lot of vent type posts here and elsewhere about AutoDesk not fixing bugs from previous versions when they release a new version.

I'm proposing a 

Demonstrable Bugs and Deficiencies ( AutoCAD ) List

keep to the facts, no vitreol or whinging.

I'll see what can be done about getting this list in front of someone at AutoDesk who may care.

[Keith™]

Version: AutoCAD 2008-2009
Item: Attributes
Issue:
Rotation of attributed blocks programmatically causes the attributes' rotation to behave erratically.
Rotation of attributed blocks in property window causes the attributes' rotation to behave erratically.
Note:
Rotating via the rotate command behaves as expected.

[Kate M]

I'll see what can be done about getting this list in front of someone at Autodesk who may care.

Ready and waiting...

Seriously, if you guys want to start a bug list, I'll happily follow along. I can make no promises/guarantees/speculations on what may or may not get fixed in a future release, but I (we) am listening.

If you have a bug to post:

1. Describe clearly, step-by-step, the commands/procedure that results in the bug.
  1.a. If you can't reproduce it, or at least remember exactly what you did to cause it, please don't post it until you can complete step 1.
  1.b. Include hardware details if you think it might be related. OS especially.
2. Provide screenshots if appropriate.

[Kate M]

Version: AutoCAD 2008-2009
Item: Attributes
Issue:
Rotation of attributed blocks programmatically causes the attributes' rotation to behave erratically.
Rotation of attributed blocks in property window causes the attributes' rotation to behave erratically.
Note:
Rotating via the rotate command behaves as expected.

Keith, can you define "erratically"? Before/after screenshots?

[Josh Nieman]

Excellent commendable idea, Daron.  I'll be sure to try and nail down my issues more empirically, and hopefully more reproducibly.  One of the hard things is the old "hang up when selecting hatch boundary" that is so elusive, but obviously present... that it's hard to definitively nail down!

[Kate M]

Excellent commendable idea, Daron.

Who?

[Mark]

Great idea Kerry!

[Keith™]

Version: AutoCAD 2008-2009
Item: Attributes
Issue:
Rotation of attributed blocks programmatically causes the attributes' rotation to behave erratically.
Rotation of attributed blocks in property window causes the attributes' rotation to behave erratically.
Note:
Rotating via the rotate command behaves as expected.

Keith, can you define "erratically"? Before/after screenshots?

Kate, this is the link where I posted all of the information I was able to gather on the issue. In that same thread is a drawing where the issue is shown exhibited. This does not affect pre-2008 versions and preliminary tests indicate it affects 2009 as well as 2008.
If you need anything else, let me know

[Guest]

Excellent commendable idea, Daron.

Who?

So it ISN'T just me, then.  *phew*  That's good to know!

[whdjr]

Nah,...it's just Josh....what more can we say.   

[Josh Nieman]

I'm sorry Kerry!

I was reading multiple threads at once, and got my wires crossed!!

[Krushert]

Version: AutoCAD 2008-2009
Item: Attributes
Issue:
Rotation of attributed blocks programmatically causes the attributes' rotation to behave erratically.
Rotation of attributed blocks in property window causes the attributes' rotation to behave erratically.
Note:
Rotating via the rotate command behaves as expected.

Keith, can you define "erratically"? Before/after screenshots?

Kate, this is the link where I posted all of the information I was able to gather on the issue. In that same thread is a drawing where the issue is shown exhibited. This does not affect pre-2008 versions and preliminary tests indicate it affects 2009 as well as 2008.
If you need anything else, let me know

and here is the link for the rotation using the properties pallet.

[craigr]

I'll see what can be done about getting this list in front of someone at Autodesk who may care.

Ready and waiting...

Seriously, if you guys want to start a bug list, I'll happily follow along. I can make no promises/guarantees/speculations on what may or may not get fixed in a future release, but I (we) am listening.

If you have a bug to post:

1. Describe clearly, step-by-step, the commands/procedure that results in the bug.
  1.a. If you can't reproduce it, or at least remember exactly what you did to cause it, please don't post it until you can complete step 1.
  1.b. Include hardware details if you think it might be related. OS especially.
2. Provide screenshots if appropriate.

There really isn't a procedure to this one, but...

The Export AutoCAD 2008 Settings doesn't work after a couple of uses. You start the program and the Admigrator.exe program appears in the MS Windows Task Mangager, but doesn't go any further. You eventually have to use the Task Manager to shut it down. While it is trying to run, in the Task Manager it shows CPU at 50 & Memory Usage at 18,112.

I tried the full uninstall & reload, didn't help. I tried the modify suggested by Autodesk, didn't help.

Intel dual Core, 2.4hz, 2gb RAM, MS Windows XP Pro w/Service Pack 2, AutoCAD LT2008 w/Service Pack.

This has happened on several of our workstations. Too bad it isn't stable, it was great when it worked.

craigr

[Bryco]

This bug has continued into 2009.
Slicing a solid with 3 points works in any ucs, whereas slicing a solid using a circle when the ucs is not world doesn't work and gives the bogus  message "Slicing plane does not intersect the selected solid"  as shown below


Select objects to slice:
Specify start point of slicing plane or [planar
Object/Surface/Zaxis/View/XY/YZ/ZX/3points] <3points>: o
Select a circle, ellipse, arc, 2D-spline, 2D-polyline to define the slicing
plane:
Specify a point on desired side or [keep Both sides] <Both>:

Slicing plane does not intersect the selected solid.

[Josh Nieman]

I also despise that when invoking slice, the default is 3points;

Select objects to slice:
Specify start point of slicing plane or [planar
Object/Surface/Zaxis/View/XY/YZ/ZX/3points] <3points>:

but in all actuality, it defaults to the 2 points function.  IT LIES!