Boh

Maybe I don’t fully understand the query but why don’t you simply change the font size of the stake? The only issue I see is if you want to have the same stakes in more than one viewport of differing scales.

Did you try that? Alternatively try changing the rendermode to wireframe.

They are simply polygons in the viewport annotation. I trace the walls, often by adding together a bunch of rectangles, offset the polygon 50mm to create the overlap, then set it to my demo-hatch class which is a class with no line and the red hatch fill. It is manual and 2d but really quick and easy to edit for revisions.

Just to note that the recommended workflow is to place notes in the sheet layer viewport annotation rather than on a design layer. That said there are valid reasons to not do this.

A work around might be to use the custom tool command to create a series of scripts that insert a callout with predetermined settings. It would probably need to be set up to insert a keynote saved as a symbol which would turn into a plug in object on insertion. It would have to accommodate different scales so the font size and leader lines stayed consistent. Could take some setting up but once done the scripts would be saved in templates and each style would be one double click away.

This this is a bit of an issue if you realise 5 issues later that one drawing wasn't included. You need to delete the 5 issues and their revisions, include the missing drawing, then redo all the possibly myriad drawing issues/revisions complete with revision notes etc. You would either spent potentially hours doing this to get an accurate drawing register, or just do it manually. This has happened to me several times and it would be good if this could somehow be improved.

Very useful indeed. If you wanted to go further you could add additional columns to your drawing label report so that you could control the properties of all the drawing labels in your file from the report. The report can then be exported to a template file to use in other projects. You can create similar reports for most other parametric objects. Reports have a wide range of applications, they were a big learning for me and really opened up the software to more than just a drawing.

I've had issues with cropped DLVPS. I try not to crop them and found they worked better. Perhaps use class visibilities to remove objects from the DLVP instead? Though this technique is not without it's bugs also.

I never knew this. Thanks for the pro tip! I played around with it little and it looks like if the class(es) you want to edit in the referenced file are not in your working file, then changing a ref vp class to use the document's class definition imports the class into the working file. You can then edit the class in the working file including using sheet layer vp class overides. Very cool. The only caveat is that the class is then referenced, so if you edit a class in the referenced file then those changes are brought into the same class in the working file when the reference is updated.

Hi @LewisFegen. Sorry, no we no longer require staff for vectorworks. Thanks for your interest.

License sold.

You might find this keynote legend worksheet useful for finding / formatting legends. I put it in this shared folder as for somereason I can't attached it to this message. https://cloud.vectorworks.net/links/4PhxMqfAa27Q4PHW/

There is a custom script that does this which I got from this forum years ago. I tried export it from my vw but the plug-in manager doesn't seem to be working atm otherwise i'd share it. Perhaps search the forum?

There are various ways to set up wall styles that might suit different projects. My baseline is to make a new style for each wall type of build up but I make sure to set all component and wall style attributes to use class attributes. This means I need a set of wall component classes which wall define the texture of walls with components using that class. My other baseline is to set the class of the wall core to use the wall class. This means for example the walls placed in a black “proposed wall” class will have a black wall core and the same style placed in a white “existing wall” class will have a white core. Using class attributes means that if I decide to change the texture of a certain finish, I just edit the class all wall styles using that component class will update. Another advantage of using class attributes is that you can use viewport class overides. So I’m one view you can have a pink wall and in another view of the same wall you can have the wall appear blue. In essence using classes along with wall styles provides simple modelling with flexibility whilst providing global editing capability across multiple wall styles. A project can easily get more complicated but as mentioned this is just a baseline.

I may do that, we might have 500 or more classes in a file but with hierarchical display they collapse down to just 14 sets of classes and each of those sets have subsets, so still a few clicks but easy enough. Other techniques are to select the objects you want to work with and group them, thereby isolating them. Or, once I have a particular view but I need to navigate to another one, I’ll do that with a second floating window so I don’t lose the custom view. There is of course the clip cube too. These are kind of workarounds and I probably should set up saved views more often but I’d argue that it ends up being extra file management time.