• Content count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About taavilooke

  • Rank
  1. My impression was that that the symbol definition has to have a tag. Then it will export as one element/component. Otherwise the behaviour was inconsistent. Also, I could not find any way to export solids and symbols into IFC so that they would have subtags (like the way walls decompose into components or curtain walls into plates and members). For the other things I don't have much experience with those.
  2. In the Default library at Reports_schedules/Architectural Reports.vwx there is a worksheet Objects without IFC Entity that lists all object without an IFC tag attached. There you can right click on the row header (the gray color thing on the right with the worksheet row number on it) and click Select item. This is only useful for solids, autohybrids and some PIOs that cannot be styled (railings and stairs). Adding data to windows, doors, symbols, walls and slabs should go through the Resource Browser.
  3. It would make a lot of sense that all objects would have some IFC type attached already (like IfcObject). Then they you could see that something some data is missing or erroneous and make the appropriate changes. At the moment these objects just do not appear in IFC and unless you intentionally look into it, no-one will find out that something is missing. The workaround that I found is to make a worksheet that looks up all symbols without an IFC type attached... Also, weirdly, if I assign the type IfcObject to an object, it does not show up in the export at all.
  4. You can actually assign the IFC type to the symbol definition in the RB. Or if you change the IFC Data of an instance it asks you if you want to assign the same data to all other instances. However there is still this problem with Project sharing...
  5. We have just finished making the first really standard-compliant BIM model with Vectorworks. Vectorworks is indeed capable of producing correct IFC models but there are lots of weird behaviours and bugs that need some kind of a workaround. So, I though I'd share the knowledge I have gathered going through this. Hopefully it will make it easier for those who have to start working with BIM. We worked on VW2017, so some of those might be fixed in 2018 (I have tried some on the new version as well and these have not been fixed). Following is a list of things that do not work as expected or need some weird workaround to accomplish: Walls/Slabs If the wall profile has been set by dragging the handles for the wall ends, but the profile is still horizontal, the wall exports to IFC with the full height (displayed in the OIP) rather than the where the handles are, even though it shows the correct geometry in VW). U-values of wall and slab styles should be written directly into the ThermalTransmittance field in the IFC Data. The style parametric object does have a field for the U-value of the wall (that is also exported to IFC), however this field is not exposed anywhere in the interface to write values into that field. When you offset the profiles some of the components of walls or assign some components to different classes, the data about the wall components and thicknesses is not exported to IFC. Also walls are exported by component, data about the materials is missing as well. Roof faces are missing most of the IFC data, it has to be entered manually through the style IFC Data option. Curtain Walls are exported with the IFC layer field empty (all other objects export the VW class as the IFC layer) Wall End Caps export to IFC with the geometry corrupted. Wall recesses export to IFC only if they are made with a 2D object, but not with a 3D object (or a 2D symbol). I think it should be possible to accomplish the same thing with symbols with a wall hole component. Windows/Doors The geometry of the window frames is corrupted in IFC— the jambs of windows are not rectangular but in an X shape. Also, both the window and the jamb are transparent. Adding U-values to doors and windows through the style IFC Data does not work consistently for me. It is more foolproof to add the value to one of the User Data fields in the style and map this value to export to the ThermalTransmittance field in IFC through the Data Mapping dialog. Even though there is a field in window data for frame and glazing materials, this is not exported to IFC. I have not managed to change the data mapping to make those fields export. The best way I found is to write this info to a User Field and change the mappings accordingly. Symbols Symbols are not exported to IFC unless they have an IFC type attached (same is true for solids). They also do not export if the object does not have a fill. This can easily lead to mistakes, because there is not really an easy way to check that all object that should be exported do have a IFC type assigned. Symbols export with the IFC layer field set to the VW class that is assigned in the Symbol options dialog (not the class that the symbol instance is actually on like all the other objects) If an IFC object is placed inside another symbol, the export behaviour is somewhat unpredictable. If the symbol is a VW parametric object it exports without having a IFC type attached (however it does not create a wall hole, unless the IFC type IS attached). For symbols containing other symbols, it does not export without the IFC type and also makes all the content into one IFC object (that does not decompose into the subobjects). Scaled symbols export with the original size not the scaled size. This one is actually useful: if you assign an IFC type to a symbol but do not change the name field, it will export with the name of the symbol as the name field by default (even though it does not show this in the IFC Data tab). Project Sharing IFC Export Settings are not saved to the project file on commit. To get them to save you have to turn the project file back into a regular document, make the changes and convert it back to project file. Data Mapping settings are stored in the local computer and are not saved in the project file (or a regular file either). In a Project Sharing document, the changes made to IFC Data of symbols are not saved to the Project File, changing them needs the same procedure as the export settings. Miscellaneous Adding data to PIOs that cannot be styled is a hassle, because the same data has to be added to all the objects separately. In these cases I have resorted to creating symbols of these objects. I think this gets better with VW2018, even though stairs and railings still cannot be styled. Assigning an IFC type to a group does not make it export to IFC. Spaces export to IFC only if they have the Show 3D option checked. Also it seems there is no way to make a space object with variable height. Parking spaces export as IfcSpace objects. This can lead to confusion, because you cannot differentiate real spaces and the parking spaces. It’s best not to export Parking Spaces at all. Solids and Autohybrids are sometimes assigned weird colors in IFC (it seems to depend on the IFC type attached to them). Stairs and Curtain Walls decompose to subobjects in IFC that do not have any data attached (the object that contains them does have all the data though). Some BIM standards expect object in IFC to have two levels of names, a generic name (Type Name in Solibri) and a specific name (Name). It seems that Revit and Archicad make use of these two levels to organize the objects and styles, while Vectorworks resource structure does not (this might be changing with the new window and door catalogs in VW 2018). The content of the Type Name field can be controlled for most objects in some way or another, but it seems easier to just declare that the content of this field does not matter.
  6. We are have to do a formalized BIM process now, where every engineer is producing IFC models. Importing the IFC model into a separate VW document and referencing it to the model seems like the best way, I've found it easiest to create a separate layer for the DLVP and switch the layers in it on and off as needed. Since the engineers are constantly producing new models, it's easier to update one reference rather than one for each story. If you need to produce valid IFC models, then architects and engineers should make their own objects and just keep them in sync. Every object in the ifc model has to have it's own unique GUID, hence copying objects from one file to another does not work well with this. We are using Solibri Model Checker to run a conflict check and see where the object are not aligning and should be corrected. Of course if you don't have to produce a IFC model yourself, you don't have to worry about the GUIDs and could theoretically import the engineers model into yours. It's also worth noting, in our case engineers only model the load-bearing structures while architects model everything.
  7. Hi! I'm trying to attach the U-value to wall styles for exporting it to a IFC, but there's a weird inconsistency in the settings. In the IFC Data Mappings tool there is a list of properties which can be exported to IFC. Most of these are visible in the wall/slab style data tab, with the exception of U-value. I can query the value in a worksheet ('Wall'.'U-value'), however this just shows 0. Does anyone have experience with that? Where can I set this variable for the wall/slab styles? Is it dependent on some setting or a preference that the U-value is not shown in the data tab? Thanks, Taavi
  8. It seems I managed to solve this problem. You have to convert the project file back into a regular VW document, make the changes to the IFC settings there and turn this file into a project file again. Then the IFC settings set in the regular document will always show up in the working files. Kind of tedious, but better than nothing.
  9. Here is the dialog I was talking about. If the other users accept this change, the spaces become uneditable. As far as I know, I have not changed any formats, whatever this is.
  10. Hi! There's a weird problem with space elements: every once in a while they become uneditable (like the one that is selected on the screenshot)-- instead of the normal OIP for a space it shows only a few fields for the element and the boundaries of the space cannot be changed any more. Sometimes it helps to restart VW or create a new working file from the project file. However other times the spaces stay like this and the only way to change them back to normal, is to delete the space and crate a new one. Has this happened to anyone else? What could be causing this? We are working on VW 2017 SP4 with project sharing. Regards Taavi
  11. Hi! I'm working in a Project Sharing file and trying to export to IFC. It seems that the data that is entered into the Export IFC Project dialog will only stay in the same working file that it is in. Even when I also commit the setting to the project file, it does not show up in the other working files or in new working files created from the master. Does anyone have experience how to save the IFC Export Setting to the Project Sharing master file? Regards, Taavi
  12. Oh well, you've got my vote on this. As a sidenote, this WinDoor looks like a really good plugin, it's a pity they only sell it down south.
  13. Is it possible to replace the window and door ID labels with custom ones, that would display some additional information from the data attached to the elements (e.g. the dimensions or fire resistance)? It would be really useful, but I haven't found any reasonable way to do this. The ID label tools seems to be the right tool, but it still only allows displaying the 3 ID parameters just like the window element itself. Regards, Taavi
  14. Hi! The geometry and textures of windows are wrong when I export the model from VW 2017 to IFC 2x3 CV 2.0. The frame of the window is transparent and the faces of the jamb and sash are intersecting. I've attached a screenshot of what the window looks like in Solibri. What could be causing this and how do I fix it? Thanks, Taavi
  15. Hi! I'm trying to create a wall that has vertical and horizontal joints (essentially just the outermost layer of concrete removed). I've attached a picture of what I'm trying to achieve. At the moment I'm creating the horizontal joints by lowering the top bound of the outer layer in the wall definition, and the vertical joints by creating wall recesses. However there is a problem that these recesses do not export to IFC. Using a symbol seems reasonable considering that the wall has about 1000 of these joints. However I cannot make a symbol of the recess itself and I cannot make a recess with a 2d symbol (rectangle). I can only make a recess with a symbol that is a box and in that specific case it does not show up in IFC. Why could that be? Is it a bug? Are there any other ways to create these joints? Regards, Taavi