Hugues

@Dick Jenkins We’ve identified the issue with the window type “I” in your Graphic Legend. This window has the ID Label W-10, and there are two instances of it in your document, each with different elevation settings. One instance is placed on the layer "(N) Floor Plan -1" The other is on the layer "Object Creation - Millwork Finished", with its elevation set to 6'10 1/2" The Graphic Legend is currently displaying the image based on the instance located on "Object Creation - Millwork Finished", as it is the first one found with the matching ID Label. Please note that when the Graphic Legend reports elements based on a parameter—in your case ID Label—and multiple elements share that parameter, it will create the image based on the first matching instance it finds. In your case, not all W-10 windows are identical, so the instance used to create the image may not reflect your expectations. Your Window Schedule does not show the same this issue because its criteria are restricted to list only windows on the layers "(N) Floor Plan -1" and "(N) Floor Plan -2". You could fix the setting of the window on the layer "Object Creation - Millwork Finished" or adjust the criteria in your Graphic Legend to ensure it references only the intended window instances. Hope this helped.

And the Z value on the OIP for all the windows is the same and that Z value is 0 ?

@Dick Jenkins If this is working fine with all other windows in the project, my guess is that there is something about these windows and the walls they are inserted into that is different. Maybe the bottom of these walls are slightly offset from the floor. Also, they could set in the settings with head height from the frame of 6'11 1/2", but that doesn't they are constrained to that height. They could have been moved. Check their Z elevation on the OIP. If it's not 0, that would explain the different heights relative to the floor.

Thank you for bringing this up. You are not alone. The fact that you are having trouble understanding the story workflow in Vectorworks is an indication that it needs usability improvements. We are taking note. Level Types and Defaults levels are two different things. That's why there are separate lists. Level types are classifications that define what a certain story level represents. For instance, level types might denote "slab," "finish floor," or "ceiling." A level type is only a name description. Levels are instances of level types that come with an elevation offset, and additional parameters that specify whether the layers and elevation benchmarks should be automatically created for the level. A level is: a level + an offset + additional parameters. Default Levels are predefined instances of levels that can be set and used as templates when creating stories in a project. Default levels provide a quick starting point when creating and editing stories. They are ready to be used and re-used so you don't have to create levels every time you need one. I hope this helps clarify the concepts. You are not require to use all of the levels in the Default list. You can just keep them there. No problems. Stories should not force you into specific workflow. You can pick the one that works best your projects. Default Levels can be specified to automatically create layers associated to the levels when you create stories. But remember that this is optional. You can setup levels that don't create layers. We refer to them as layerless levels. I you have already created your layers at the time when you create your stories, you should use layerless levels for your stories. Once your stories are created, you can then associate any existing layers you have to stories and levels. Yes, you can. Going back to my answer above, you should now understand the difference. The default level "Bottom of Slab (Layerless)" is set to not create a layer at the time when the story is created. You should use it instead of "Bottom of Slab" if you do not want a layer to be created for that level when you create your story. We provide both versions of the level to accommodate the different workflows. You can create your own default levels and set them up the way you like. Also remember that once a story is created, you can always modify it, add/remove/edit levels, add/remove layers, etc... Hope it helps.

The only to do something like this is to create the database using DATABASEBYSCRIPT. You would have to write the script that filters the objects.

@Bart S The LOCATION criterion is a generic criterion that uses pure geographical boundaries to determine locations. Object A is located within Object B if it is clearly within the boundaries of Object B. This is why the windows will be located within the space only if the space encloses the windows. GetSpaceNameForObj is a function that is specialized for spaces. It is aware of the context of a Space object and use special rules that apply to Spaces where objects don't necessarily need to be enclosed by a Space to belong to it.

It is the 2024 file that you are browsing that would be the problem. If you can share that file, that would be helpful. Is this happening with just any random 2024 you are browsing? or only specific files? Are you on Mac or Windows?

This looks like a bug. It shouldn't crash. If you don't mind sharing these 2024 files we will investigate the issue.

Hello, In an effort to improve the Vectorworks user experience, we are seeking your input to help us evaluate our upcoming Door and Window Assemblies tool, which will let you combine multiple symbol, door, window, and other types of objects into a single assembly that can be inserted into walls. You will gain access to a special Vectorworks 2025 build and be asked to provide feedback in a private Forum group after testing. Disclaimer: the special Vectorworks build used in this focus group will be a standard English US version. The new Door and Window Assemblies tool to be evaluated in this version only supports standard US version door and window objects. Requirements: You will need a Vectorworks 2025 version license of Architect, Landmark, Spotlight or Design Suite. You must have a Vectorworks Forum account to participate. The first 100 people to submit their information will be able to participate. Please let us know by October 22 if you would like to participate by filling out your information at the link below. I would like to participate in the focus group. We would be delighted to have you take part! If you have chosen to participate, we will reach out to you shortly with further details. Thank you for your consideration. Hugues Tsafak VP, Product Development

