line-weight

As far as I can work out, the choice seems to be between some free stuff that is very limited and rather unreliable, and paying for quite expensive libraries. https://forum.vectorworks.net/index.php?/topic/44878-3d-plants-options-for-the-confused-architect/ Twinmotion is an external application, not something that works within VW. So you have to export back and forth. There is supposed to be a live link feature but it doesn't work properly and isn't maintained. Every time I try and add plants, I run into some problem or the other.

And in the currently existing "horizontal section" workflow you basically do have that option, whereas you don't with the top/plan approach.

Although I agree (from an architect point of view) with much of what you say about the purpose/interpretation of drawings, I would prefer that VW moves towards a more literal cut plane, which is what the "horizontal section" workflow is all about. It's still completely possible to choose to over-ride the literal cut with something more symbolic where that makes more sense. There are situations where the "literal" cut plane is more communicative than what top/plan would provide. For example consider a stacked wall buildup where the lowest section of the wall is plinth-like and thicker than the main part of the wall. I'd want to draw the section through the thinner part with the top of the plinth part visible in "elevation" below. Especially if that plinth had some kind of shelf or ledge incorporated. That's how I'd have drawn it in ye olden days by hand too. Top/plan struggles with this kind of thing whereas a horizontal section draws what I want first go. This is just one example, there are many others. I find that drawing with a literal cut plane as a starting point gets me much closer to the kind of control over what's actually drawn, that I had when I used to hand draw, than fighting the top/plan system does.

Horizontal sections are the way forward!

@Rick Berge I'm trying to do this in VW2025 but am not sure where to find "Draw all other objects: Normally". Is it the button that's now called "show"? If so, selecting this does not seem to allow the "other objects" to fall back to the viewport's class over-rides. At least in my case, where I want to use data vis to change the texture of everything in a certain layer, while having things in all other layers fall back to the viewport's class over-ride settings.

"Parent" styles, as suggested here: https://forum.vectorworks.net/index.php?/topic/119602-the-need-for-a-parent-style-to-rule-over-sub-styles/#comment-519002 would also make them a lot more useful. For example - I might have a file with a lot of viewports that show "as existing" or "as proposed" conditions. I will tend to use layers to distinguish between those. There will be a particular combination of layers that show the model in "as proposed" condition and as the project develops, new layers might get added, or I might want to change that combination in some way. It would be useful to be able to change the layer visibility setup in a viewport style and have that roll out to the tens of relevant viewports in the file, rather than having to go and do them all individually. However... I might also want to use a viewport style to control the graphic appearance of (say) all 1:50 section viewports. There may be many such viewports in the file but some of them are "as existing" and some are "as proposed". I can't currently do both things using viewport styles. Either I choose to control layer setup via style, and graphic appearance manually, or vice versa. Or... I have to create two styles (1:50 sections as existing, 1:50 sections as proposed) and each time I want to change the graphic appearance of all 1:50 sections I have to go and change the settings in two styles. And if I want to change the "as proposed" layer setup I probably have to go and change it in multiple vport styles too (1:50 sections as proposed, 1:100 sections as proposed, GA plans as proposed, etc etc) This is quite a similar problem as we see in other object type styles, like wall styles.

Viewport Styles are potentially very useful but there are various things they can't control which means that I can't use them for certain purposes. To start with, a couple of things that it would be useful if they could do: - Control class over-rides independently of class visibilities (note that I can transfer these things independently between vports using the eyedropper tool). In other words, I might want to have class over-rides determined by style, but class visibilities determined per viepwort. - Controlling which lights are turned on or off. There are other things, which I'll add to this thread as I think of them.

You should be able to click on the relevant points in the PDF even if you can't snap to them. I am quite often going through this process. You can zoom in to get your mouse click as accurate as is possible. If the PDF includes a scale bar I start from there. I'll click on the start and end of the scale bar ... zooming in as necessary (if it's rasterised then that means zooming in enough to see pixels and clicking as close as I can to what I judge to be the midpoint of a line). The fun starts when you realise the PDF has been scanned at some point and has ended up scaled slightly differently in X and Y directions...

What is the reason that you want to create a "new" model rather than just continuing to make further modifications to the original one?

I have had similar experiences trying to use the built in satellite imagery or maps - frequent failures to download or other errors. It shouldn't really be necessary to fiddle about with resolution to make it work. This part of the tools (image download from server) needs to handled much better I think. As it is, it can be very frustrating, especially when it can be a bit difficult to understand what's going on with the GIS tools anyway.

Ok, I see. It may be that you don't use the Structural Member tool in a way that is affected by its limitations. But I think there are many of us who do. Most of these limitations aren't necessarily bugs - I would call it something like incomplete implementation. And there are a few threads (like the one I linked to above) that outline these in quite some detail. This of course is a separate process from the bug submittal one - it's users letting VW know that the tool would be greatly enhanced if some time could be spent improving it.

Another example of an existing feature that desperately needs attention is the notes database & manager.

If this is the case, then the problem is exactly that: fixes and improvements being defined as "low priority". They should be a higher priority than the implementation of other, new, features.

https://forum.vectorworks.net/index.php?/topic/90654-structural-member-usability-improvements/

Exactly this. And the structural member is a good example.

The new features are fine and good. The problem as ever is the lack of progress in fixing all the "old features" which most of us would use every day if we could.

This was actually confusing me the other day and I wondered if something had changed in W2025. I had problems with a SM imported from a VW2023 file and I could only get the texture to work after creating a new one (might still have been user error though). You can set "by class" here in the SM settings circled in red. It took me a while to find this because the "texture" column circled in green doesn't offer "by class" as adirect drop-down option whereas "attributes" next door to it does. You have to click and open a dialogue box and find the "by class" button at the top.

Have submitted.

My guess is that @Scott Schwartz, AIA is thinking that the suggestion is to use a bunch of 2d SLVPs on a sheet layer rather than a bunch of 3d DLVPs assembled in 3d on a design layer(s).

And, not having used the SM tool in anger for a few months, this is tripping me up all over again. Had to come back to read this thread to remind myself how to stop SMs auto-connecting when I don't want them to.

It's very frustrating that we still can't lock the slope angle whilst adjusting the span or length of a structural member. The most simple operations become much more convoluted than they need to be.

Another question for @Matt Panzer I think.... is this a bug?

Another version, now with viewports 10 & 11 added. This is the system I am going to use for now I think. I have to accept stacked viewports, and some manual work done in annotation space. I may get around to making this into a proper VE submission at some point...however I've already spent rather a lot of my own time messing with this and now need to get on with the actual drawings that earn me some fees for a bit. I think all the info is here in this thread for anyone who wants to look at what does and doesn't work in HSVPs as far as site models are concerned.

That explains what confused me then!