Peter W Flint

Upgrading is a process that requires days to weeks of readjusting resource libraries once the migration process is finished. Its not something I can do in the height of production season and something I try to avoid until there are enough new and functional features to justify the effort. My preference would be that updates for incomplete features be included in service packs. Agreed. I was simply piggy-backing on your comments with my own example. I can post a dozen other reprex files for other objects.

I guess this illustrates my gripe with the inconsistency. A feature should be fully supported for all tools before it ships, not halfway done, particularly in a software with an ever-increasing price point.

I am running into similar issues with data tag inconsistency. I know there have been updates in the logic of how tags call data from objects intended to make them more functional, but there is a lack of resources for staying updated with those changes, and the user dialogs don't seem to contain the information I am looking for. I have resorted to tweaking the resources that ship with VW, but even these don't function as expected when changing object and selection criteria. The recording below, for instance, captures a slab-material tag customized to a hardscape. The original slab tag will pick up components in subpart mode for a slab but not a hardscape. The customized tag will only pick up components in "all eligible objects" mode. Reprex attached. Screen Recording 2025-10-30 at 12.50.01.mov 2025-10-30_forumReprex_dataTag-bug.vwx

Changing to a comma definitely does something but doesn't correct the issue. See right side of screenshot. I am happy to keep fiddling with it as an exercise in OCD therapy but the solution above resolves the immediate issue.

Update: No success with this formula but this one works: #Landscape Area#.#Instance Name##AREA##Landscape Area#.#areaUnits# #AREA# from Object Function data source

Ok, thank you! EDIT: @Alexandra Beshevlieva When I change the parameters per your instructions it simply removes the name and projected area altogether. What am I missing? Typically I use the "Define Tag Field..." dialog via "Edit Object Style..."→"Edit Tag Layout" and the accompanying drop-down options. In this case I copy-pasted your parameters into the field definition box.

Having an issue with data tags after migrating from v2022 to v2025 where some tags are inconsistently calling metric data to as opposed to imperial as specified in document settings. The screenshot below shows two LAs from a test drawing with the same data tag called from the RM of the problem drawing. One is showing feet & inches correctly, the other displays the projected area in mm2. If I change the settings of the correct LA in any way, the tag reverts to the metric area. It is unclear to me the source of the issue. I've seen a similar issue here. Reprex attached. Cheers PWF 2025-09-15_reprex_dataTag-metric.vwx

This response feels like a cop out in terms of basic UI. Yes you can type "tag:<yourTag>" into a search bar and find your resource. This is generally something you learn at the intermediate level after many hours of usage. Expensive software should shorten the many hours curve. Every modern file browser interface, from Finder to Explorer to task managers and code editors, includes a specific button for filtering and displaying tags. With such a feature, you don't have to include "misspelled tags" because you can correct the mistake once you see a populated list. The closest VW comes to this are the tag lists in the organization panel. This capability, in addition to the RM being able to call mixed resources based on a selected tag, would be incredibly useful.

Curious if this FR has been included in any VW updates since the original post? PWF

@Mauro Pujia Once you got past the error dialog, did you have success importing sheet layers with title blocks attached? I'm not able to and according to this post doesn't seem like that is a feature...

I am troubleshooting a number if issues related to the OP with two different LAs on preformatted reports. For instance, some plant images are not rendering in the worksheet. Thoughts are welcome. Reprex attached. Thx, PWF 2024-03-19_forumReprex_wkshtPltImage.vwx

I have shared models in the last few months with some of my tech-savvier/enthusiastic clients and not heard any complaints. There are some UI improvements that address the learning-curve, notably the `?` Help icon with some simple graphic instructions. Classes can also be toggled on and off, those are the improvements addressed over the course of this thread. However, there seem to be some issues in the course of introducing those features that have now made the app less set-up friendly on the deisgner end. For instance, I'm not getting consistent results with availability of higher level PIOs in .vgx files generated after the latest series of updates. Ie doors, windows, landscape areas, fences, or texture beds will not display or be available in class selection. That is a significant step back. Layer organization also seems somewhat arbitrary, meaning layers will not be arranged according to the order in which they are specified in the original file, but they are also not arranged alphabetically so I've not tracked the logic on that. In defense of the developers, I am still drawing in v2022 and the issues above may be related to that. Overall I would say it is still a useful tool provided its limitations are understood, maybe at the conceptual phase when still playing with massing and spatial arrangements. But it now requires more time and energy to set up at more advanced stages of design and I suspect is ultimately more confusing for an end user or client. As an example, I am preparing for a review next week and do not anticipate introducing it as a presentation tool. PWF

Fair point. I think this was partly "complain as problem-solving" and screaming into the void. There is an issue with the way the data is formatted in the catalogs and the way it is read into a new catalog from the edit plant style dialog in the RM, but it works when creating a new plant from the Landmark menu. I am struggling to find a way to reproduce in a time efficient way. Will probably set aside and return to it once I am clear on the necessary steps.

EDIT for clarity: I use the field/record terminology for tabular data as commonly used in GIS applications. When I use the term "record" I am referring to what would be called a "row" on a spreadsheet or an "observation" in other data related disciplines. I am not referring to VW resource records. When prompted to add a new or edited plant style to the catalog, VW will interpret some of the data as new records (or rows) from the values in each field. The pattern I have been able to determine is some hidden delimiter in the data that ships from one of the Vectorworks catalogs. When I create plant data from scratch I am able to import and export between catalogs without issue. As an example, here are some screenshots from one plant edited in the VW2008 catalog. I have edited the flower characteristics, tolerances, and comments fields. It seems when there are multiple values delimited by a space in the same field, VW will interpret as a new record. If I include a pipe (|) VW for read as multiple values. This is not user-friendly. Please do not reply with advice for using plant styles in their own drawings or to avoid use of the plant catalog. I am already familiar with these approaches.

Prompted by discussion in this FR, I am able to assign tags to objects in the resource manager but unable to filter by them. I suggest a "filter by tag" drop-down somewhere in the vicinty of the "filter by resource" drop down on the RM ribbon. This adds another layer of visibility once drawings become resource saturated. PWF