Taking up a proposal I made many years ago, regarding import of dwg files.
As we know dwg format doesn't have the possibility to have multiple models in one file. At least that was the status the last time I worked in Autocad. One thing that dwg does much better than Microstation is handling cells. In Autocad this means shared cells, which are stored in the dwg file itself.
Honestly I never liked the way Microstation handles this, shared cells have a bunch of bugs and they don't really work. Especially it is difficult to access them for change.
What I proposed this time was that when opening a dwg file, Microstation should handle each shared cells in the dwg file as a model for itself. This would open a world of possibilities and probably even fix some problems in Microstation itself.
The reason I am taking this up again is, that we are increasingly changing formats for exchange in the building industry. The dwg format is becoming a second option, as ifc is taking over as an interdisciplinary exchange format between different programs.
At the moment AecoSim has 2 options for opening ifc formats. The old way is the file - import way, which mirrors the structure of an ifc file by creating a couple of files which are referenced into a master file. The backdraw of the method is that it is extremely slow and generates extremely large files.
The new way is the file - open method, which creates one file, and is quite fast in it as well. The backdraw is that the original structure of the ifc file is not saved. If the architect had split the model in different floors, you won't see it in Aecosim.
So let's get back again to the proposal for the dwg file.
Why not use the functionality of Microstation, and import the ifc into different models, and reference them into the default model of the dgn file?
Think about it.
Not sure I am following this... could you propose a specific workflow that might make it more obvious what it is you are suggesting?
Also...
Unknown said: shared cells have a bunch of bugs and they don't really work.
shared cells have a bunch of bugs and they don't really work.
would it be possible to identify specific issues that are impacting you? TIA
Shared cells have always been a source of troubles, and I have filed a couple of SR's on them. Things are Not lately, because we don't use them anymore.
To mention a few:
- SR 1-305444912, TR 136399, date (2005-04-11)
- CR 8000765702 (date: 2010-03-12)
- and a couple of other SR's where we are having problems with drawing extractions.
...and my first blog on communities:
communities.bentley.com/.../cells-and-headaches.aspx
...or this post
communities.bentley.com/.../50620.aspx
Unknown said:- SR 1-305444912, TR 136399, date (2005-04-11)
This Service Request is from 2005 and we no longer have access to those records.TR # 136399 does not seem to be related to what is being discussed here and was actually verified as fixed in 08.05.01.XX in 2004.
Unknown said:- CR 8000765702 (date: 2010-03-12)
Service Ticket # 8000765702 just seems to have been raised regarding the second discussion forum.It does not seem to have had a Trouble Report or Change Request raised for it.
Unknown said:communities.bentley.com/.../cells-and-headaches.aspx
This items seem to be a Blog with an opinion about how Bentley should be dealing with Shared Cells.It does not really relate back to any Change Requests which may have been raised for you.
As Phil suggested you might like to provide a full explanation for what it is you are trying to achieve here.This could include example files, screen captures, your expected workflow, etc.We could then look at whether a Bug Report has already been raised for this particular issue or investigate the possibility of raising a new one.
RegardsAndrew BellTechnical SupportBentley Systems
Regarding # 8000765702 I really haven't got any clue why it hasn't been taken up by Bentley support staff, that's a thing that you should discuss. It was filed as a change request, not a service request. Below is from the e-mail I've got this time.
The following is the result of a Change Request form. Note your Service Ticket number for future reference.
Regarding opening of ifc files, it is correct that I have not filed anything yet, as I just wanted to discuss the idea. If nobody ever has thought about it before, I have no problems filing something.
Regarding the first SR mentioned, I never have got any feedback that it is fixed. That's a problem with your "new" bugfiling system, where we never get any feedback. In the old times we did get a feedback when things got fixed.
SR 7000072696 filed for file - open - ifc behaviour.