Jump to content

Boh

Member
  • Posts

    1,703
  • Joined

  • Last visited

Reputation

818 Spectacular

2 Followers

Personal Information

  • Location
    New Zealand

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi @LewisFegen. Sorry, no we no longer require staff for vectorworks. Thanks for your interest.
  2. 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/
  3. 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?
  4. 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.
  5. 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.
  6. Interesting that you rely so heavily on saved views, whereas we hardly use them. The difference is undoubtedly to do with the type of work we do and how we collaborate with others as well of course our preferred way of working. We have probably dumbed it down so that others can easily jump on a file, and I guess we could make better use of saved views, but in general we find saved views another bit of file organisation that sucks up time. They do come into their own occasionally especially when you need to quickly jump from one custom 3d view to another view.
  7. Agreed. Lately I’ve only been making project/file specific notes databases for keynotes and using the project notes database to keep the keynotes uniform. For standard call-outs I might initially draw the note from a master notes database but thereafter would tend to use a worksheet for global editing of standard call-outs.
  8. I've found that if I change a note in a notes database, I'll only be asked if I want to update the notes in the current open file to the linked revised database note. Other files with notes linked to the changed note will not change but just become unlinked.
  9. The notes manager was improved a few versions ago so it is actually possible to effectively update notes across a file using a notes database. That said, I agree with @line-weightthat it is a tricky tool to use. Not very intuitive. If feels like it needs to be upscaled and rethought so that can be effectivley and efficiently used across multiple diverse projects. The actual notes database files are very small. It seems to me it would be better if each drawing file had it's own integrated notes resource, and accessed just like any other resource in the resource manager.
  10. I always put legends in vp annotations for this very reason. It doesn’t matter what the current file class settings are the legend will always publish. Added bonus is that any vp class over rides used will also act on the legend.
  11. I think there is a bit of confusion about this request. As I understand it, it is not about class visibilities in viewports, rather the class visibility settings when you are on a sheet layer. If you draw a line on a sheet layer (but not in a vp annotation), you turn it's class off, it will become invisible. So if you have objects on different classes on sheet layers and they are not all visible when you go to print then those objects will not appear in your print. This is a potentially dangerous situation, for example, if you issue construction drawings with important information not appearing on your drawings without you realizing it. My workaround to avoid this is to keep all objects on sheet layers on the none class. Any objects with a different class, if not in a design layer, go in VP annotations. So I fully support this request.
  12. Yes, with the project revision history worksheet, once you have done your revision changes you then need to add an issue for the revision numbers to show in the worksheet. The title block manager can be tricky to work with though I understand it has had undergone some improvements in vw2024. My process for what it’s worth: Open title block manager Go to select sheets and choose the sheets revise Add revisions Go to select sheets and choose the sheets to issue (if different from the set you’ve just revised) Add an issue Go to select sheets and choose all sheets you want to appear in the project revision history worksheet. Make sure “update project revision history worksheet” is checked. Close title block manager. Hopefully the worksheet updates correctly!
  13. Hey Tom. Yes, I’ve done that too, I just don’t like having to model both 2d and 3d in a hybrid symbol and I don’t like the auto hybrid tool. Also using an orthogonal top view means mech roof plant, terminal vents, spouting, chimneys, access ladders etc can just be simple 3d solids with no 2d portion. Much quicker for revisions.
×
×
  • Create New...