Matt Overton

Yes and yes please.

@JimWIt might be a good idea if merging threads to note the merge/bump. Looks like a bad necro otherwise.

It would be great if we could overide the class attributes of multiple viewports at the same time from the class edit/visiblities dialogue box. Or some other way of bulk setting a presentation look for a class vs a working look. ie turn-on dropshadows in viewports but off for the working view.

Agree with @Markvl no need to delay. Energy tools are likely to stay useful but not valuable for a few versions yet so best get on with useful tweaks. While care is taken on the more valuable code compliance.

How would this translate to printed output? If I need to leave a note for the team I probably need to tell the builders. At the same time really see if value in being able to see those notes by touching the object in any view. Sorry a bugbear of mine is how much information Vectorworks BIM requires to work that doesn’t translate to deliverables.

Or more times a year and say hosted by the regional distributors to get a border spread of customers and users.

Or could be higher as they don't take in to account the air skin in the outsides of the walls or any internal cavities.

Should be sum +1 as neither original proposes get a vote on their own thread but are clearly supportive. Also might be good if we get in the habit of treating the Original Post as a feature brief and bring in relevant summaries of the on going discussions so someone jumping in to the thread has a nice bullet point summary at the start. Also mean as this post is pinned to top of page you could jump to last page(s) and still be in the loop.

New files a still get a clear stutter like it has returned control but then grabs it back. Neither pause is a enough to beach ball, both are worse if object has transparency. Problem gets distinctly worse as the you work with files with more geometry on another visible layer. Even if I add a space for the first time to a reasonably complex file. I get a clear stutter. Testing a number of files that had spaces pre service pack 2 and stutter becomes greater to the point of beach balling.

Space objects are now joy enriched with many many beach balls of death. Any change double beach ball about 8-10 secs each. so 20secs inactive per change.

Also this dialogue box is most unhelpful...

Unless there is a change in the agreement and we continue paying money, why do we need to check this box and hit a button each update?

So we will see Vectorworks drop these horrible 3rd party tabs in favor of the platform provided ones?

Yes that answers my question. So no reason to think there might be a reporting skew.

Certainly would be better if we had a tool similar to Handrails that made a group and calculated the mitres based on a 3D Path.

I was thinking right yet somehow still typed left.

To me the only negative about the image on the left is it to far and could handle being richer, even if it was just adding an on/off button where suitable. Yes take this very strong Yes please for a better, cleaner, clearer and easier to get to the right place sooner.

I thought Windows Crash report wasn't as streamlined as MacOS so it didn't have the board spread of users like the MacOS version has? How does the unique users on each platform compare from say the update system compare to crash reporter?

Framing members with a custom Profile work are my personnel preference. Easier to modify after the fact.

Procedural Components would be useful here. I mean we normally fake these if we need from by duplicating the roof to create a thin roof above and replacing the shape with a double line polygon along the required edges. If we had Components that say allowed an x mm wide band on selected edges or y mm wide bands every z mm in a certain direction. We could build maybe 80% of this function in to Roof (,wall and slab) Types. Very few components are monolithic as implied by the current system.

I haven't played the Data Visualisation much yet but could it be used for LOD filtering or indeed any sort of "visual" filtering based on a record value? So attached is Proof of Concept based on being able to control if doors and windows are open or closed by Viewport. Uses a record with pop-up list of options, record is attached to versions of the object to distinguish instead of classing. Data visualization then un-draws the ones not applicable. "Small" snag only works hidden line all render modes bring back all geometry and render them. Still could be promising for LOD and potentially versioning objects. Only a proof of concept but looks like records could be a very powerful way of controlling visibility when we don't need full function of a class. If they had the right internal support. PoC Openings.vwx PoC Openings.pdf

I think Vectorworks handles this better than some of the others. Well to be fair most of other experience is with offices in transition to ArchiCad including being trained. The thing that struck me from training was the overhead you mention to get to a workable base. Talking to people in those offices 5+ years down the track they still had the same overhead. Also convinced me that using VW better was more valuable than changing (but this is purely personal). With Vectorwork a few settings many of which we now have have embedded in our templates much of the early 3d comes cheap and you can set-dress as needed to suit just the views, design exploration and detail that are going to get bills paid. Have to admit getting people in to the mind set of set-dressing the model to suit just the view they are concentrating on can be tricky but very valuable as it really does help defer model building activity down the track to where it's billable. As digital Carbon comment what really helps is shamelessly reuse of previous work. Keeping the work organised so you can get what you want quickly. Making symbols and types early as in as soon as you think they might be reused.

Hoping one the ongoing development projects is to move view state out of the model state this would be a good move towards that. Also ould be good if we could set a third state per object for use in presentation views. Then we could save some of the set dressing we do for presentation views.

From chatting with other users I'd say depends entirely on version. One version the Mac runs better next it might be Windows but could equally be Mac. Go with the system you feel more comfortable with.

To me it would be better if they stayed that way. The dial should be on the view not the objects. The problem is the current system can't defer the creation of geometry until it's needed it has to create (and recreate in full) every time the object is touched. So would end up slow and unworkable if implemented in the current system.