shorter

These are easy enough to create. There are simple preference toggles. e.g. Procedure OffsetDuplication; BEGIN SetPref(1,NOT(GetPref(1))); END; Run(OffsetDuplication); Wrap it up in a command, and add to the Workspace.

One day... I would like some way to define how a wall joins so it does not join on a mitre.

e.g. double click on 'auto display detail levels for design layers' should open document settings.

We have to apply them as veneers, but ideally they would be extracting volumes from the wall, so that we can take a section etc, or schedule volume of them and the wall.

Scheduling...

Caught a couple of people out coming from other softwares... "Why has Vectorworks deleted my drawing?!" "Because you have elected to delete all objects outside of page boundary" "But I am not on a Sheet Layer...?" "I know..."

Do that at a corner...

Same issue with rustication. If quoins are proud of the wall, you cannot make these go anywhere near the corner of the wall as a symbol. They certainly cannot wrap around the corner.

Quoins...

"...walls don't like symbols inserted in them with 2D components extending past the ends of the wall path" Why ever not?!!! This has always been a massive issue with Walls.

We do and there is. ISO19650... However, this only applies to issued data. It does not need to apply to 'work in progress' files. WIP file naming must make sense to the practice, but you need to have a reliable system to ensure the file you issue is named correctly. Again we have our standard which like our classes works as it's a 'guideline' and is flexible and agile enough to permit any file to be named in a similar manner. ISO19650 on the other hand, does not, but then it's not meant to because it's all about making sense of the deliverable, not the file that you link to an Indesign document showing a view down the road on the 25th april at 1pm.

Yes, but a standard is just a guideline. It has no authority. If you don't follow it when you are supposed to, yes, that can lead to some uncomfortable conversations. The 'standard' we were asked to adopt by our client, back in 2002 was the AEC UK CAD Standard. I set about setting it the office up to use it and took it with me as I set up my business and converted others to a 'standardised' approach to using Vectorworks. However, as one person out of the 100s of staff amongst my clients mention, not one client since, and not one consultant ever issued their DWGs using that 'standard'. So now we use our own 'standard' which guides staff as to the way classes should be named, and we use a mapping table to comply with which ever 'standard' is imposed upon us.

@Matt Panzer is nearly correct... 😉 Create a 2D symbol to take care of the 2D representation and then add the required 'hole' i.e. the 3D extrusion to model the recess. No need to take a horizontal section. Symbol is inserted on edge with 'half break'. I would upload a file but I can't at the moment for some reason, so here is the file. https://www.dropbox.com/t/yj4b6oFj1yYyfZfJ Always try to create a plan using a standard viewport otherwise you waste so much time waiting for section viewports to update.

The fact of the matter is there is NO standard. BS1192 AIA AEC ISO13567 all with or without codification from CiSfb Uniclass 1.4 Uniclass 2015 Uniformat Omniformat with and without abbreviation with and without 2D indication in the middle or end of the class name... i.e. the 'hidden', 'reflected', etc. The standards themselves are not standards. They are guidelines. The problem with not inventing your own standard is that you will forever be adapting to standards imposed upon you if you insist on always being 'industry standard', so you might as well create a standard that works for you. To demonstrate the mess in the industy at the moment, classes for a wall can be variously written, using recent and current 'standards'... A-G25-M-Wall A-G25-M_Wall A-EF_25_10-M_Wall A-EF2510E-Wall A-WALL-FULL AI-WALL-FULL-DIMS-N A-251012-T2N01B113B23pro A250

We can lock the position of a viewport but can still edit class and layer of the viewport, but not it's position. Very useful. Would be great if we could do this for objects?