Thanks. This confirms our findings that Apple has resolved this issue with in macOS 15 (Sequoia).

While you cannot search for tags directly in the search field on the Navigation palette, you can setup layer filters based on tags.

If you aren't running the Cloud Service app, sign out of Vectorworks from this button on the top right corner, then shut down and restart Vectorworks. Sign-in again and the problem should go away.

@VIRTUALENVIRONS If the Vectorworks Cloud Service app is running, sign out and restart it, or sign out from Vectorworks and sign in again. This should resolve the issue.

@gloudon If you are reporting space areas, ='Space'.'EnergyArea' will be faster and more precise than the generic AREA function. You could separate reports for the building footprint and lots classes as explained by @Tom W. If you want to keep them in the same report, you could use a IF function to conditionally show the area for spaces in a specific class. For example, in the Buildable footprint column you could enter: =IF ((C='Buildable Footprint'), 'Space'.'EnergyArea', 'n/a')

I would like to clarify that this is not about cell formatted as Text or Text field. This is about decimal numbers in general.

@Pat Stanford @ashot Here is the answer the question about the precision in worksheets. The IEEE 754 specification standard for how to store and calculate floating-point numbers doesn't offer infinitely precise calculations. That standard can only accurately represent 15 digits decimal numbers. Worksheets follow the IEEE 754 specification but move the limit down to 13 digits to allow for handling of various rounding errors. I believe Excel follows the specification with 15 digits. This is the reason why decimal numbers in worksheets have a precision of max 13 digits. Note that the number of digits in the specification here is the number of digits for the number, not the number of decimal places. @Pat Stanford You are seeing max 11 decimal places because your number already uses 2 digits for its whole number portion. Hope it helps.

When a cell with a decimal number is formatted to "General", the default number of decimal places displayed is 3. If the cell is later formatted to a format that allows specifying the number of decimal places, the number of decimal places specified will be remembered when the cell is formatted back to "General" or another format. When you format a cell to "Text", it is not changing the value of the cell. Your number remains the same. It simply instruct the worksheet to treat that cell as a text as opposed to a number. You are seeing 8 decimal places instead of 12 because the internal decimal format for that cell is set to 8 decimal places from its previous formatting. Remember that when you reference a cell, you are referencing it's actual value and not its display format. The format of the cell you are referencing into will determine how it will display. As @Vlado mentioned, if you have a number that you want to convert to Text, the text cell format isn't what you need. You should use the TXT function.

I would like to add that as of VW2022, there is now a function that returns the class description of an object's class in a worksheet. =OBJECTDATA('class description') https://developer.vectorworks.net/index.php?title=Worksheet_Functions

@Amanda McDermott Could you please email me a copy of your user log files ( the VW User Log.txt and VW User Log Sent.txt) ? htsafak@vectorworks.net

@Ben3B We are not seeing the same issues with google drive folders. The error you are seeing is an indication that Vectorworks is not able to get write access to the file because another application has an exclusive lock on it. Not sure what Google Drive is doing to the file. How big is the Excel file you are using? Are you using the latest version of Google Drive for Desktop?

@line-weight Yes, data visualization can switch object attributes from hatch to solid and vice versa. You would need to setup appropriate data visualization criteria depending on where your objects are getting their attributes from. Simple example: You have objects in Class A, B and C that are using attribute by class and you want to override the Fill using data visualization. Set the Object Criteria to find objects in class A, B, 😄 Class is A OR Class is B OR Class is C Set the Display Criteria to Objects using function Class. You'll see the list of classes. Set the fill for the classes you want to override to whatever color you like.

The Graphic Legend tool is building the legend for objects and resources that exist in your drawing. There are no criteria for filtering objects based on resources or resource folders in the Resource Manager. You could submit a wishlist item on the Wishlist Forum and describe what you are trying to accomplish.

One possibility is that the 3/4" you are seeing is a rounded display value and that the precise values are slightly different.

Viewport Styles control visibility and attribute overrides for Classes and Layers. You can try to copy a viewport from one file to another to see how the class overrides work. That should give you an idea of how this would work for Viewport Styles.

Edit the reference and you should see the option to auto update the reference at file open. This an option that can be controlled for each reference individually. Note that if you are referencing an image file and the option to save the referenced cache is unchecked, the reference image will always auto update at file open. You must enable "save referenced cache" to control the auto updating at file open. Hope it helps.