Jump to content

Mihail Rizov

Vectorworks, Inc Employee
  • Content Count

  • Joined

  • Last visited

Community Reputation

33 Great


About Mihail Rizov

  • Rank

Personal Information

  • Occupation
    Software Engineer
  • Location

Recent Profile Visitors

812 profile views
  1. Hi @Laura Stone, Sorry, we can't try this, because we don't have the full model - we have only the excerpt you sent here ūüėČ Export Site model affects only the export of DTM object that is representing the site (and its layer must be mapped to Site story). Regards, Mihail Rizov
  2. Hi @Laura Stone, I can confirm that assigning materials in Revit works only if the geometry is extrude/solid and not in case of surface geometry. IFC sends the geometry as is and in case of Aligned Slab, the object geometry is mesh (surface geometry). Regards, Mihail Rizov
  3. Hi @Laura Stone, We still don't have Revit 2021, but tried with 2020/2018 (used Improved IFC Import Add-In, as with the standard one nothing imported). In all cases, Revit shows the color of the geometry (from Vw) - the objects are imported as Floors with Import Symbol inside and you can assign material to both of them, but it always shows you the original geometry color. For me, the problem is that, actually Revit can handle well only solid geometry - we'll try and will get back to you. Regards, Mihail Rizov
  4. Hi @Laura Stone, It seems to me, it's probably Revit Import problem. But, we have to find out the reason and use a workaround, if necessary. Please, send us a small excerpt from the model that illustrates the problem, so we can try export and import in Revit. (Also, please tell us the version of Revit that is used in your data exchange.) Regards, Mihail Rizov
  5. Hi @elch, Could you re-post your files, as it is not possible to download them? Thanks, Mihail Rizov
  6. Hi @Matt Hagen, We are looking into this issue - temporarily, you can attach IfcSlab to them and set PredefinedType field to one of LANDING (if it is a part of a ramp/stair), ROOF (you know when), otherwise BASE or FLOOR (both are actually a floor, but BASE is a load-bearing element and as such is part of the building structural model). I'll notify you with our findings, when ready. Regards, Mihail Rizov
  7. Hi @Matt Hagen, I've reviewed your file and here are my comments, specifically about IFC (I can talk only about IFC): - You used a lot of extrudes in your model and you can't see them in IFC model, which is normal. IFC works with objects and each object consists of designation/type (defining the purpose of the object - like is this a wall/column/slab/roof/furniture/beam/etc.), data, relationships with other objects (like positioned in a building story, space, contained or part of another object, etc.) and geometry representation. So, an extrude might be the geometric representation of a wall, covering, column, footing, ... and this is why the user has to define what kind of object represents the extrude in question - this can be done by directly attaching IFC Data or using Data Manager class-based mapping. If you use Vectorworks plug-in objects - you don't have to do anything - they have the proper IFC designation and settings already defined. - You exported IFC4 file - at this moment, only Vectorworks and ArchiCAD have certified IFC4 export (IFC4 import certification not yet started). Even some applications claim to support IFC4 - you shouldn't trust claims. So, please use IFC 2x3; Regards, Mihail Rizov
  8. Hi JMR, Please, try it with 2020. Regards, Mihail Rizov
  9. Hi David, As I promised, I asked about your question and here is the answer: "The menu style used in worksheets does not support separators. But this is an improvement we could consider for a future version. Hugues Tsafak Director of Product Development"
  10. Hi David, My answers: - Item 3 - please, file a bug; - Item 2 - sorry, this is outside of my field of competence - I'll try to get an answer from the right person. Regards, Mihail Rizov
  11. Hello, It seems to me, it will be better to have a simple example file attached, so I would be able to examine this closely. Now, to your questions: 1 - We plan to change that for SP3; 2 - Here an example will be of a great help; 3 - Except the need of an example file, as I don't know the content of the worksheets you mention, I'm not sure I understand this "you have to make a selection in the OIP first, or the worksheet selection does not seem to stick" - please, clarify with more details; 4 - Actually, the change happens in real-time, but the object(s) needs to be reset to show the change. OK, understood. 5 - Door is the plug-in object that comes with the English version of Vectorworks. Door CW is a plug-in object that replaces Door in the localized version for DACH-countries; Best Regards, Mihail Rizov
  12. Hi @milezee If you can log bugs in JIRA - this is the preferred way. Otherwise, sharing files platform. Regards, Mihail Rizov
  13. Hi @milezee, How could I get at least one of the files, in order to see what's going on? Regards, Mihail Rizov
  14. Hi Zeno, Of course, Vw supports unique IDs for each object (GUID) and even at the level of components (like for the walls). The other concept is not exactly just a timestamp. It is IFCOWNERHISTORY - it contains not only the timestamp for creation and modification of the object, but also last user and application, type of modification, state and access of the object. It is possible in IFC to attach this to every object in the model, but I've never seen an application to support it at the level of objects - it is supported at the level of the project, so there is just one instance of the owner history and it is used from all of the objects in the model. There was a proposal to all IFC implementers (members of buildingSMART ISG) to make this support, but the main reason to not make it is, that this will make files a lot bigger and will slow down all the applications, along with the implementation costs. Regards, Mihail Rizov
  15. Hi gester, Component functions were made to map component data in one particular workflow, which requires each component to be exported as a separate instance (ExportOptions->Export Separate Instances). So, during the export it returns the component data, based on the currently exported layer. Otherwise, it uses the core component data in the calculations. First, you have to remove the custom pset from Manage Custom Psets (IFC Data dialog) and then you have to be sure that a custom pset is removed from all data mappings. (if even one object uses this custom pset in its IFC Data mapping, then the custom pset will be recreated again) Regards, Mihail Rizov


7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114


© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

  • Create New...