SteveJ

We are always energized by the forum. And we find motivation and incentive from all the feedback we see. But every now and then... we do enjoy a gust of wind like above... it can help fill our sails. We are here listening and trying to serve you and your design as best we can. Thanks to the entire community!

There are reasons. Many reasons. Vectorworks is a very complicated piece of software and we are always looking for ways to accelerate these updates. That is why we just increased the update (SP) frequency. In a sense there are no "minor" bug fixes. We need to take time to build confidence that any particular fix does not introduce a step backwards.

Has anyone here been disappointed with Apple Silicon? (16GB limit not withstanding)

Recall the single M1Max is quite fast - some might chime in here. We will get our hands on ultra asap - and share what we find! I would not expect it to be slower than M1Max. and you have the 128GB option. If you currently use 128GB for your projects, this is very nice news!

Hello all interested in Native Apple silicon! The publish command is certainly a lower bound for performance improvements. The multi-core and GPU/Metal/DirectX performance wins for Vectorworks currently occur with the everyday, every minute, every second workflows of changing views and navigating your complex design. Switching and redrawing in Top/Plan, switching to and navigating 3D views, working with large files with large number of classes and more. I think/hope those using Apple silicon already can remind us of the these wins. Concerning 16GB and the frustrations updating multiple viewports in batch, that is one of the biggest offerings of ultra. Updating multiple viewports with complicated section cuts does push beyond 16GB. With 32, 64, and now 128GB, that limit is lifted. So four points to add at this point: The memory limitation of 16GB has a new upper bound! The real multi-core and GPU benefits of native Apple silicon are not well celebrated with the publish command - those of you already using Apple silicon might remind us of the experience you see. (16GB batch update limit not withstanding) This discussion thread will collect more benchmarks as we and others get hold of a shipping Mac Studio. We will be able to report on workflows other than the publish command. Apple silicon is great technology. And, don’t forget, much of what we do is cross platform. Ultra and UltraFusion are quite compelling. Here at VW, we are constantly working to improve Vectorworks to take advantage of all this new technology. We hear and understand your concerns and are laser focused to continue to improve your workflows and experiences.

Thanks to this Forum and the entire VW organization as well! It does take a community!

Thanks for the insight Maarten. We can look at CallDefaultTool mechanism if this turns out to be the issue. @Stefan Bender We may need to get hold of the Window and the info that lets us run in debug mode. Perhaps this info and attachments are attached to a previous build? Anyway, thanks for digging in on this.

A great example of a shortfall in user experience. I would think this should not be a job for the Window tool. I would expect this be a fix in for the main application/SDK to make. I will look for a way to get hold of the CW Window tool. Or, @Vlado, Perhaps we can find a sample tool that shows the same behavior

Is this a regression?

Got it. Understand. I will ask @Vlado about the Insertion tool code path you are using.

@Stefan Bender Are you asking about the "Full Screen Cursor" when you mention horizontal and vertical guidelines? Perhaps a quick movie to confirm?

Most likely the next version.

The advantages are difficult to compare Mac to Win. That said, Direct X and Metal will improve VGM performance on each platform. Continued move to more multi-threaded processing, as with 2022 hidden line, will bring performance gains to each. What is different in 2022 is the gains provided by Apple Silicon. The performance gains from this technology obviously favor the Mac

They are not. A high quality release of this feature was not in the cards for this release. We will continue to work to deliver this solution in the next appropriate release. Please follow the roadmap and contribute to the discussions as we move forward.

Hello Willofmaine. Hello others following this topic. I would not classify the current behavior as preferring unrestricted snapping as much as preferring to NOT to force working plane snap. As noted, VW even goes so far as to turn off the Snap to Working Plane automatically as tools are changed. I think VW is “afraid” to “leave the working plane snapping ON”. That is not to suggest that VW is behaving as it should. This is just a quick attempt at an explanation for why you have seen inaction here. Let me apologize for being timid in this area. I think Vectorworks can consider being bold and working to improve this. To do what you seem to suggest. Can we explore ideas together and see what VW might be able to do to improve here? To get this started… What would we call the view that we are talking about? The workflow context? Can we call this Orthogonal With Working Plane Perpendicular to View? OWWPPV (we could rename this) …Following Will's comment about being "backwards" , what if VW automatically turned ON the snap to working plane when entering OWWPPV? You could simulate this now by constantly pressing the keyboard shortcut while working in OWWPPV. This might provide behavior Will describes as "RESTRICTED to the screen plane". Could something like this help? Thanks in advance. Steve