Announcements
IMPORTANT. Forum in Read Only mode. You can no longer submit new questions or replies. Please read this message for details
Autodesk Architectural Desktop 2007 & Prior
Welcome to Autodesk’s Autodesk Architectural Desktop 2007 & Prior Forums. Share your knowledge, ask questions, and explore popular Autodesk Architectural Desktop 2007 & Prior topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Autodesk: ADT 2006 detail hatching vs ADT 2005?

13 REPLIES 13
Reply
Message 1 of 14
Anonymous
380 Views, 13 Replies

Autodesk: ADT 2006 detail hatching vs ADT 2005?

One of the things I really liked in changes to ADT 2005 details was that
certain hatches like plywood and rigid insulation were consistent with the
insertion point of the component being drawn - the base point of the hatch
was the corner of the component drawn regardless of placement or angle of
the component. 2" rigid insulation was ALWAYS 6 even hatch cells wide - no
partial hatch cells.

For some reason with ADT 2006 seems to have regressed with this and the
hatching of plywood and rigid insulation is based on a common basepoint for
the drawing and not set with the individual component. WHY DID THIS CHANGE?
Is there a way to get the ADT 2005 detail hatching feature back??
13 REPLIES 13
Message 2 of 14
Anonymous
in reply to: Anonymous

Gary Whitehill wrote:
> One of the things I really liked in changes to ADT 2005 details was that
> certain hatches like plywood and rigid insulation were consistent with the
> insertion point of the component being drawn - the base point of the hatch
> was the corner of the component drawn regardless of placement or angle of
> the component. 2" rigid insulation was ALWAYS 6 even hatch cells wide - no
> partial hatch cells.
>
> For some reason with ADT 2006 seems to have regressed with this and the
> hatching of plywood and rigid insulation is based on a common basepoint for
> the drawing and not set with the individual component. WHY DID THIS CHANGE?
> Is there a way to get the ADT 2005 detail hatching feature back??


I can verify this:
This is a horrible oversight on autodesk's part. Arbitrary hatches set
to global is a big goof guys, and defeats some of the points to use the DCM.

What's the fix autodesk?

--
David Kurtz
Peckham & Wright Architects, Inc.
Columbia, Missouri
Message 3 of 14
Anonymous
in reply to: Anonymous

The hatches do follow the slope of non-orthogonal components but with ADT
2005 if you placed two 2" rigid insulations 1/16" apart vertically and
horizontally the hatches would be offset the same. With my ADT2006 the
hatches come in one exactly over the top of the other (same origin) except
the hatch is cutoff or extended to the respective different boundaries.


"David Kurtz" wrote in message
news:4887524@discussion.autodesk.com...
Gary Whitehill wrote:
> One of the things I really liked in changes to ADT 2005 details was that
> certain hatches like plywood and rigid insulation were consistent with the
> insertion point of the component being drawn - the base point of the hatch
> was the corner of the component drawn regardless of placement or angle of
> the component. 2" rigid insulation was ALWAYS 6 even hatch cells wide -
no
> partial hatch cells.
>
> For some reason with ADT 2006 seems to have regressed with this and the
> hatching of plywood and rigid insulation is based on a common basepoint
for
> the drawing and not set with the individual component. WHY DID THIS
CHANGE?
> Is there a way to get the ADT 2005 detail hatching feature back??


I can verify this:
This is a horrible oversight on autodesk's part. Arbitrary hatches set
to global is a big goof guys, and defeats some of the points to use the DCM.

What's the fix autodesk?

--
David Kurtz
Peckham & Wright Architects, Inc.
Columbia, Missouri
Message 4 of 14
Anonymous
in reply to: Anonymous

Gary Whitehill wrote:
> The hatches do follow the slope of non-orthogonal components but with ADT
> 2005 if you placed two 2" rigid insulations 1/16" apart vertically and
> horizontally the hatches would be offset the same. With my ADT2006 the
> hatches come in one exactly over the top of the other (same origin) except
> the hatch is cutoff or extended to the respective different boundaries.

I don't have 2005 on this computer any longer so I can't see the
difference without going to another workstation.

I've opened a support request though our subscription account. They are
looking into the issue and getting back to me.

I'm a bit saddened with this big, it's an important feature of the DCM.
Hopefully there may be a fix via the XML or MDB file or registry
setting. Cross yer fingers. 🙂


