Floor Manger keeps changing elevation

Hello

I am working with AecoSIm V8i SS5 

I am having problems with my Floor manager. When i input the elevation value in Meters (As below)  

However when i open the floor manger again it changes as per below 

I have seen older posts which has said to make the working units the same in the Design file and Dataset & Project DGNLibs, BB_FloorMaster. I have done this and hasn't fixed this problem

Below are Working units from BB_FloorManager & design file

BB_FloorManger 

Design file 

Help with this would be very much appreciated as i am completely stuck with this.

Thanks 

Parents
  • Hi Gavin,

    The design file appears to have been created from a MicroStation seed file, these are the standard resolution settings from MicroStation seed files used by civil designers working with large scale objects, building tools require the 1000 UOR/mm resolution for optimum operation. We recommend that your building DGN files have this resolution, most easily done by using the delivered seed files.

    Note that changing the resolution of existing files will change the size of any existing elements.

    This particular problem can probably be avoided by only editing the floor properties from a DGN whose resolution is 1000 UOR/mm.

    More recent versions may have dealt with this particular situation, we have enhanced the behaviour of both Floor Manager a Grid Systems dialogs' handling of unit settings, but we will have to test this particular combination.

    Marc

  • Hi Marc,

    I think we could ask a simple question:

    The default workspace/dataset (Dataset_FR for me) is configured in mm (millimeters).

    I would like to work in meters. Wich files must be changed and how ? (seeds, dgnlibs, cells, datasets,....)

    regards,

    chris

  • Hi Chris, sorry for the delayed response, I started to reply to this a few days ago but must have inadvertently closed the tab...

    The crucial files are:

    Seed files: they don't contain much these days, most library content is in DGNLIBs (or should be!), the important setting is the file resolution. It must be 1000 UOR/mm for use with OpemBuildings:

    Ideally all files in a project should have this resolution, but it is most important for files containing building elements. For instance 2D files at other resolutions or formats can be referenced as OBD will handle the scaling.

    BB_Floormaster.dgnlib: this must have the 1000 UOR/mm resolution. Note, while we do show a warning in the message center when the Working Units differ between the active file and the floormaster, this just refers to the display units, the behaviours of both Floor Manager and Grid Systems Manager have been enhanced by recent releases to handle differing display units.

    Other DGNLIBs: Some library content, levels for example, are unaffected by file resolution. DGNLIBs containing geometry should be scaled correctly regardless of resolution, but it is possible that highly detailed or geometrically complex objects with a lower resolution could behave inconsistently when cut by dynamic views.

    More detail in my blog.

    Marc

    Answer Verified By: Gavin Dungan 

  • Hi Marc, Thank you this solved our issue with the Floor manager. We now have 1000 per mm, The issue we face now is trying to coordinate our models with Civils, and structures who have a resolution of 1000 per Meter. Everything that we modelled in 1000 per Meter is very small now compared to what we will be modelling at 1000 per mm. I can see this been a problem when we link in Civils and structures models. And the same when it comes to them linking in our models. Is there a way around this issue?

    Thanks for you help

    Gav

  • Hi Gavin,

    Provided that elements are drawn at their correct size they will reference together correctly, the application deals with scaling between files of differing resolutions. Has scaling been applied to reference attachments?

    Have the contents of your files been rescaled when changing resolution?

    Marc

  • Hi Marc,

    It seems when I change our resolution to 1000 UOR/mm and reference it into other design models which are 10000 UOR/m they align correctly and same goes when we reference other models into ours. I believe scale is 1:0. Why do you ask if scaling has been applied? 

    The problem we have now is of course when we change the resolution half way through modelling, everything we have already modelled is in a different scale, see image below to get an idea of how our newly modelled wall looks compared to the rest of our model. Is there a way of re-scaling the elements we modelled before we changed the resolution? 

    For now at the early stages of our project we still have our resolution 10000 UOR/m (As this is what we have inherited) What problems would we have if we don't change to 1000 UOR/mm? Would this become more of an issue the more elements we model? 

    Thanks

    Gavin

     

Reply
  • Hi Marc,

    It seems when I change our resolution to 1000 UOR/mm and reference it into other design models which are 10000 UOR/m they align correctly and same goes when we reference other models into ours. I believe scale is 1:0. Why do you ask if scaling has been applied? 

    The problem we have now is of course when we change the resolution half way through modelling, everything we have already modelled is in a different scale, see image below to get an idea of how our newly modelled wall looks compared to the rest of our model. Is there a way of re-scaling the elements we modelled before we changed the resolution? 

    For now at the early stages of our project we still have our resolution 10000 UOR/m (As this is what we have inherited) What problems would we have if we don't change to 1000 UOR/mm? Would this become more of an issue the more elements we model? 

    Thanks

    Gavin

     

Children