Andy Broomell

Neither of the things OP mentioned are saved into a template. I think they're saved in one of the various .txt .xml files in the User Folder but I'm not sure which one.

@Gunther my VB-216550 has a test file that is sluggish in 2026 but is smooth and responsive in 2025. Not sure if it's related to OP's issues but I figured I'd mention it.

Anything that's a Component in SketchUp will come in as a Symbol when importing into Vectorworks. Unfortunately there's currently no way to avoid this. The aforementioned checkbox only adds an additional step of putting all the imported geometry inside a new Symbol that Vectorworks creates. (This may or may not contain sub-symbols depending on if the SketchUp file has Components.) If you want to rid the geometry of all symbols, the most reliable way is to make sure the "Import as Symbol" option is checked, then after importing do a command called "Convert to Group" and make sure to choose the second option which says "Convert nested symbols and plug-in objects." Then you'll be left with all raw geometry and no symbols (though you'll still have Groups). Do this in a separate empty file, then copy and paste the result into your working project file after doing these steps as to not clutter up your Resource Manager. I also like to take look at imported Classes and delete/reassign as needed.

What's the font test function?

This has been my experience as well. It should be improved somehow so that a user can double click to end the poly, even when using the snap loupe.

@Matt Panzer I think my VB-189181 is also related to this. There's a detailed narrated video and test file. Unfortunately the VB got a long-winded comment that concluded with "So the idea that it is not working correctly is coming from a false assumption as to how it should work and what it does." Which I internally grumble about every time I try to set window elevations 😄

Got it - so the RM in 2026 still contains symbols for the all possible geometries, but the various data permutations have been removed. Then, those various graphical representations can be pulled in by the Plant tool, combined with plant data, to create specific Plant Styles as needed? So if I only care about visuals (sometimes 2D, sometimes 3D, sometimes both), the best way would simply be to browse the folders within Vectorworks Libraries until I find something that looks correct. Thanks Katarina! (btw, having watched your videos on the beta forum, I realized I now read your posts in your voice! 😄)

In 2025, searching "Ophiopogon" in the RM gives a result. In 2026, it does not. Katarina, I see in your screen recording that you inserted the Plant via the Plant tool set to "Data Mode" rather than "Geometry and Library" mode. I'm not sure users who have previously inserted plants via the RM would realize that many plants have been removed from that source in 2026, and presumably are now found only in the "Data Mode" instead. (If I'm understanding correctly). I'm not in the Landscape Design field, but often have to pull in specific plants for set dressing, and typically just perform a quick RM search to see if it exists. Should I now check both the RM and searching the Plant Tool's Data Mode?

From what app are you printing the PDFs? (Or are you printing directly from Vectorworks?) And are you on a Mac or PC?

While I personally prefer a venue to be on a single Design Layer with multiple classes used to classify things, I can also see the advantages of using a handful of Design Layers to organize the various major categories. In any case, I'd recommend adding a common prefix to ALL venue Design Layers, so that later when designers utilize the file, any layers they add are easily distinguished in the list from the venue Design Layers. Ditto with classes - they should all use a common prefix.

You're right. What I think I meant was that if you had rotated symbols in your drawing, editing via the RM would default to the original unrotated symbol view. However, if you're working with a Rotated Plan, editing via the RM indeed retains the rotated view (which I hadn't grasped till now). Thankfully, Cmd+5 or Ctrl+5 still works as expected to quickly unrotate the view, which is then restored upon exiting the symbol.

The initial release of 2026 would show a solid color even if the Attributes Palette is set to None, which is annoying. I believe a fix for this will come out in a forthcoming update.

Hmm.. I actually suspect the underlying issue with the parthenocissus is that the texture doesn't scale up or down on the internal 3D polygons when the object size is altered by the Plant PIO. The phragmites I'm not too sure about. The internal Image Prop for that one seems to actually have that sparse image as the texture instead of the reeds image. The sparse image was the Top/Plan representation in 2025... So it looks like something got messed up in translation to 2026. Here are the symbols from 2025 which you can hopefully import into your 2026 file: PlantsForVR.vwx PlantsForVR.vwx

Hey Victoria. I'm seeing the same thing in 2026, so it must be a content error. I also noticed that the parthenocissus inserts as a 2D/3D symbol in 2025 (and looks correct), but as a Plant object in 2026 (and looks wrong). Either @JustinVanHassel or @Katarina Ollikainen might have some insight here.