Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by Christiaan

  1. We need to be able to generate traditional window schedules (vector-based as opposed to bitmaps) that fit on an A1 sheet and include dimensioned elevations of the windows/doors. Preferably all at the click of a button.
  2. Christiaan

    Flippin' Flipped Doors

    Hey Matt, thanks for poking your head in. The reason I think it's by design** is that VW doors (and windows) try to be flexible but just end up being a bit stupid about what's outside/inside, left/right. Flipping a door is a crude way of changing whether a door is a lefthand or righthand opening in or out, and it's this crudeness I think that leads to Will's issue, because some elements of a door don't even realise what they're meant to be doing (which seems to be the case with a custom leaf), because there's no explicit left/right, inward/outward. There's only the ability to flip the object. Or take for example the door/window ID tag. I've run into a issue when producing traditional elevation window schedules, using isolated instances of my door/window styles. The ID Tag will show on one side of the door/window when it's isolated (the inside) and then show on the other side once it's inserted into a wall (the outside). Again I put this down to an inherent underlying confusion within the door/window objects because outside/inside has never been an explicit setting. It's all fluid depending on whether the object is in a wall and which way it's flipped. There's a related issue with window sashes too. We should be able to specify whether a sash is inward or outward opening and it should stay that way whether we flip the window or not, but that's not the way it behaves. And then there's the Tilt/Turn Custom Sash Option, which has no controls for whether it's left or right hung, and doesn't understand that it should only open inwards. Tilt/Turns only opening inwards but VW will quite happily show a Tilt/Turn opening outwards if you crudely flip it. ** This issue could of course be dealt with as an isolated bug, but the problem seems to me to be the underlying design of VW windows and doors, very concisely pointed out by Mike in his comments above.
  3. Is anybody else having a problem with Keynote Legends disappearing when using Project Sharing? Have you been able to isolate when it happens?
  4. Christiaan


    Yeah, jumping from 2D CAD to 3D CAD these days is a huge leap of progress. Glad you're enjoying.
  5. Christiaan

    Flippin' Flipped Doors

    I'm in agreement with Mike. This might seem like a bug to us users but it works as designed as far as I understand it. Vectorworks doors do not understand what inside and outside are. I've been meaning to make a Wishlist item about this issue.
  6. Christiaan

    ready to make the plunge to Mojave

    I've been keeping a close eye on things and macOS 10.14.3 + Vectorworks 2019 SP3 is when I'll be flicking the switch in our office.
  7. One of many bizarre default behaviour decisions in Vectorworks. This button should checked by default, out of the box. Seems to be a user setting.
  8. Christiaan

    Workflow for large projects

    We've also experienced the other side of the coin on this one, at least when working in conjunction with Dropbox. If your network is congested in any way, say because your internet upload speed is slow or because you're working with large files, Dropbox is slow or you're doing a lot of uploads, then this method can actually be debilitating. You end up with no choice but to sign out whole layers, otherwise you can spend hours in a day waiting for objects to be signed out.
  9. Wha's the quickest way to transfer IFC data from one object to another? Say for instance I download this object: https://www.nationalbimlibrary.com/en-gb/rockwool/sp-60-firestop-slab/?lo=en-GB The Vectorworks file comes with a Wall object with all the relevant data attached, which is fine as these fire-stops can be installed vertically, but they can also be installed horizontally, so I need a Slab object with all the data attached too. Is my only option to manually copy and paste all the data across to a Slab object?
  10. Christiaan

    Transferring BIM data from one object to another?

    Ah yes, thank you guys! Sometime I need my hand held ūüė¨
  11. Been there, feel your pain.
  12. Can somebody clarify: are updated/re-rendered viewports meant to sync across Project Files/Working Files in all cases? Or are there exceptions?
  13. Christiaan

    Syncing of Viewports in Project Sharing

    Haha, well done. I think this also illustrates how silly the current behaviour is.
  14. Christiaan

    Syncing of Viewports in Project Sharing

    No, the only way I've found is to generate a new Project File once your render is done and then tell everyone else to dump their Working Files and create new ones. That does work of course if you have renders from multiple files that you want added to the Project File.
  15. Christiaan

    Syncing of Viewports in Project Sharing

    Agreed. We could effectively be running a render farm in our office but we can't push the renders back to the Project File from separate Working Files.
  16. Christiaan

    Transferring BIM data from one object to another?

    Good thought. After a little experimenting I've noticed that most of the IFC data is attached via Record Format. There is a small amount of IFC data that the eyedropper tool can transfer but mostly classification data that is better done manually. The Record Format on the other hand can be attached to the Slab by clicking on Attach Record in the Data tab of the OIP. But hardly any of the data is applied to the Slab. Here's the original Wall object data and the result of attaching the same Record Format to a Slab object.
  17. Christiaan

    Viewport updates with shared file

    I had the same question. Check this thread out Tim:
  18. Christiaan

    Workflow for large projects

    Yes we run into the odd problem. We will usually create a new project file when we hit problems. One sure way to screw things up, at least when using Dropbox, is for people to do a save and commit and then shut their computer down and go home before it's finished uploading to Dropbox. When somebody else comes in the next day and cracks on with things we've found this to cause problems. So watch out for that one if you're using Dropbox.
  19. Christiaan

    Workflow for large projects

    Couple of things to bear in mind if you split sections off into a file separate from the model file is that you'll lose the ability to use Section in Place. And in my experience Section Viewports in referenced files are notoriously buggy.
  20. Christiaan

    Bluebeam dropping Mac

    I saw the title of this thread and opened it up fully intending to point out how this would put the nail in the coffin of my efforts to explore Revu. But then I read this: This actually sounds great. Look around, from CAD apps like Onshape to specification apps like NBS Chorus. I'm a big fan of native apps but cloud-computing and web-standards is changing what's possible, and something like Revu is perfect for cloud-computing because it's all about collaboration. If they get this right my bet is it will provide an even better experience than native apps.
  21. I'd like to be able to use Nomad but it's often not capable of coping with our building models. They're just too big. I look at Twinmotion (which uses Unreal engine) and Archicad's BIMx and wonder why we appear to be so limited with Nomad.
  22. I've updated this wish to be about Nomad in general rather than focused on the AR aspect, because I'm running into problems with our files in the 3D View as well, not just the AR view.
  23. Christiaan

    Stepping Floor Plate Setup in Stories

    I use a single Storey for each level of the building and use Level Types to deal with any level changes within that Storey. I keep Wall Styles to a minimum. Our Wall Style default top and bottom bindings are set Layer Elevation and then I'll manually edit all wall instances (mostly more than one at a time) to adjustment the top and bottom bindings of all their components to suit each situation. This sounds like a lot of work, and it some ways it is, but it's actually an auditing process. You're checking all the junctions and making sure there are no errors. The more I model buildings in VW the more I learn to use automated behaviour thoughtfully and sparingly. I also prefer to manually model my Slab edges to exactly where I want them to meet the wall (we use one Slab object for the structural slab on its own layer and another for the finishing slab, plus another for ceilings again on its own layer), because the problem with auto-binding them is that sometimes when a wall is edited the slabs reset themselves and you end up with broken junctions in your section drawing. If they're manually modelled this can't happen, but it does mean to need to make any changes yourself when you move a wall for instance. For the moment this method also means windows and doors need to be offset manually, but I don't find this much of a problem in practice. If one of the level changes needs to be adjusted this means editing the Elevation Offset for each Level Type + adjusting all your window and door offsets. But that's it, all your wall components will adjust automatically to suit your Level Type Elevation Offsets. Attached is a screenshot of our typical Level Types. This project originally had three level changes, but now only has two. The more you have the harder is to manage and navigate, so some discipline is required.
  24. Christiaan

    Workflow for large projects

    We tend to break up large projects into model file + sheet layer file.
  25. I'd like to be able to join multiple walls at once when using the join command (‚Ćė-J) So in the following example I want to re-join these three walls because I've edited the Wall Style and my components are no longer joining correctly: Step 1, select all walls Step 2, execute the join command (‚Ćė-J or Modify > Join > Join) Result: all adjacent walls rejoined As currently designed I'd have to use the join command or the Wall Join tool to join each wall join separately. When you apply this to an entire model, let's say 8 storeys high with 140 flats, this can get pretty tedious, especially if you change the wall style multiple times throughout the project.


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.