--
David Kurtz
Peckham & Wright Architects, Inc.
Columbia, Missouri
Message 5 of 14
Anonymous
in reply to: Anonymous

Gary Whitehill wrote:

> For some reason with ADT 2006 seems to have regressed with this and the
> hatching of plywood and rigid insulation is based on a common basepoint for
> the drawing and not set with the individual component. WHY DID THIS CHANGE?
> Is there a way to get the ADT 2005 detail hatching feature back??


This is now a confirmed regression and they will not be fixing it for
free. We as customers are expected to purchase new versions to fix old
bugs.

I encourage you to write autodesk and let them know is is not acceptable
behavior for the price we pay. I am very disappointed at where ADT
development is heading if simple bugs won't be addressed. I very much
understand development, I code myself, and I am getting increasingly
frustrated at the number of little bugs in ADT that is making it look
rather sloppy and rushed.

Below is a cut and paste from my support request. I suppose the "good
news" is that they are at least planning one Service Pack. Perhaps if I
can report enough bug's they'll do 2 and we can get this addressed.

...and companies wonder why open source is getting so popular, I don't
care about free-as-in-money. I need to be able to fix the mistakes their
bean-counter's won't let them address.


> Dear David,
>
> I received an update from the development team on this issue. It has been confirmed as a defect and a regression from Architectural Desktop 2005.
>
> Unfortunately, it was discovered to late to be included in the upcoming Service Pack, but it has been linked to be fixed on the new release of Architectural Desktop.
>
> Please accept our most sincere apologies for the inconvenience, and thank you very much for identifying the problem.


--
David Kurtz
Peckham & Wright Architects, Inc.
Columbia, Missouri
Message 6 of 14
Anonymous
in reply to: Anonymous

Hi Gary,

Sorry for the trouble and here are two workarounds for you.

- Select the offending hatch > right click > Set Origin > Pick origin point
for hatch & you're done
- Another approach is to double click the hatch > select 'Click to set new
origin' in the Hatch Edit dialog > Pick your origin point & OK out of the
dialog to complete the process.

Dennis

--
Dennis McNeal, AIA
Autodesk BSD
"Gary Whitehill" wrote in message
news:4886873@discussion.autodesk.com...
One of the things I really liked in changes to ADT 2005 details was that
certain hatches like plywood and rigid insulation were consistent with the
insertion point of the component being drawn - the base point of the hatch
was the corner of the component drawn regardless of placement or angle of
the component. 2" rigid insulation was ALWAYS 6 even hatch cells wide - no
partial hatch cells.

For some reason with ADT 2006 seems to have regressed with this and the
hatching of plywood and rigid insulation is based on a common basepoint for
the drawing and not set with the individual component. WHY DID THIS CHANGE?
Is there a way to get the ADT 2005 detail hatching feature back??
Message 7 of 14
Anonymous
in reply to: Anonymous

Thanks for the reply, Dennis and especially David. I was hoping this was
not the case. I don't understand how something that worked fine in 2005
does not in 2006 - seems like the code for the insertion routine was
changed. yeah we can go through the pain of resetting all the origins but
we should not have to do that! - It's all your fault, Dennis - Ha!

Thanks again David and Dennis. at least now I know where I stand.

; "AIA - [Autodesk BSD]"
wrote in message news:4888950@discussion.autodesk.com...
Hi Gary,

Sorry for the trouble and here are two workarounds for you.

- Select the offending hatch > right click > Set Origin > Pick origin point
for hatch & you're done
- Another approach is to double click the hatch > select 'Click to set new
origin' in the Hatch Edit dialog > Pick your origin point & OK out of the
dialog to complete the process.

Dennis

--
Dennis McNeal, AIA
Autodesk BSD
"Gary Whitehill" wrote in message
news:4886873@discussion.autodesk.com...
One of the things I really liked in changes to ADT 2005 details was that
certain hatches like plywood and rigid insulation were consistent with the
insertion point of the component being drawn - the base point of the hatch
was the corner of the component drawn regardless of placement or angle of
the component. 2" rigid insulation was ALWAYS 6 even hatch cells wide - no
partial hatch cells.

For some reason with ADT 2006 seems to have regressed with this and the
hatching of plywood and rigid insulation is based on a common basepoint for
the drawing and not set with the individual component. WHY DID THIS CHANGE?
Is there a way to get the ADT 2005 detail hatching feature back??
Message 8 of 14
Anonymous
in reply to: Anonymous

