Model Category Meltdown

[jsnyder]

I thought I would post this up here to get some feedback before I send the file off to the factory. We have a model that now hangs whenever the team tries to access Visibility Graphics or Object Styles. I did some digging into the past and found a version from almost a month ago that would allow me to access either one of the two dialog boxes. Look what I found...
I was under the impression that we could not add model categories. Yet here we have literally hundreds of new model categories, all named "0". It is a little hard for me to believe that they worked in the model for a month without wondering what all that stuff was, but there you have it. I can only imagine some kind of mangled, mutant DWG import/explode operation gone horribly wrong. Has anyone ever seen anything like this before?

[Alex Cunningham]

Thats a lot of layer 0's. Let me know if you can make Defpoints too.

[elton williams]

I thought I would post this up here to get some feedback before I send the file off to the factory. We have a model that now hangs whenever the team tries to access Visibility Graphics or Object Styles. I did some digging into the past and found a version from almost a month ago that would allow me to access either one of the two dialog boxes. Look what I found...
I was under the impression that we could not add model categories. Yet here we have literally hundreds of new model categories, all named "0". It is a little hard for me to believe that they worked in the model for a month without wondering what all that stuff was, but there you have it. I can only imagine some kind of mangled, mutant DWG import/explode operation gone horribly wrong. Has anyone ever seen anything like this before?

wouldn't an imported DWG have it's categories listed under the "imported" tab...? something definately screwy:crazy:

[psteel]

my first instinct would be that someone has exploded an imported DWG.

Can you select and isolate these elements say in a 3D view to ascertain what they are. We have had to do
a similar audit, that time we placed are the rogue elements in to unique workset.

Greetings from London

[gdoherty0102]

my first instinct would be that someone has exploded an imported DWG.

Can you select and isolate these elements say in a 3D view to ascertain what they are. We have had to do
a similar audit, that time we placed are the rogue elements in to unique workset.

Greetings from London

Exploded DWG would be my guess as well.

[Jj Mac]

Look what I found...
I was under the impression that we could not add model categories. Yet here we have literally hundreds of new model categories, all named "0".

Never seen this before either, but thanks for posting. This defiantly needs to go to Autodesk. Keep us posted on what they say! Good luck.

[mdradvies]

this isn't an exploded dwg. that's not added as an model category. those are converted to model lines.
This needs to go to Autodesk, cause something is definitely broken.

[jsnyder]

this isn't an exploded dwg. that's not added as an model category. those are converted to model lines.
This needs to go to Autodesk, cause something is definitely broken.

Yes, they are chewing on it right now. I will report back results for the sake of posterity.

The file was definitely in the ditch - the first day there were 8 "0" model categories. The next day there were a couple hundred. The next day, a couple thousand. BOOM!

[mdradvies]

Keep us posted, would like to know what caused this!

[jsnyder]

A quick update since we are still waiting a definitive answer from the Factory. The following was the initial response:

"After some further research, I have found this issue logged with our Development group. From the information we have, it looks like the issue stems from families that were either created in Inventor, or have nested elements that were. When the families are loaded/reloaded, it adds a "0" model category."

We do not use Inventor. Still don't even know if they can fix the file. Be careful out there...:banghead: