Currently when doors, windows, walls, etc. are placed when a level is set as active, the various components of the part land on different levels. The part placement actually creates levels that have been programmed into the part and cannot be changed. These additional levels do not even register as "used" when filtering to find what level and information has been brought into the file. The function of part placement worked fine in AECOsim V8i. This malfunction started when we switched to OBD. It is understandable that it can be advantagous to have, for instance, window frame, glazing, etc. data separate in order manage, but without control of the corrosponding data it does more harm than good.
It creates numerous problems, especially with a multi-story building to keep these parts on the different floors where they are designed to be. It also causes problems with drawing production of plans and sections.
When tested, drawing production for the same file works fine for plans and sections in AECOsim V8i but not in OBD for the same model file.
| How frequently will feature be used? | Several times a day |
| How much time will you save? | Working around this problem consumes a substantial amount of time for each project. I have been considering using a differenct CAD program after 20 plus years. |
Are you creating a wiki for a solution to this specific issue or just in
general about the use of levels
Hi Richard, we will shortly create a wiki on the use of levels and dynamic views explaining our recommended workflows.
We propose using at least one file per floor and reference them together.