Dennis McNeal wrote:
> Hi Gary,
>
> Sorry for the trouble and here are two workarounds for you.
>
> - Select the offending hatch > right click > Set Origin > Pick origin point
> for hatch & you're done
> - Another approach is to double click the hatch > select 'Click to set new
> origin' in the Hatch Edit dialog > Pick your origin point & OK out of the
> dialog to complete the process.

Hi Dennis:
Thanks for the input. I was aware that I could set the basepoint of the
hatch after the fact but I don't consider it much help...I use the DCM
so I *DON'T* have to do this for every hatch - that's the whole point!

I'm aware that if autodesk finds a "work around" that bugs are lowered
in severity in autodesk's eyes; but this does nothing to help the users
that paid good money for a product that doesn't perform as advertised.

Sorry, this is not directed at you; you're a valuable asset in this
group. I'm just getting frustrated at the falling QA level in ADT.


--
David Kurtz
Peckham & Wright Architects, Inc.
Columbia, Missouri
Message 9 of 14
Anonymous
in reply to: Anonymous

Gary Whitehill wrote:
> Thanks for the reply, Dennis and especially David. I was hoping this was
> not the case. I don't understand how something that worked fine in 2005
> does not in 2006 - seems like the code for the insertion routine was
> changed. yeah we can go through the pain of resetting all the origins but
> we should not have to do that! - It's all your fault, Dennis - Ha!

The problem is most likely poor regression testing and perhaps an
over-reliance on unpaid beta testers to report bugs. No doubt this was
introduced as they rework the DCM routine to add "edit" features, which
was a great addition, but the bug is a troublesome additional "feature".

> Thanks again David and Dennis. at least now I know where I stand.

Your welcome. Let me know if you find anything else. I plan to leverage
our expensive subscription account for all it's worth to get some timely
answers as much as possible now.


--
David Kurtz
Peckham & Wright Architects, Inc.
Columbia, Missouri
Message 10 of 14
Anonymous
in reply to: Anonymous

Actually, the code for determining the Hatch origin was changed in AutoCAD
so users would have more control over it. The Details code was supposed to
react accordingly and something slipped through the cracks.

I'm not making excuses, it shouldn't have regressed. But I do want to point
out that the QA team does a fantastic job. Any large program, such as ADT,
is a combination of hundreds of libraries of code from many different groups
and companies. Changes to the underlying OS, hardware, graphics drivers,
and in this case, base platform, create an enormous number of variables to
track.

We apologize for the inconvenience, and we'll get it fixed as soon as
possible.

Jim Awe
Autodesk, Inc.

"David Kurtz" wrote in message
news:4889091@discussion.autodesk.com...
Gary Whitehill wrote:
> Thanks for the reply, Dennis and especially David. I was hoping this was
> not the case. I don't understand how something that worked fine in 2005
> does not in 2006 - seems like the code for the insertion routine was
> changed. yeah we can go through the pain of resetting all the origins but
> we should not have to do that! - It's all your fault, Dennis - Ha!

The problem is most likely poor regression testing and perhaps an
over-reliance on unpaid beta testers to report bugs. No doubt this was
introduced as they rework the DCM routine to add "edit" features, which
was a great addition, but the bug is a troublesome additional "feature".

> Thanks again David and Dennis. at least now I know where I stand.

Your welcome. Let me know if you find anything else. I plan to leverage
our expensive subscription account for all it's worth to get some timely
answers as much as possible now.


--
David Kurtz
Peckham & Wright Architects, Inc.
Columbia, Missouri
Message 11 of 14
Anonymous
in reply to: Anonymous

Hi David,

Just so you know, we don't lower the severity of bugs because a workaround
exists. We try very hard to limit bug fixes in a service pack to assure
quality. We base service pack fixes on severity, risk and things like
dependency on AutoCAD.

Every bug fixed introduces the possibility of new bugs. Since development
and testing for a service pack is shorter than a release, we have a much
higher chance of seeing a regression. I'm sure you wouldn't be pleased if a
hatch fix broke wall display, or something like that.

Again, I'm sorry for the inconvenience.

Dennis

--
Dennis McNeal, AIA
Autodesk BSD

