References faster than base / original file ?

My case:

I want to ask because i have to render 60 flats on 5 floors in same position but in near top perspective .

I need a flats in same position but the flats have other shapes and clip volumes. So i'm not moving Camera but moving file to marked / clip point

As i see - moving whole design  with interiors  is so slow and sometimes crash  but  i found solution  - new file and design as a reference. Now i can move it faster and render.

Why references are faster in this case ? If they have same elements / same info  ?  Maybe because can't be edited - so are smaller / faster ?

Martin

Parents Reply
  • Yes... I think the use of read-only dgn's will increase in future. For a lot of projects, which are hosted by PW and require BIM compliance, most of the files we reference are read-only (which creates their own problems). 

    Ideally, the live dgns would be collated as an .ism, which would be updated every time a model is shared/published. 

    I suppose that the read-only nature of the info should make it easier / faster to handle. 

    One strategy would be to make the context an imodel / ready only. This is usually a big 'backgound' model that would slow things down... and not really require much write access. 

Children
  • OTOH, Bentley is probably thinking that if speed / scalability is what you are after, then you should not be using the Mstn environment and should use something like LumenRT / ConceptStation or maybe even Vue Render.... with something like an .ism as a bridge.

    It would be great if LumenRT, ConceptStation and Vue could get some Mstn DNA and ref attach external files.