Christiaan

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.

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

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.

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.

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.

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.

Ah yes, thank you guys! Sometime I need my hand held 😬

Been there, feel your pain.

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

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.

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.

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.

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

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?

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.