Josh S

Hi all, When we start any new project we bring in the OS tile which is in dwg format. Typically, we import with a prefix then go through and turn off or delete layers we don't use, as well as change the line colours to suit our preference. I want to try and stream line this for both our OS imports but also a few other things we bring in, for example standard details etc where layer/class naming is consistent. Example 1: OS file (dwg) has a layer (dwg version of a class) called "contours" when imported this comes in with the line colour and fill as back in the class manager and magenta on the drawing as an overwritten line colour with the fill on "none". We would like this to come in on a Class called, "digi-contours" with a green line colour. Now the "digi-" can be set by setting a it as a prefix or by using a mapping set. However, if I set a template file with this class already created (with the line and fill as wanted), the import will overwrite the line and fill settings. Therefore we have to go back through and change everything again. This is time consuming and frustrating, particularly if addition OS data gets bought in later into the project. The current work around of exporting to a new file then bringing into the existing document by using the new layer > import geometry option creates Georeferencing headaches. Example 2: We are looking to use https://detail-library.co.uk/ to support our existing standard details. They have kindly shared tips for import settings, however we would like to go one step further and blend their classes(layers) with our standard layers. Again, using standard the import layer mapping, i can change the names, but the layer settings all revert when i bring it in. Can anyone help? Is this a workflow issue, or a setting issue? many thanks, Josh

Ah I missed the in "the resource manager" bit!

I think I am missing something... When creating a window style, is there an option to change the Class to "by instance" for the plug-in options, or alter existing window styles to be by instance, rather than by class? thanks!

I know the ability to group layers is frequently requested, but to add to the request for updated layer organisation, can we get a column that states the elevation of each layer? As crudely shown below! Whilst usually, knowing the storey they related to suffices, sometimes it is useful on projects that for example are split level blocks of buildings to have a prompt!

It's maddening that there is no way of doing it. But to be fair even if we could add a "-" to allow a heirachy system like the classes use, it would be an improvement. Being able to link them though would be great too, although I guess that is mostly done through saved views and editing from within the viewports? This is our current work around to try and keep files organised. We would welcome any tips on improving this?

Have you a link to this wizardry?

Unless I am mistaken there is no current way of using the autnumbering tool to make stairs start at any number other than 1. Ideally, this should be customisable so the stairs from Level 1 to Level 2 will be numbered 1-16, and then the stair from Level 2 - 3 will be numbered 17-32 and so on. Presently we have the tedious task of numbering stairs manually, which is fine until the number of treads or even the depth of tread changes and everything needs adjusting! I do appreciate stairs can just be numbered from 1 for each level, it just doesn't comply with the Directors preferences!

@Christiaan Bloody clip cube! cheers for this, I was just choosing which window the PC was about to go out!

Hi @Wes Gardner, that works well when creating the ceiling from and extrusion. I could use the cut extrusion, to create a polygon the correct size. Create a slab from that, giving me a correct slab for the ceiling. But I suppose is there any benefit at that point to using the slab for a ceiling over a simple extrusion? thanks, Josh

Hi, Anyone able to point me to a tutorial on creating a ceiling in an attic space? I can fudge it and get it sort of the right size but it's a b it of a faff. There must be an easier way! It's probably something simple I am over looking? The roof is made up of roof faces and the ceiling a slab. Ideally I would be able to get the slab to intersect with the soffit of the roof. TIA, Josh

Thanks for the suggestion. I had a look at their products and downloaded one of their doors. They do have vectorworks formats but they aren't quite as friendly as vectorworks own doors. They are more just 3D extrudes put into a symbol. Still, better than starting from scratch!

I assume this hasn't been addressed in 2020 vectorworks?

I quite like how the stories work. Really handy when sketching out designs and fiddling with levels. That said, they probably are less beneficial for two storey development. I'm new to vectorworks (and architecture!) this year after working as an SE Tech using AutoCAD and Revit. I swear, if you could smash Revit and Vectorworks into each other hard enough, you would have some great software!

Yes, likewise, I have to delete the wall peaks to reset it and get FWtO to work. I've started changing how I create my upper floor walls also. Previously, I used stories and walls would go "top of slab" to top of slab over". for this I would create a "top of slab" level on the upper most story, or a false story. Now on my upper floors I tend to set walls as from "top of slab" and the upper to wall height. Then use FWtO to get the correct elevation for the roof height. This seems to make FWtO much more consistent.

@Wes Gardner @David S Thank you for the comments and sorry for the slow reply. I'm struggling to upload a file to this at the moment - I have tried increasing the overhang to see if it resolves it but it still is happening. I've worked around it with negative embedment depths. I'll come back to this when I next come across it!