"David Kurtz" wrote in message
news:4889087@discussion.autodesk.com...
Dennis McNeal wrote:
> Hi Gary,
>
> Sorry for the trouble and here are two workarounds for you.
>
> - Select the offending hatch > right click > Set Origin > Pick origin
> point
> for hatch & you're done
> - Another approach is to double click the hatch > select 'Click to set new
> origin' in the Hatch Edit dialog > Pick your origin point & OK out of the
> dialog to complete the process.

Hi Dennis:
Thanks for the input. I was aware that I could set the basepoint of the
hatch after the fact but I don't consider it much help...I use the DCM
so I *DON'T* have to do this for every hatch - that's the whole point!

I'm aware that if autodesk finds a "work around" that bugs are lowered
in severity in autodesk's eyes; but this does nothing to help the users
that paid good money for a product that doesn't perform as advertised.

Sorry, this is not directed at you; you're a valuable asset in this
group. I'm just getting frustrated at the falling QA level in ADT.


--
David Kurtz
Peckham & Wright Architects, Inc.
Columbia, Missouri
Message 12 of 14
phildlight
in reply to: Anonymous

I'm not making excuses, it shouldn't have regressed. But I do want to point
out that the QA team does a fantastic job. Any large program, such as ADT,
is a combination of hundreds of libraries of code from many different groups
and companies. Changes to the underlying OS, hardware, graphics drivers,
and in this case, base platform, create an enormous number of variables to
track.



WHICH IS EXACTLY WHY YOU SHOULD TEST THE SOFTWARE WELL BEFORE YOU SHIP IT. MAKE SURE THINGS DON'T SLIP THROUGH THE CRACKS, AND DON'T SEND IT OUT UNTIL IT'S FIXED.
Message 13 of 14
Anonymous
in reply to: Anonymous

Jim Awe wrote:
> Actually, the code for determining the Hatch origin was changed in AutoCAD
> so users would have more control over it. The Details code was supposed to
> react accordingly and something slipped through the cracks.

My mistake, thanks for the clarification. Sometimes just letting
customers know the what/why can make explaining a bug much easier to
their managers. I caught a lot of heat over this one as I push DCM usage
and was allowed to do beta testing last year on the company dime. To be
fair, I didn't catch it then either.

> I'm not making excuses, it shouldn't have regressed. But I do want to point
> out that the QA team does a fantastic job. Any large program, such as ADT,
> is a combination of hundreds of libraries of code from many different groups
> and companies. Changes to the underlying OS, hardware, graphics drivers,
> and in this case, base platform, create an enormous number of variables to
> track.

I really do understand the complexities involved and have sympathies to
the developers. I've programmed since I was 12 (33 now) and live
knee-deep in code on 4 flavors GNU/Linux platform to work majik on our
servers. In the process, I contribute bug reports to hundreds of
applications; so it's no surprise to me that bugs slip through...
Perhaps the yearly release schedule is compromising the time to find the
bugs?

My boss' just don't understand the lack of monthly patches (like
Microsoft issues) especially because we annually pay autodesk the most
money of *any* supplier, software or otherwise.

> We apologize for the inconvenience, and we'll get it fixed as soon as
> possible.

Thanks for the post and I apologize for my out-spoken critique. I
realize this bug is no show stopper; I'm just frustrated it's there as
we now rely heavily on the DCM over the custom routines I used to write.
I hope my subscription contact was incorrect in saying that it would not
be fixed until the next release; ten months of resetting the basepoint
is a long time...



--
David Kurtz
Peckham & Wright Architects, Inc.
Columbia, Missouri
Message 14 of 14
Anonymous
in reply to: Anonymous

Dennis McNeal wrote:
> Hi David,
>
> Just so you know, we don't lower the severity of bugs because a workaround
> exists. We try very hard to limit bug fixes in a service pack to assure
> quality. We base service pack fixes on severity, risk and things like
> dependency on AutoCAD.

My apologies, I was misinformed then. Serves me right to listen to a
discreet developer about autodesk. 😕

> Every bug fixed introduces the possibility of new bugs. Since development
> and testing for a service pack is shorter than a release, we have a much
> higher chance of seeing a regression. I'm sure you wouldn't be pleased if a
> hatch fix broke wall display, or something like that.

Gotcha. So it also stands to reason that the yearly release schedule
also increases the chance of bugs. I guess it just feels like there have
been more in ADT since 3.3.

> Again, I'm sorry for the inconvenience.

Thanks again Dennis. I'll shut up about it now. 🙂


--
David Kurtz
Peckham & Wright Architects, Inc.
Columbia, Missouri

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report