Don Seidel

If you put slope on a slab. There's currently no way to hide the elevation text! No class, no settings (I could find) afterward to turn them off.

Except for slabs connected to the building foundation,… (patios, porches, landings. These are not part of site development )…. one would expect to use the slab tool. there are 2 or 3 workarounds, yes, but we should have a simple option to pitch an exterior slab without a workaround 😊

Should not be this hard. In the real world all exterior slabs slope; most always just in one direction.

1- I would never have guessed a Data Tag called "Wall Dim-Name w Leader" would yield component info. Can we fix this? 2- Only works on Un-joined walls. Try above example with 2 or more joined walls, top-plan. So it's fine to note components of wall types, for example. But if one wants to note components of a wall section in a normal building model, It doesn't work. 3- We don't always BIM to real-world dimensions. 1/4" thick material would blob into nothing at 1/4" scale drawing, adding confusion. In such cases we may model a non-real thickness of something for clarity. VW's actual reading of the drawn thickness would then be NOT what is wanted in the note. Thus the request for a distinct user-text field in data of wall components.

Thanks Nikolay, but you missed the point. Noting wall components is SO COMMON is architecture, that VW users should not have to write code. At the moment we can do the entire component list as 1 paragraph. This is the exception, not the major use. And you have to use materials. The information needed for individual component notes is already done by the user (component name, thickness), so the most basic Data tag would offer that info back without coding. BETTER Still: Why not offer another data field for components "Notation" , in which the VW user could have any terminology they wanted to be the text result for a data Tag. At the moment we'd have to create and attach a separate database. Workarounds are not always the proper solution. component notation.pdf

VW should have a Data Tag that does this (Individual component name, with option for additional fields of the component definition). Too much custom coding for an everyday use. this is a MOST COMMON need of noting a wall section or detail. Also, a CHANGE in the data of components would auto-update the project notes (component data tags) everywhere = BIM

unfortunately, the closest VW solution to 3D piping is a round AC duct (show 3D detail).

Yes. Extrude along path is only adequate for small amounts of wall trim. It has to be created and edited manually, so it's not at all a solution for regular and large projects. The above plugin facilitates molding creation. While similar, not the same as wall trim. As part of a wall, trims would have huge automation.

IMHO, moldings should be integrated into walls, similar to components. Optional checkboxes for ceiling, chair rail and base trim where you simply select the profile, and set a control point for height (some cases where base trim would be above the floor). Such trim would be secondary to door & window trim (in case of conflict), and automatically stop at door/window openings. Option to continue through cased openings. Individually classed of course. Would make interiors so much faster, as all the trim would auto edit with changes to walls, doors and windows.

Anyone find a decent workflow for watercolor style rendering? AI render would probably do pretty good w perspectives, but I’m looking for 2D graphics with a watercolor look.

On recommendation of a buddy, who is a 3-D printing hobbyist, the Bambu P1 series printers are very cost-effective ($700 +-) and produce models just under 11 inch cube in size. Out of box settings are perfect for anyone who doesn’t want to make a career of 3-D printing, but simply needs to print things. Of course, it’s always good to know your equipment better, but you can get up and running very quickly. You have to be realistic about what level of detail you will get with this level printer.,(opt for the 0.4 steel head) but for the most part, we’re very happy. VW export (STL) works pretty well. The problems we have is any cabinet or door plug-in object which has panels. The panels do not print and you get a flat surface…or simply a void. Our workaround is to create a copy model, just for 3-D printing, and then convert these problem items to mesh. Every brand has their own settings. So jump in.

Other VW employees have acknowledged that the link breaks on the Mac, but they don’t know why. So it’s not a new issue or an unknown one.

Apparently for quite a while, it's known for a long time that there are Mac issues connecting SQlite databases to a VW document. It's highly buggy at best, and broken at worst. The issue has zero weight to get fixed. So I find it disingenuous that VW would publish a FEATURE ARTICLE on a tool that rarely works. https://blog.vectorworks.net/guest-video-sqlite-databases-vectorworks-objects If the issue won't be fixed, fine. Then please remove the tool/function from the next update. But don't advertise things which clearly are not ready for mainstream use.

...so it begs the question: WHY do any final render in VW anymore? The modest cost of TM or ES for the speed and final product are an incredible value. I LOVE that ES operates as a live plugin, making the start-to-finish process even faster. Of course VW was never design to primarily be a render program, but the speeds of even top-end machines are dinosaurs compared to what base-level machines can do with TM or ES.

Mac Studio M2 Ultra 128 GB ram (OS 14.0) = 5:42 VW 2024 TwinMotion or Enscape onscreen = 2.3288964 sec Output to jpeg = probably under 15 sec.