Boh
-
Posts
1,717 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Articles
Marionette
Store
Posts posted by Boh
-
-
PM me if interested. Thanks
-
Are you trying to place the viewport on a design layer or a sheet layer? To reference an external file with a viewport, you need to create the viewport on a design layer.
-
Yes I have this happen occasionally too. I've found that a restart of VW is usually required. I'm not sure if it's been flagged to VW but it's been going on for a few releases.
-
The eyedropper tool has a "Pick up sets defaults" option. When checked the tool will pick up the settings of an object and make those the default setting for the tool that created them. For my templates I have done this for all my commonly used tools so they are already pretty much set up for me. That said, for some reason this isn't working so well on drawing labels, i.e. the preferred label style isn't not being set as my default.
Another option which worked for me is to open a new template drawing, select the drawing label tool, set the tool to your preferred settings incl style, create a label, delete label and save the drawing as a template to override your original template.
I'm not sure if this works for new viewports where you have the option to include a drawing label, but at the moment my new viewports have my preferred label.
Note that if you use the Pick up sets defaults option then be sure to not leave it checked once you have your tool defaults set. If you do leave it checked then you may find your active class changing when you use a tool.
Cheers
-
1
-
-
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.
-
4 hours ago, line-weight said:
There is a kind of cheat in this situation: press B on your keyboard which will give you a kind of X-ray zone where you can see things in wireframe. If wireframe can see the corner you want, then you can usually snap to it, even if you can't in shaded view.
Did you try that? Alternatively try changing the rendermode to wireframe.
-
2
-
-
On 8/22/2024 at 4:06 PM, Milindsinh Solanki said:
Could you please guide me on how you created the red hatches that offsetting out from the wall?
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.
-
21 hours ago, Itchy said:
I did quickly try Bohs work around having the DLVP on a separate layer, but then realised stacking on the notes wouldn't work, so am now having to move all notes to the new layer also. Hopefully, it works...
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.
-
2
-
-
On 5/18/2024 at 9:39 AM, Michael Creason Audio said:
This helped me greatly and I learned a whole new way to find things. Thank you for this - I was able to find what class my errant drawing labels were on in seconds.
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.
-
1
-
-
10 hours ago, markdd said:
You can make Referenced Classes (but not Design Layers) locally controllable by using the Source Buttons in the Class Dialog of the Referenced viewport. This will make any Classes controllable specifically from Sheet Layer Viewports.
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.
-
1
-
-
-
-
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/
-
2
-
-
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.
-
2
-
-
6 hours ago, line-weight said:
If you want to make a whole bunch of classes invisible for example, how do you do that? Do you go to the classes organisation palette and switch them all off manually each time?
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.
-
12 hours ago, line-weight said:
I use saved views all the time when in design layers - to do stuff like switch between building storeys, existing/proposed versions, and all sorts of other class or layer visibility setups. I don't think VW would be usable otherwise - the alternative would be manually changing multiple class visibility settings each time.
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.
-
1
-
-
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.
-
7 minutes ago, line-weight said:
It already feels a bit dangerous that I can quite easily alter a bunch of notes scattered throughout a file without realising it. The ability to mess up multiple projects in one go (and maybe only realise some time later) - yikes.
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.
-
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.
-
3
-
-
On 11/14/2023 at 10:42 PM, Amanda McDermott said:
we often create a key using classes - which works really well because we can use class attributes to ensure the key is up to date. But it does result in invisible key elements sometimes when we've been working in another view and then go to the sheet layer, if we don't remember to switch on all classes before publishing.
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.
-
2
-
VW2024 architect license for sale
in General Discussion
Posted
Hi all.
Boosting this post. Just to note that we have had this license for some time so will work with many previous versions of VW. Keen to sell.