Matt Overton

Would be handy for groups as well, maybe even other container objects. "By Container" would be great if possible.

Maybe over simplified but from what I've seen... Vectorworks lets you get going on less information and present that information at every stage. Con isn't as helpful with automated tools. So as you get more advanced you'll find yourself resorting to modelling by raw objects much sooner. ArchiCad (at least from discussions with users and training) has a much higher overhead of information it needs before it'll produce something useful but the build in tools will take you further and have much greater flexibly. If your a student then use many. Or look at the companies you want to work for and see what they use.

1,2 & 3 Yes please regarding 4: If there was a unified list making it easy to go tweak then hopefully that list would :- a) carry between versions so we only get hit by new options not have to rebuild every option after upgrades. b) make the list an office standard. My points seem to followed 2 themes - Too much interface clutter. Important things hidden, related things too far apart, unimportant things prominent. - One for you, one for me. Too much information repeated as VW requires it for modeling but doesn't display it.

or "There is only two ways to do a job. Right and again"

helps to create some fake sun light objects for the building faces that aren't likely to see any sun. Generally use line and shadow here with lines set to 0 pixels.

Elevation marker isn't relevant as it's completly independant and useful for one off special annotations. (if it can linked to objects like a dimension better still) Keep it simple. As noted by Jonathan above Viewports should be able to render level markers. Which levels show controlled by layers dialogue. Graphics of the markers by a document setting or a viewport style. Storey's dialogue stays the one place to get the information right.

I'd like see project sharing move to a full version control system. Delta saves would add to that.

I want to up vote this agian.

Yes we use BIMing to producing elevations, sections and 3D's that improved client communications greatly. As other have noted elevation markers can report the correct elevation but if the model changes slightly (or not so slightly as per attachment) marker does not change. In this case comically obvious, in the case of a small change dangerously non-obvious. Is also reliant on snaps but doesn't link to points with a visual marker. If the first goal of BIM* is "model once --> view thrice" then this is not BIM it's a liability. In the case of common levels we note each instance makes the problem exponentially worse. Would be very happy to be proven wrong and there to be an existing solution, but the more I look it the more it problems it presents.

Benchmark tool doesn't track changes made to heights made in the Storeys or layers. So it's still effectively just a manual notation that can be entirely incorrect if not treated with care. Worse it creates multiple instances that could be wrong each reliant on hitting the right snap point. Ok for single referencing but no good for general dimensioning. Using a line of heights symbol at least only gives two locations to co-ordinate. Having Section views directly report heights from Storey and Layer configuration would reduce this to one, distinctly correct location.

I hope I'm not going to have to bump this when we are 6 versions past the obvious need for it.

Not that I've found, so really just tagging myself in case someone has. It would be useful.

So it's summer in Australia the last thing anyone here would be thinking about is Hydronic heating. Well except me who searched Vectorworks Resources Library from with in the app to find radiator and fireplace symbols for a farm house renovation. Even found what I was looking for without a web search. Now I'm seeing ads everywhere on the web for Hydronic Heating. Just coincidence?

I don't mind the nested dialogues, specially the new style list down the side. To me it's certainly preferable to multiple dialogue boxes. Do agree it could be improved for faster navigation from Object Info Palette and will conceed i can see the appeal at times to have direct links. Still why can we have the best of both worlds and head towards an Interface the is rich as required, spares when not. To me it could be in the form of a universal setting button. Main part of button would take you to nested dialogue, a small drop down triangle would let you pick which panel you want to jump to quickly to a panel. Having an option to expand the list into individual buttons as demanded (say option-click drop-down part fo button). As for other suggestions for site model, yes it could be much improved.

A new offender to add to the list of interface missing the mark.

Why not go further and have Viewport styles like plug-in styles? They could link Class set up to the style and then we'd have one central place to fix issues.

Interesting a lot of people have clearly dumped the snap hot keys for interesting things to them. They are right at the sweet spot of the keyboard. I do hope this sort of study is because VW might be brave and do a clean sweep of the keyboard shortcuts. Throw out all the old assumptions make every command earn its place. Make the pain worth it.

Yes sorry read that the wrong way. So how many default keys have a high percentage of remapping?

http://blog.vectorworks.net/inside-vectorworks-gaining-insight-from-data-analytics?_hsenc=p2ANqtz--IJ-Bme-SiM4Hg_MfRSCCWUYqmSyh1-NMxlktYCaKc-R5QGTpkVxj_uhBgrE1SnuAyEtVLqci7afk025dGZi7e8X7PK8fLVxQ8L4don5FGlq9rhzs&_hsmi=60451065 So "M" is the most popular true key to press in the new Vectorworks. Does it still hold up if you discount all the times M is hit again after the first M without hitting any other key other than to maybe google why did that happen? Maybe needs a voice recorder to check no one said "what happen there". All up I'd think this was a bad metric if mode is so good why are people switching so often?

So one brilliant feature of Vectorworks going way back to the early days is being able to edit numerical values with standard math operators. If you tab between fields the existing value highlights and gets replaced by what you type also very good behavour. It would be great if typing a standard math operator (+,-,/ & *) on a highlighted field caused the existing value to be retained. Avoiding the need to tap after the the existing value and allowing as to tab->math a series of fields.

Why have a button at all, or just one button? a) The whole orange highlight could be the button. Add the text as repeats in the band so everyone knows. b) Move to left agian just inside the orange band instead of wrapped text. (Top left corner seems to be freer space to me. c) Or b+ - Change to a jump bar like this one in xCode. Allow us to jump back anywhere in the chain but also say open up other faster naviagtion. So If a go into design space of a viewport the next part could be just the layers active in that viewport. If we transverse say 10 level deep to fix one item for a sheet we want to publish we then have one click return.

With screen capture you do hit an issue with long object info palettes. The space object above runs off the bottom of the screen requiring two images and stitching to get whole thing. Print option would capture the whole whole thing in one step. Also with multiple panel dialogue box it would hopefully capture each panel as one page in one step

Yes and once similar thing are grouped allow them to be collapsed and out of the way. It's funny to me to show position handles on a Viewport given this something I'd change on maybe 1 occasion a year and generally only as an attempt to fix a quirk. It could easily be collapsed for a Viewport but ever one is different. So a way to set if collapsed or not by style would also be good. So looking at a bigger offender here is a design review of the Space Object. Showing how good collapsible sections could be.

I know this pain... Really needs better solution.

Or just improve Hidden Line. Vectorworks already has enough improved versions of things that have been given new names instead of just replacing the broken function.