Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by Christiaan

  1. If I model them in next project I think that's what I'll use. What would be better of course is a tool that inserts them into the wall and binds them to a top and bottom Level. No, just by manually drawing the shape. The advantage of the Slab object is that I can set it to a Level. Yeh good idea.
  2. Ever since the Greenfell Tower tragedy, which killed 72 people, the installation of cavity barriers (used to inhibit the spread of smoke and fire in concealed spaces) has come under the microscope in the UK. Partly in response to this we've started modelling cavity barriers. This makes them a more prominent part of the design process and has helped me to put earlier thought into their arrangement. Instead of applying them as 2D objects latter in the process. It also provides the possibility of displaying them in 3D, in a 3D view or even on an elevation, with the outer wall components turned off. The problem is I've only been adding horizontal cavity barriers to the model, using the Slab object. At the moment I'm still relying on 2D for vertical cavity barriers. Because there's no suitable tool that comes to my mind that can conveniently model vertical cavity barriers and insert them into walls. And the Slab object is not particularly ideal for the horizontal barriers either, as it would be useful to be able to insert these into walls also. So I'd like a tool designed for this purpose. See also: https://forum.vectorworks.net/index.php?/topic/98035-wall-closures-support-for-cavity-closers/
  3. Now that we have the very welcome Wall Closure feature I would love to have support added for 'cavity closers'. 'Cavity closers' are used in cavity wall construction around openings in the walls—in particular windows and doors—to protect against water ingress, damp, heat loss, condensation and smoke. In some types of construction they're also used to inhibit the spread of smoke and fire in concealed spaces; in the UK their name changes to Cavity Barrier in this case. I'd like to be able to show these on our 1:50 floor plans and sections. See also: https://forum.vectorworks.net/index.php?/topic/98080-new-tool-for-modelling-cavity-barriers/
  4. No I haven't had to deal with non-optimized Revit to IFC files. My RAM use has always been from rendering Sheet Layer Section Viewports. Each one eats up RAM and doesn't let it go. Eventually leading to the need to restart VW. I have no way to qualify this but there have been quite a few times in the past few years when I've seen people running into stability problems while we've avoided them and the variable that seems most plausible to me is the amount of RAM we have.
  5. We're not getting anything with less than 128 GB RAM, which puts us perilously close to the price of a base model Mac Pro. So we're waiting to see what the new Mac Pros look like before we make a decision. I wouldn't recommend a configuration with less than 64 GB, but it depends on what kind of workflows are used.
  6. Some on this thread are, including Mark Aceto:
  7. Not specifically, no, but what is it about them that the current window tool can't do? Maybe I have a more generic wish covering it?
  8. @Matt Panzer @Gunther @SteveJ @JuanP sorry to loop you in but I don't know who else to ask. Can you bring this thread to the attention of somebody who can address it?
  9. What I'm finding now is that we can't even upvote any answers to our own trouble-shooting posts at all. The forum is starting to feel decidedly broken. I've added items 5 & 6.
  10. Okay, after discussing and understanding things better, I've completely rewritten the original post and added some examples.
  11. Wow, that looks amazing. Assemblies are geared toward the Aussie market but it wouldn't need the assemblies to be useful.
  12. For the Timber configuration it's not just the default, it's the only setting. The inside edge of the Timber sill aligns with the inside face of wall, as does the outer edge of the Stool Nose.
  13. Ah yes, good one, thanks for reminding me of this one Tom. I added items 2 and 5.
  14. I've reworded item 1 and 3 and added items 4 and 7. Are there any other problems I've missed with the window sill? I'm going to discuss it with our distributor very soon.
  15. Is this Onshape moving into architecture or has Onshape long been able to do this?
  16. We give each field of the BIM file name it's own Sheet Data field in VW. Sheet Number in VW is then reserved for the BIM Number field only. Our file export options then look something like this:
  17. That was it, did the trick for me. Must have had that turned off already in the very first file I successfully turned off Legacy 2D. They need to update the dialogue window text.
  18. Yeah I think we would get non-Apple displays so that's handy to know. Apart from the cost of the 128GB RAM version I'm also a bit disappointed by the Studio Display itself. If the retina display iMacs (which we have) supported target display mode we'd probably be running Mac Studios already. But at over 5 grand without a display I thought we might as well wait to see what base Mac Pro looks like. At least then we could easily upgrade RAM and HD space later on.
  19. Very handy. Just missing Zeno's 43": https://forum.vectorworks.net/index.php?/topic/93360-mac-studio-m1-ultra/page/5/#comment-424964 Updated version of article here: https://bjango.com/articles/macexternaldisplays2/
  20. Agreed, but it's a mistake to think Apple do this intentionally to make money off dongles or some other two-bit scheme. These decisions are always design decisions about the device or the ecosystem; moving the industry away from a certain port or device, simplifying the number of ports, making a device thinner, etc. I've listened to dozens of interviews that shed light on these priorities. The look and use of device in its own right has always been put ahead of backwards or 3rd party device compatibility. This was even more acute under Jony Ives. I think his absence is the reason we now have Magsafe, HDMI and an SD card slot back on the MacBook Pro. The hockey puck mouse is another great example. Another of Jony Ive's mistakes. It's a great example because it shows just how far Apple would go to put aesthetic simplicity ahead of practicality. The original Apple TV remote fits into this camp too. Mostly this mode of thinking works out really well. My favourite example was when they moved the whole industry away from floppy disk drives (and toward USB) by simply leaving it off their new fandangled computer, the iMac. That was an extremely a shocking move to many, but it was absolutely the right decision and it was one of the reasons the iMac became what I think is the best desktop computer ever made.
  21. Why would they save HDMI 2.1 as an incentive for a later model when they could use it as an incentive now? I've followed Apple pretty intensely for over 25 years and it just doesn't operate that way. It's not in its DNA. You can definitely argue that Apple has made some bad design choices here and there, but that's just it, they're design choices. These are not choices made by bean counters. Exactly. It's trade offs. All design involves trade offs.
  22. I have a very hard time believing Apple went with HDMI 2.0 over of 2.1 because of cost. Any cost difference is going to be miniscule. It's more likely to be a technical reason, such as bus bandwidth limitation. Apple TV 4K ships with HDMI 2.1 for instance.
  23. Maybe I'm recalling it incorrectly but I seem to recall that there was a message when I imported things last time, telling me Screen Plane objects would be moved to Layer Plane because Legacy 2D was turned off in the file I was importing into. Anyway I definitely didn't get that message when I followed the steps in my post above.
  24. Some resources can be. Symbols for instance can have objects that are set to Screen Plane or Symbol Definition. To be fair, I've just tried this on another existing file and failed. I removed every single thing from the file that I could think of: resources, saved views, layers, classes and I purged everything (including special formats) for good measure, but I still could not turn off Legacy 2D. The alternative is to start with a blank file with Legacy 2D off: 1. Open a blank file (and turn off Legacy 2D if it isn't already). Update any other documents settings to your preferences. 2. Open original file and import all its resources into the new blank file. 3. Import all Design Layers from original file into new file with Import Layer Objects option on. In theory you should now effectively have a copy of your original file, but with Legacy 2D turned off. ....however, I've just followed these steps and what I'm finding is that despite Legacy 2D being off, objects that were previously Screen Plane objects are still behaving like Screen Plane objects. If I go into a 3D view they disappear. Also, if I select them, the Plane dropdown menu in the OIP is blank, and if I click on it there is an option to change the object to Layer Plane. And here's the kicker, if I then turn Legacy 2D back on in the resulting file, those objects appear on Screen Plane (in the OIP) and I can't turn Legacy 2D off again. I'll report this as it sounds buggy to me.
  • Create New...