When creating a new model file in Architecture utilizing the delivered seed files I find that there are a number of levels within the active file that appear without any associated elements in the file despite Level Manager claiming that these are used.
See appended screen-shot of Level Manager
Compress does not delete these.
I only want to use the levels associated with the relevant dgnlib file.
Any suggestions?
When I used to want to get rid of no-seeums in Microstation I would create a fence around the drawing and then do a Void-Fence delete. You could turn off the levels you want to protect and make a small fence to get all of the elements removed from the levels you want them removed from. Hope that helps.
Thanks Dean,
I have tried that as well as Select By Attributes. Neither method finds any elements.
It seems that Architecture creates these levels automatically no matter what original seed file is opened.
If I open the same seed file in just MicroStation these levels do not appear.
I get the same results. I can compress the levels and get rid of the 'used' ones if under Compress->Options I enable the setting: Delete Unused Levels. Can you verify you have this setting enabled? It doesn't really matter. After I compress the levels, save settings, save the DGN then reopen it, the same levels are 'used'. This seems to be a bug. Can someone from Bentley respond?
Thanks,
Dan
Hi Rodney
After some investigation I have found that all these levels are related to the parts defined in the dataset explorer. So, f.i., if the part "concrete" is assigned to a level "A-WALL-FULL" than this level become an used level and can't be deleted. This is related, I think; to the Dinamic View support.
If you want to use the levels associated with the relevant dgnlib file you shoul reassign all your parts to these levels.
Hth
Leonardo
Leonardo,
Thanks for the info.
I suspected something like that and was busy looking at the settings in the cfg files to determine whether it was possible to reset this. Have not found anything yet.
Regarding the Datasets have you also found an issue with the Datagroup catalog and Datagroup editor exe files?
I posted a thread regarding this a couple days back.
All the best
Rodney