Thursday, 31 August 2017
  3 Replies
  2.5K Visits
0
Votes
Undo
  Subscribe
NUKE kept crashing AutoCad, so I did what I usually do: run AUDIT first to see if that was the problem. It was. Over 100K errors fixed. Thought I'd share.

Can anyone glean from the attached screenshot what might have caused this?

Oh, and NUKE worked fine afterwards.
Tom,

From a partial screenshot? Is this some sort of name-that-tune challenge? Identify the celebrity from a close-up of their nose? :p

As for the causes of the Audit Bad Layer message, one prominent cause is by manually placing objects on the DEFPOINTS layer, at least according to this post.
It seems the eNotThatKindOfClass message is due to proxy objects, particularly from older versions of Land Desktop.
But this is all just a guess, and just regarding the last 6 audit errors there. Without the proxy information display, without the drawing, without the other 112,354 errors, I can't really offer anything substantial.

As for Nuke -- the first thing it does, after saving the file, is to run an Audit. In this case, it seems that strangely the file was able to be opened, but not saved. Note that when Nuke does fail, opening the file via the RECOVER command ensures that the Audit process happens first.

--J
Thanks, J. From what I remember, most of the errors were the eNotThatKindOfClass .

First time I saw this. It's sort of like finding a drawing where over 50K REGAPPS get deleted.
Might be worth mentioning to your Autodesk Reseller to see if they have any ideas. ;)

--J
  • Page :
  • 1
There are no replies made for this post yet.