Peter Neufeld.

Hi Joe, The Send to Surface command only works with a Vectorworks Site Model. With your mesh if you Modify>Convert to Group and ungroup the result, the resulting 3D polys can then be used as Source Data for the Digital Terrain Model (DTM). Note that it won't work for certain objects - like the Seating Section for example, but if you once again Modify>Convert to Group that and ungroup the result the individual seat symbols are then able to be moved to the surface of the DTM. The Vectorworks DTM is in a totally different league to Sketch Up. Please have a look at the video story recently done on The Imagination Collaborative and Select Event Group and Liv Golf. They scan the terrain with a drone, convert that to a Vectorworks DTM and harness all the power that can bring to their planning in conjunction with geo-referencing. At this level, the pain is worth it and long gone. Note that you will need either Design Suite, Architect or Landmark to do this. Cheers, Peter

Hello, I'm not sure I understand what you're doing as Renderworks and HLR requires 3D objects in any view other than Top Plan. What you might be missing is the graphics power unique to Vectorworks in Top Plan such as this example below on the left combined with a Sketch render. If you pass that through the built in Vectorworks AI Visualiser then you can quickly get a water coloured plan. Below is almost a first pass without any refinement to get the idea. Cheers, Peter

Hello, Associate Dimensions are only for 2D objects. Cheers, Peter

Hello, See if this Catenary curve plug in helps: Cheers, Peter

Hello, The floating data bar in Vectorworks really boosts efficiency by allowing you to enter exact values and see real-time feedback when drafting. This greatly reduces the need for manual corrections afterwards and generally streamlines drafting. You can control aspects via the Quick Prefs: Maybe choose the second option at the top so it only shows when you hit the tab key? Cheers, Peter

Oh I see I knew it would be something other than a standards list! I can see why you asked as the alternative would be to import both Architect and Landmark standards, then use all pertinent PIOs that auto populate classes. Good luck! I take it you have the enclosed script but in case you don't I include it FYI. @Bruce A Ferguson kindly added a texture column recently and it originated from @Pat Stanford Once you have that document with all those classes it will create a great worksheet for referral with all the class attributes and descriptions etc. Worksheet listing all things about classes in a doc.vwx Cheers, Peter

Hello, They will need to go to the local Vectorworks website>Downloads and download the Vectorworks 2026 Install Manager. Once opened they need to check the 'viewer only' button. Cheers, Peter

Hi Christiaan, Do you mean the standards list or something else? Cheers, Peter

Hi, macOS 15.7.2 M4 Max 36GB UM Using the smaller file in the post before my reply (182.3MB). Cheers, Peter

Hi @line-weight Here are my results: Opened v2026: 6GB Opened the above file: 8GB Updated all viewports: 8.75GB Updated all viewports: 8.75GB Updated all viewports: 11.79GB (and had opened another file) Updated all viewports: 11.79GB (closed other file) Updated all viewports: 9.72GB (only this file open) To my mind nothing seems unusual here as the range is small. I know though that memory can be retained but it seems that eventually in my case some was released after a while. Cheers, Peter

Hi, yes Steve has retired and JIRA has a limit of 1GB I think. I didn't realise @Tom W. that it was such a large file which might explain some things as there's probably a lot going on even idling. If you ever have a clean cut example of a file that when doing one action and letting it sit in the background and the memory increases and/or doesn't let go it would be good to submit a report about it with the file. I'll see if I can get any more information about this. Cheers, Peter

Hi @Tom W. I'd file a bug report about that please. Cheers, Peter

Hi @line-weight I'm not qualified to speak in engineering terms about memory and/or memory leaks rather just my own observations about large numbers of undos. I understand as I see it too though, some files use a chunk of memory and retain it, even if I haven't brought them to the foreground for a while (say parked in another version as I usually have 3 or 4 different versions open at once). Often they might be left in Shaded which is understandable retaining memory. I'll have to do the experiment and go to wireframe and leave it for a while and see if the retention is reduced. Cheers, Peter

Hello, You hint at the possible cause of the problem. If you do the experiment and set your undos to 0 does that makes a difference? I always recommend users keep the undos at the default of 20 because it's going to eat up more processing and memory otherwise. Cheers, Peter

Hello, In tech support last week I had an LD who wanted to number and label the different types of bulbs and also the length of the catenary. Using the Marionette tool as mentioned above, once they were happy with the result I got them to Modify>Convert to Group and then ungroup. Once done just add the EntEquipUniversal record (or Light Info if required) so the Numbering command auto numbers the lot. I then created a quick Data Tag and a Graphic Legend. In the enclosed file it was using the symbol name which as you can see was too long and should be shortened. Festoon v2026.vwx Cheers, Peter