Christiaan

Back here another 5 years later to take my own advice 🤪

But a function-first approach to common tools doesn't stop one from using those tools for other things, and nor from having more generic tools. It does, however, make it easier and more logical, especially for new users. "Slab" for most people in architecture is a very specific type of floor.

I've moved this thread to the wishlist forum. The Framing Member tool should be able to do a 'cross' too.

Sometimes you have to go uphill to get downhill 🤪 The ultimate goal is logical consistency and usability, right? So even though in this case tools would be added (and some renamed), it would make things far simpler and logical for the user.

The Slab object should be renamed Floor, but only when we have a separate Ceiling object and a Roof object that can do both pitched and flat roofs. At the moment Vectorworks is geometry-first for Slabs but function-first for Roofs (and Walls). From a user point of view it should be function-first for everything (Floor vs Roof vs Ceiling).

It's incredible what one can be blind to. I had no idea there was a "Floor" object until I read this.

New users.

It could work, but... The problem with the Column tool is that presents the user with far too many options and too much information to begin with. When a user first chooses the Column tool and sets the preferences, everything should be collapsed away from view apart from width, depth and height. The other problem is that you can't even apply a Texture or a Fill to the Column object. All attributes are strictly controlled by Class or Material. Horrible stuff.

To be fair this is pretty much the only bug I've run into in practice. I submitted a couple of others to do with a sequence of actions that can cause a crash, but that's all I've found. The LOD stuff is controversial, but I wouldn't class it as buggy.

Don't know, but we know this: Vectorworks 2025 Update 4: Released March 17-18, 2025. Vectorworks 2024 Update 4: Released March 13, 2024. Vectorworks 2023 Update 4: Released March 14, 2023.

That's a good one. Or at least merge Move and Move 3D.

I'd like to be able to taper/reduce/shape the thickness of Roof components at the eaves, to reflect tapered or reduced rafter eaves overhangs.

I'm working with an architect who's mastered rendering in Nano Banana. His renderings are phenomenal. His main advice is clear wording, working through a number of prompts and then starting again with a combined prompt using the most effective ones. These are both generated from a Vectorworks model via Hidden Line Viewports.

I model the external roof covering/finish separately, and then use one Roof Face object for the main roof structure and another for any reduced rafters. I then also use separate Roof Faces for finishes to the underside as well (i.e. ceilings, soffits). Is this how you do it?

I don't know. I was just curious what other people would say. I don't think developers should be scared of removing things from their software, otherwise it becomes bloatware. I'm happy with the deprecation of Screen Plane for instance. I guess my main wish would be for the removal of legacy code that blocks multi-threading. With regard to plug-in objects, I would open source them and put somebody in charge of managing code input from users, especially for little tools like the Clothes Rod.