Jump to content

Jeffrey W Ouellette

Member
  • Posts

    864
  • Joined

  • Last visited

Everything posted by Jeffrey W Ouellette

  1. Try this for the v2013 file: https://dl.dropboxusercontent.com/u/11532539/VectorworksBIMWorkflowsDemoV2103.vwx.zip
  2. That diagonal line is actually an edge(s) of adjacent triangles. In many cases, the geometry of objects is exported as a simplified surface model. Surface models are made of triangles. For a 4-sided, flat surface, you would have two triangles. The more complex the polygonal geometry (more edges) and surface irregularity (curvature or folding), the more triangles you will have. This methodology is very basic to computation of surfaces and is expressed in the IFC specification as the most basic means of representation of 3D planar objects. Control of the rendering of these edges would need to come from the Revit side.
  3. For IFC2x3, the difference is a bit complicated. The relationship between and object (IfcColumn) and its type (IfcColumnType) is meant provide a system much like our internal symbol data structure (one definition, many instances). However, for the whole Building Services part of IFC2x3, there are inconvenient incongruities, mainly due to the proliferation of object concepts. Trying to tag a object with the appropriate IFC data, for both ends of the workflow, can be tricky. The team behind the IFC2x3 specification realized this and made significant changes for IFC4 that will benefit everyone. In this case, I'll file a bug to see if we can address this. I'll say this much, our focus has been on the IFC2x3 CV2.0 Certification for the architectural export requirements. It does not require support for all the possible MEP objects. That is extensively covered in the building services export requirements. Why? Because Vectorworks Architect is an architectural BIM tool, first and foremost. On the other hand, our Import effort requires us to support all objects and concepts. I believe we did and excellent job of this, with only very, very, very few exceptions or limitations. That being said, we have worked hard over time to expand our support for other objects/concepts, but it looks like there are still some missing parts. I'll see if we can address this. On the other hand, DDS does make a great MEP tool and they are now a Nemetschek family member...
  4. Bill, I'd be happy to share a recent sample file with you (and everyone else): Dropbox: Vectorworks BIM Example file v2013 Dropbox: Vectorworks BIM Example file v2014 It is a work in progress and I use it to test workflows. Should give you an example of a relatively simple story setup. As for renovations, I like Majic's approach. Couple that with Classes for demo objects and I think you've got a pretty good "best practice" set up.
  5. Give me a minute to look at it more closely.
  6. Guys, We have a partner for this very thing: CadFaster It works really well.
  7. I'll bet on AMF before 3MF... http://blog.stratasys.com/2012/09/19/new-amf-file-format-to-unleash-the-potential-of-3d-printing/
  8. gbXML export is now part of Vectorworks 2013. We have a strategic partnership with IES, Ltd. that leverages IFC and gbXML. We haven't thoroughly tested any other tools, at this point.
  9. Yes, it is a waste of time trying to use Fundamentals as a BIM tool. It is best to upgrade to Architect.
  10. We have a slider, but not the XX configuration you are looking for. This would be a good addition to the tool.
  11. You can create a custom symbol, with all the geometric specific to the configuration you are looking for and then use the "Use Symbol Geometry" option in the Door plugin object to insert it.
  12. There is the Bug Submit, via the link above-right in the "VW Community Links" menu box http://www.vectorworks.net/support/bugsubmit.php Communicating via VSS definitely helps, too. What version of Rhino are you using?
  13. Ray, rather than simply complaining about it, would you do us a BIG favor and report a bug with the files that are failing for you? Thanks.
  14. Are you referring to the use of the detailing tools or of the Framing Member and Column tools? The Framing Member and Column tools have default IFC assignments. The Detailing tools do not. They were NOT originally developed as standard BIM objects. Just use the IFC Data command to add desired IFC information. Also note that the default IFC assignment for the Framing Member may not be what you intend because there are so many different permutations on both the Vectorworks and IFC ends.
  15. Jim, the software for the current community board doesn't seem to like search terms of 3 letters or less. you could use google to look in the community board to find what you want; there is plenty piled up in here. Try entering this in a google search: site:techboard.vectorworks.net BIM Then you should be able to find what you need.
  16. Peter, I wouldn't go so far as to dumb down everything. Autodesk does have to suck it up and improve their IFC import. While progress is slow, they are working on it. We've had success with Walls, Doors, and Windows, though it is touchy. Revit doesn't like "flipped" Doors and Windows. It is easy to do in Vectorworks, flipping a Door/Window around after placement, and we export it and the transformation info, but Revit has difficulty resolving this operation. It is an issue both sides are aware of. Walls at different levels appear to be the result of conflicts with height settings determined by instance or style, especially when using heights set automatically by layers/stories, especially with top and bottom offsets. Again, it is valid information written, but not handled well by Revit, at this time.
  17. Have you tried converting the Extrudes to Generic Solids and then export them that way? You could run a test by taking one problematic object from the project, in a blank file, and place multiple instances of it. In each instance, change the geometric representation (e.g. Extrude, Generic Solid, NURBS, 3D Polys). Then export via IFC. Part of the problem is that Revit is trying to convert the IFC objects into native Revit data structures and the implementation of its geometry kernel isn't very flexible, at the moment. It has difficulty taking some valid types of geometry descriptions and making them fit the Revit ecosystem. You can help, by "dumbing down" the file for them.
  18. Custom workspaces don;t go in the application folder. They go in the ~User/~/Application Support/Vectorworks folder. Or, as Peter suggested, redirect your User folder to Dropbox.
  19. Vincent, The Room Name object is an OLD object (pre-BIM, if you will). The Space object, and all its functionality, including the customizable tags, were developed most recently, with these aspects in mind, creating some of these new features. In most cases, such functionality is not migrated back into old objects. Instead the old objects become "legacy". Why not use the Space object instead? You get more data out of it that can be scheduled through database worksheets. If the simple Room Name object is important, then make a case for changes in functional parity on the Wish List.
  20. IFC Entities are plug-in objects, not resources like Symbols or Wall Styles. You can put them in Symbols, however....
  21. IFC files can be imported into a VWX file that is setup as a reference source into your project, just like DWG.
  22. In Garry's scenario, replace the DWG files with IFC files and you have Open BIM.
  23. Why not use the Framing Member for the precast elements, then the Slab tool for the topping slab?
×
×
  • Create New...