Unwanted Levels in Seed Files

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?

Parents
  • 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.

  • Check out this thread...sounds like the same thing. http://communities.bentley.com/products/building/building_analysis___design/f/5917/t/13113.aspx

    Brian Thomas, AIA, LEED AP BD+C

    GH2 Architects

  • Hi Brian,

    Thanks for the referal

    Looks like the same issue.

    FYI Bentley have logged a service ticket for this issue.

    Hopefully will be resolved in the near future.

    Best regards

    Rodney

  • All you have alot of garbage levels in the library files.  I went in and clieaned all these up and have gotten ridden of many levels as I had a University Clients who does not want to see anything but approved levels.  USES the AIA Level set up.

     

    Eric

    Ustn since 1988
    SS4 - i7-3.45Ghz-16 Gb-250/1Tb/1Tb-Win8.1-64b

    Eric D. Milberger
    Architect + Master Planner + BIM

    Senior  Master Planner NASA - Marshall Space Flight Center

    The Milberger Architectural Group, llc

  • Please note the following explanation re. unwanted levels in any Bentley Architecture file:

    The parts and family system can define different levels for forwarded, cut, reflected and centerline graphics. Since the Drawing Extraction Manager created new elements in a separate file, this was not a problem. However, Dynamic Views do not create new elements or create separate files, as the same data is just displayed in a different presentation. The problem is that these alternate presentations cannot be created on levels that do not already exist. Therefore, as a workaround, the dataset is scanned for undefined levels, which are then added to the DGN-file. As a result, users may have levels in their DGN-files that they believe they have not used. 

    This scan is performed by default to support Dynamic Views. However, if the configuration variable BB_DVDATASETELEMENTS in C:\Program Files\Bentley\MicroStation V8i\Triforma\config\atflocal.cfg is commented out this scan and the creation of undefined levels is disabled. However, this is likely to lead to problems in Dynamic Views!

    If the Section, F&R view, and Center line levels are identical to the model levels there is no need to scan the part files and to add undefined levels.

    Note: When editing a dgnlib file in Bentley Architecture, make sure that BB_DVDATASETELEMENTS is not defined, i.e. it should be commented out in the configuration file C:\Program Files\Bentley\MicroStation V8i\Triforma\config\atflocal.cfg.

    To delete the unwanted elements that carry the level information, use File > Compress > Options > Delete Building Dataset Elements.

    Hope this helps.

     Regards,

    Volker Thein [Bentley]

     



  • Hi Volker:

    In my opinion, the big problem here is the BB_DVDATASETELEMENTS  should NOT be set up the way it is.  As mentioned, you have to be careful to COMMENT OUT this variable in the atflocal.cfg BEFORE you open any other files your will populate those files too with unwanted levels.

    How intuitive is that?  I added levels to several files without even realizing it.  This is not expected from past history with BA.

    If a users works with a full level set containing everything in his parts library, I take it he does not need this feature.

    Perhaps there is a way to check AGAINST THE EXISTING level set BEFORE adding datatset elements to each of these levels.

    Perhaps the new levels could be inserted when you start to use Dynamic Views, instead of when you open the file.

    I have two questions for you:

    1.   Is there an intention for a new release of BA V8i soon?

    2.   How EXACTLY does the BB_DVDATASETELEMENTS  variable FIND and CREATE the levels to put in the drawings?  I am finding levels that do not appear in any of my catalogue files or parts files.

     

    Neal Kruse

Reply
  • Hi Volker:

    In my opinion, the big problem here is the BB_DVDATASETELEMENTS  should NOT be set up the way it is.  As mentioned, you have to be careful to COMMENT OUT this variable in the atflocal.cfg BEFORE you open any other files your will populate those files too with unwanted levels.

    How intuitive is that?  I added levels to several files without even realizing it.  This is not expected from past history with BA.

    If a users works with a full level set containing everything in his parts library, I take it he does not need this feature.

    Perhaps there is a way to check AGAINST THE EXISTING level set BEFORE adding datatset elements to each of these levels.

    Perhaps the new levels could be inserted when you start to use Dynamic Views, instead of when you open the file.

    I have two questions for you:

    1.   Is there an intention for a new release of BA V8i soon?

    2.   How EXACTLY does the BB_DVDATASETELEMENTS  variable FIND and CREATE the levels to put in the drawings?  I am finding levels that do not appear in any of my catalogue files or parts files.

     

    Neal Kruse

Children
  • This is actually part of a bigger discussion.

     PARTS and CATALOGS

    Without great detail or discussion - I feel that there needs to be a greatter discussion of where parts and catalags fit and how they will evolve.  Also greater thought and then input from the users.

    I am constantly told that NO direction is given to how to use BA as it must remain flexible.  However it is obvious that the  users see otherwise as the first thing syou see in the support groups is the request for datasets.

    Therefore a methodology for using BA is important.  And if you look at BA's competitor it is usable out of the box.  This being said and to keep industry compatability.

    This being said we need a complete group or organized parts and a complete Group of Organized Assemblies

    Use Masterformat for Parts and Uniformat for Assemblies

     

    Ustn since 1988
    SS4 - i7-3.45Ghz-16 Gb-250/1Tb/1Tb-Win8.1-64b

    Eric D. Milberger
    Architect + Master Planner + BIM

    Senior  Master Planner NASA - Marshall Space Flight Center

    The Milberger Architectural Group, llc