• Content count

  • Joined

  • Last visited

Community Reputation

8 Neutral

About nrkuhl

  • Rank

Personal Information

  • Occupation
    Architectural Designer
  1. 2017 SP5. If placing them in the design layer directly, they do show the correct elevation, but refer to my previous post for the problems related to that. If placing them on annotations, then you have to use one of the methods you list for 2d drawings. None of which solve the issues of coordination brought up by the OP, or come even vaguely close to matching the functionality of elevation benchmarks and grid lines in other BIM programs, or link to the story information that we have already entered into the model.
  2. No elevation benchmark I've ever placed in an annotation layer in VW on a live section has ever shown a proper elevation without significant manual intervention. @Samuel DerenboimIf you're talking about placing the benchmarks in the design layer directly, they don't show up properly in views that aren't orthogonal to them and seem to lose some of their formatting controls.
  3. Revit import does not result in particularly functional objects. Importing 2D .DWG works reasonably well. 3D objects from other programs can be finicky. I think your best case scenario in VW is that Revit users would export their sheets to 2D dwg and send to you. PDF export could also work. We have a lot of consultants using AutoCAD, and we typically export DWGs specifically formatted for them to use as bases, and we send them a PDF of our drawings as a reference. I'm pretty sure you will not be able to edit Revit objects and send them back and forth between the programs with any real functionality. You definitely can't in 2017, and from what I've seen in the forums, 2018 isn't a huge difference in functionality. They are fundamentally different programs, so this is not that surprising.
  4. Have there been any updates on the NAS reliability front? My office needs to replace our server, and we're looking into whether we get a new server, or a NAS setup. We do (attempt) to use project sharing on our larger projects. We are a Mac based office, so the server would probably be a Mac Mini server.
  5. The design layer viewport trick is fine as a work around, but it adds another layer of updating and adjusting. It would be ideal if we could just shoot a perspective/ortho/whatever view straight to the sheet layer with the clip cube active, like we can with any other view. This wishlist item gets my vote.
  6. One more interesting note: this seems to be file dependent. I have one file where the site model is filled in section viewports as expected, and one where it isn't. So far as I can tell right now, they have the same settings.
  7. I just unchecked the "show 3D" in the OIP and that took care of my interference issues. I guess I don't understand what that checkbox is meant to do. I also can't seem to change the 2D top/plan fill of my texture bed. It only shows as solid white.
  8. This may be a very obvious question, but how do you raise the elevation of a texture bed via the OIP? I only have x and y location fields, and moving 3D or move by points in Z direction seems to have no effect. I'm attempting to use texture beds for generating roads on a site model as a work around for having roads actually mapped to the site surface. However, I'm getting the interference effect as others have described in this thread. It would seem that if I could even give the texture bed a bit of thickness, then this would work.
  9. Oh snap, I had no idea, that helps for sure! It would still be nice if you had this control popup at time of duplication.
  10. It would be great to have some layer visibility controls when duplicating layers. Currently, a duplication will show up in every viewport where the original is visible, but that is almost never the behavior that I want when I duplicate a layer (which is often done to generate multiple proposals in a file).
  11. I'm having a similar problem - I can't get site model to show fill in any section viewport. I've checked everything I can think of and followed all advice in this thread and this one: Still no progress.
  12. Hmm, if we have multiple layers that address the same sort of level in a story (i.e. first floor as built, first floor demo, first floor proposal 1, proposal 2, etc), usually only the as built is created as a "story level" via the story dialogue box. The others I just create and assign to the story via the layer creation dialogue. This is why we've lately been putting stairs on their own layer - this way they can use z references from stories without being confused by the proliferation of layers. So, stairs from floor 1 to floor 2 have 1-Stair as their bottom level and 2-Stair as their top level. We do a lot of work in existing buildings, and it is typically preferred to keep the stairs as-built or rebuild exactly as as-built due to IBC, so stairs are often a given for us. Did I understand the question correctly? I don't find myself using saved views much.
  13. Oh, interesting, I also have VW Arch, and do not see that option in the OIP for any extrudes I create.
  14. Oh, object has to be set to be an IFC entity, I missed that part
  15. Do we get that checkbox on solids in the US version of VW? I can't seem to find it anywhere.