Design doctor

[Anonymous]

Hi,
Here is an interesting picture (see the attached). There is an error in one
of the sub-assembly but the Design Doctor is not wiling to elaborate in
which one. I did try to interrogate him by all means available to me - no
luck. Shell I sent him to Guantanamo or what?

Igor.
PS. IV2008, Sp1

--
To reply please use igor@iinet.net.au address

[Anonymous]

I've had one or two of these myself.....he should be "struck off " the
medical register

STED

"Igor Mironenko" wrote in message
news:5655153@discussion.autodesk.com...
Hi,
Here is an interesting picture (see the attached). There is an error in one
of the sub-assembly but the Design Doctor is not wiling to elaborate in
which one. I did try to interrogate him by all means available to me - no
luck. Shell I sent him to Guantanamo or what?

Igor.
PS. IV2008, Sp1

--
To reply please use igor@iinet.net.au address

[Anonymous]

put the lime in the coconut and drink it right down......

take to aspirin and call me in the morning.......





"STED" wrote in message
news:5655679@discussion.autodesk.com...
I've had one or two of these myself.....he should be "struck off " the
medical register

STED

"Igor Mironenko" wrote in message
news:5655153@discussion.autodesk.com...
Hi,
Here is an interesting picture (see the attached). There is an error in one
of the sub-assembly but the Design Doctor is not wiling to elaborate in
which one. I did try to interrogate him by all means available to me - no
luck. Shell I sent him to Guantanamo or what?

Igor.
PS. IV2008, Sp1

--
To reply please use igor@iinet.net.au address

[Anonymous]

There was a defect that was targeted to be fixed for SP1 that dealt with
DgnMD reporting problems when in facct there were no problems. It seems as
if the "fix" for that issue may have introduced the observed behavior of an
active red cross with no problems listed.

I have forwarded this morning's posts to Bob and Johnson.

If anyone can supply (reasonably sized) data sets which exhibit this new
behavior in R2008sp1 please let us know.
--
Gary R. Smith
Autodesk Inventor Team
Portland, OR
2.33GHz 2GB IBM ThinkPad T60p; XP pro SP2
ATI Mobility FireGL V5250 driver: 8.293.1.0

[Anonymous]

The thing is that there was a problem with one part buried deep in one of
the sub-assemblies. When the top level assembly was opened for the first
time it gave me a report which file is not up to par. I looked at the
report, dismissed it and clicked on the Red Cross in order to truck the
problem file. And that's when I got the blank look from the Doctor. Still,
I fixed the file (lucky me I was able to remember which file was at fault
from the report) and the assembly is fine for now.
Igor.

--
To reply please use igor@iinet.net.au address
"Gary R Smith (Autodesk)" wrote in message
news:5655716@discussion.autodesk.com...
There was a defect that was targeted to be fixed for SP1 that dealt with
DgnMD reporting problems when in facct there were no problems. It seems as
if the "fix" for that issue may have introduced the observed behavior of an
active red cross with no problems listed.

I have forwarded this morning's posts to Bob and Johnson.

If anyone can supply (reasonably sized) data sets which exhibit this new
behavior in R2008sp1 please let us know.
--
Gary R. Smith
Autodesk Inventor Team
Portland, OR
2.33GHz 2GB IBM ThinkPad T60p; XP pro SP2
ATI Mobility FireGL V5250 driver: 8.293.1.0

[Anonymous]

We're seeing the same issue here. If you 'edit' the sub-assy you get the red cross but no info, the only way to find out the problem is to 'open' the sub-assy, however, when you have large assy's with many sub-assy's it is a royal pain to have to open each one to find the problem. If the doctor knows something is wrong he should be able to specify what and where it is.
I would attach a file but ours are very large, I don't think it will let me.

As a side note, we would like to see the doctor(picture) go away, he is annoying.

[Anonymous]

This problem has been reported and fixed in the internal builds. In the meantime you will have to edit the part (or the sub-assembly, I verified part only not the sub-assembly) to see and fix the error.

http://discussion.autodesk.com/thread.jspa?threadID=599907

(Based on the description, the error sounds same. I can verify if your issue is fixed or not if you could please send dataset to shekar.subATautodesk.com.). 965192 and 953111 are the issue numbers relating to these.

Thanks.

shekar