Matt Overton

Offset duplication resets to standard offset on auto-saving. Offset-duplication will repeat the offset of the last duplication with the newly created object if you hit duplicate again (command-d). It will repeat this until you select a new object then revert to the standard 45º about 1m offset. With version 2024 update 4.1 release each time the autosave triggers the previously created object stays selected but the offset distance reverts to the standard.

Having spent some time REVIT of late and previous experience with other options out there, it seems there just isn't a good wall handle many of problems in any system. Given everyone loves saying they have AI features why couldn't we use machine learning path-finding to attach a tag to a wall at lining changes and have AI determine how to fill out the available wall/surface between tags. Instead of making it more complex make it so the wall has to handle less but much much better than it does currently. allow bots to handle the complexity.

https://www.vectorworks.net/en-AU/public-roadmap?url=wall-modernization-83 Wall modernization has been on the roadmap in active research for a while now. Hey but at least Slabs/Roof modernisation got move to in development recently.

I think you'll find that it sends the previously rendered viewports back to wireframe.

this is a completely different interface than the one you are in to edit layer visibilities so if you hit layers then need to adjact classes, or indeed realise you want to change a bunch of viewports you have to close one dialogue open another. In contrast to a more modern tool with title blocks, most of the buttons take you to the same dialogue, add a revision then decide you also want an issue added at this time, or the project name/address needs an edit just jump between tabs in the same interface.

For many tools the buttons on the PIO are shortcuts to tabs on the expanded settings dialogue. Once open you can just between various tabs of fix multiple things. It would be great to see that as a standard approach.

Force quit works if you saved before publishing. Which is wise anyway.

It really is a bad release. I wonder how it got out of the virtual door?

You can hack this with various degree of success by using layer override colours. set the black line and fill squares to grey and most objects will respond. Not always all doesn’t change image based resources.

I've seen slabs so polluted by trimming modifiers the only choice was to throw them out and start again. Does seem like the system should be rethought you can never really modify the modifiers as most edit operations make them unknown tot he slab, just delete them and reapply them.

Tttleblock allow you to record both Revisions and issues. I've seen offices use One for client facing and have that list on the printed page and then use the other one showing up outside of the printed page for Internal tracking.

Yes, Universal Vectorworks files would be great and it was put forward several times over the years as the reason for .vwx file change. Still as a show of progress and to improve the usability of the Libraries, it would be a good test bed. At a per-type level how many of the types have changed dramatically over the years? Lots of objects have got a revamp but at the same time, they moved from Red Symbols being stored in the library to Object Styles Types. The code to do the conversation if they are needed would exist, Sure doing the conversion each year isn't much work but it seems it is enough to mean people just don't use the system.

To avoid redundancy and other management problems, Library files should not be in a specific version of the file format. They should be able to deliver the resource to the version of the app that being used regardless of what version of app saved the resource saved it. Given that most resources are fairly small objects anyway, any background data conversion that happens to get it to work would be quick. Benefits- - One True single library (per user or company-wide) - Smaller Install, smaller footprint - less management - Set and forget each version wouldn't need new locations to be set so could just read the settings from prior install.

Yes surely the talent they might throw at AI could probably be more impactful targeting low hanging fruit of production killing issues.

Also 3D clearances for parking structures

In theory, the AI could already author a vectorscript description of the Wall type you'd like to replace the wall type you had if there was enough of the function exposed in the VS documentation.

My first lecture in my first year of architecture started with that very line. 30 years later it is only marginally more true today than then and fails to understand how much further it has to. So sure maybe in my lifetime I might read about it happening while in the nursing home.

Or the Program ship from your local distributor with most of the common ones in your market. Then you'd only need to make a small handful of uncommon ones each year.

Add the potential VisionPro is showing and you have the specs sheet for the last CAD program I'll invest in, in my life time.

That shouldn't need AI just features like Materials to do the job they are said to do. 😉 Save the AI for Fun things.

Storey Styles, LOL I sort of Kid, but it does seem like the way they do things like this these days. Still, a Storey Style might not be a bad single place to update in the project. We could have multiple in the same file, and we could transfer them from project to project or have a library of common project/construction types. That said, I will always upvote better Storey/Layers/Levels to better represent common building practice.

With an option for stacking them all on top of each other but creating a layer for each

If you have a symbol, you want to lay out a regular spacing along a line, why not use the repetitive unit tool?

Yes, it would be nice.

That is hopefully fixed as part of the non-modal change.