Tim Harland

@MullinRJ Update number 2 - it also worked on the other issue we had - thanks a million - that saves opening & closing ca. 3000 Symbols by hand!.

@MullinRJ your Script worked for this particular issue, thanks! I'll test it on our other case as soon as it pops up again.

See attached for a test file - we have a couple of different issues, both of which are solved by opening the symbol in the file providing the referenced symbols and closing it again. One thing to note - our symbol is a bit complicated as it is a symbol inside another symbol (so that we can push updates to record fields out to references files), I am pretty sure that is where the issue lies. In the attached instance the content in the library file which has been updated via a worksheet is not updating in the file in which it is referenced. We also have another example where the symbol inside the symbol is simply not visible at all in the referenced file. In both cases opening the symbol in the library file and closing it again solves the issue. Note Library.vwx Test Datei.vwx

Yes exactly, the old "give it a thump" trick that Vectorworks somethimes requires!

Hi @Pat Stanford istit possible to create a Vectorscript that simply opens the 2D editing pane of each symbol on a particular design layer or a selection of symbols and then closes it? We have an issues with the visibility of referenced symbols that seems to only be solved when we open the symbol and close it again. We have several hundred symbols though so it would be great to automate this process as a workaround to the bug in Vectorworks.

Using save referenced cache to disk did work, thanks for the tip!

Yes since VW 2024 this is now working for cloud rendering which is great!.@inikolova could it be that there is a similar issue to the vgx export in that when the local version of vectorworks is not as current as on the server the referenced files won't be rendered? I haven't tried a cloud render from VW 2024 since VW 2025 was released.

Hi @inikolova Thanks for the explanation - the different versions are quite likely the issue. We are using VW 2024 so I presume the cloud is processing in 2025? Although 2025 has only just come out in the last week here (we are running the German version) and we probably won't update to 2025 until at least update 2 so there is always going to be a bit of an overlap. I'll try using saving the reference cache & see if that works - we don't typically have it switched don in order to save disk space (these are big 3D files) Regards, Tim

I have noticed that when I attempt to export a VGX with layers that are (traditionally) referenced into my VWX file, the referenced layers are not exported. Has anyone else had the same experience? It was similar for cloud rendering until VWX 2034 & 2024 (referenced layers would not be rendered) but that has been fixed. I presumeit is a similar issue for VGX export that wasn't corrected at the same time?

We are also still seeing this issue in VW 2024??

Hi, is anyone else having problems editing room finishes with VW 2024 Update 6? When I select and existing finish, or add a new one and then click on the Finish number or description the field goes grey and I can't enter any text?

Is there any way to get the Drawing/Sheet Number Box to scale with a longer Viewport Number and/or Sheet Number (similar to how the Drawing Title adjusts to fit longer text) and to shift the drawing Title and Scale in the Drawing to the right in the Label Square style?

I have a file with referenced Design Layer Viewports, I have applied Viewport Styles to the viewports with class colour overrides, however after I update the reference the class colour overrides disappear, I have to 'kick the tyres' by applying a different viewport style and then reapplying the style I want to use. Has anyone else seen this behavior?

Hi Luca, yes I'll pull something together - I suspect what we are after is going more on the direction of the SQLITE Databases post that was in a recent newsletter, albeit even in those videos it didn't seem to be possible to link back out to the database from record fields.

Thanks @Tom W. that coffee break was quite helpful - I must have missed it. HI @Luka Stefanovic OK that is good to know it can be done. It wouldn't just be for formating, we would also use it for data entry, especially as it is much quicker and less destructive to filter lists in excel. There are also still advantages to formatting in excel (printing over multiple pages for instance, adding headers & footers, printing headers on multiple pages) unless there are additional printing option for worksheets that I have missed in the last few versions? It is also necessary for excahnging information with clients and consultants. As far as I understand it from your Coffee Break, we would have to have a referenced version of the Excel Schedule that is linked to a Database worksheet (eg. via the Door number or a Door Type). But all the information about the item being scheduled would have to be just in the excel file - we wouldn't be able to have the information about the item as a record field in the symbol? In the coffee break example would it have been possible to change any of the information about the sanitaryware products within vectorworks? I guess it would be possible in the refenced Excel file, but not in the Database worksheet? So again in that example you wouldn't be able to select all sanitary objects from a particular manufacturer, or with a particular finish? In your example would it have been possible to list all the objects indivually and add other information from a record format eg Layer or class or a record format attached to the symbol? That could potentially work for us. What would be most useful for us would be to be able to for instance change the fire rating of a door in vectorworks and then update the excel version of our door schedule to reflect this without having to do an export. Of course it would be amazing if we could also make changes in the excel that would be reflected in the vectorworks file but I can see how that is technically very challenging and would essentially need a permanet connection to the vectorwokrs file to know the state of all the objects that were being scheduled.