JasonMichael

Yeah, splitting something twice would cause a loss of geomtery as you describe. For me, I deliberately used the split tool to end up with open geometry, and would clip surfaces if I wanted closed geometry, especially if it would be a multi-step trim. Trimming open geometries still results in open geometry, so I can probably work around that. A toggle in the tool settings would be ideal.

Hah yeah I was so surprised when I noticed this changed. Seems like such a nuanced action to change deliberately, so I'm wondering if it is a consequence some change in how geometries are processed. As a work around, I've hot-keyed "decompose" in my custom workspace. After I split, I decompose the resulting closed poly, deselect the line I want open, and then compose my selection again. Then I delete the extra left over line. Kind of a pain lol.

I've noticed in the last few service packs of 2025 and in current 2026, the Split Tool now only splits closed 2d objects into closed polys. In prior issues as far back as I can remember (at least 2017) the split tool on 2d objects like rectangles, circles, closed polys etc, would result in an open poly, with an open side along the split line. The "Point Split Mode" still sort of works this way: if I split a 2d object at 2 points on its perimeter, I get two open polys/polylines. If I cut it the same way with "Line Split" or "Line Trim" mode, I get a closed poly. In previous versions it would be open. Is there any setting I can change to go back to the old way, resulting in open polys after splitting by line? It is far quicker to close an open poly in the OIP than it is to open one side of a multifaceted closed polygon, and I am finding I desire open poly's most of the time after splitting. Cheers.

Ah thanks @JustinVanHassel, I didn't see it up there. Works for me!

In 2026, was the "Show other objects while in editing modes" quick preference toggle get removed? Can we get that added back to the menu? That was one of the most useful quick toggles for my workflow, and I'm sure I'm not alone in that.

I've been having this same issue with working planes as described above by @ajpen. Been having this issue for a few years now, and just been ignoring it. I've been working much heavier in 3d now, doing more sophisticated interior renderings, and this is getting to be quite the nuisance given how vectorworks generates 3d through 2d surfaces. Has there been any solution to this? Just don't use the shortcuts?

This is for sure a workaround, but I feel it may be redundant to do this when I have files with dozens of sheets and multiple viewports on each sheet. Managing and updating 50+ sheet viewports is enough work, adding another 50+ named views to coordinate with each sheet layer viewport seems like something I don't want to do entirely lol. If there is no way to reset the default settings when navigating to a design layer, I shall continue hitting Ctrl+Alt+5 every time I navigate in--maybe the calories I burn with my fingers will do me some good. You are correct in that I had this setting toggled on. I have toggled it off just now, going to see if it effects any behaviours. I do feel like I never used to have this problem, and that the default in the file would eventually reflect the behavior I desired, however I'm not sure exactly what triggered the change in preferences. Maybe saving and closing a file with my desired layer options, and then reopening a new session?

In my typical workflow, I navigate to design layers through Sheet Layer Viewports, i.e. context clicking on the viewports, and selecting "Edit Design Layer." Over the years, I've found this is the path of least resistance in keeping mentally organized through my files. In my current document in VW 2025 Update 2 on Windows, when I enter a design layer this way, the default "Layer Options" are "Show/Snap Others" and I prefer to work in "Gray/Snap Others." It is getting annoying hitting CTRL+ALT+5 every time I navigate to a design layer from an SLVP. Is it possible to change the default settings when navigating to Design Layers so it is Gray/Snap Others instead?

@Dave Donley, you sir are a genius! Thanks, I believe the issue was in having the Default Compression in Vwork Prefs set to JPEG on one machine. Changing to PNG resolved the issue. Thanks a bunch!

I am working on some rendered viewport elevations, with my work split between two different computers with two different CPU/GPU's. On my work machine with a i7-10700 and Quadro P2200 cards, I get clean renders; on my home computer with a i7 13700K and GeForce 3090 cards I am getting a white ghosting around the perimeter of my rendering, as shown in the first image below. (Both images are screenshots of published pdfs. The halo artifact is also visible in Vectorworks on the sheet layer view after updating the viewport.) The background trees and foliage are viewport annotations, just jpegs underlayed behind the viewport; the foreground trees are annotated vector art; and the building is rendered without a background. I am not sure why I am getting a clean result on my work machine and a messy result on my home machine (that is significantly more powerful than my work machine, although not a Quadro card, which I suspect has little to do with it.) Any ideas? I would prefer not to upload my file publicly.

I have solved it, I had an issue with an illegal character from using ALT Codes for special characters, i.e ² Ø ▼ → . To troubleshoot I exported the pdf with rasterized text, and found their was no error on printing having done that. I "Selected All" on the design layer that was giving me the error, and changed all objects to "Arial" font in the "Text" menu bar. Then I scoured the text for any funky characters, and found a few empty squares and error characters. Deleting them and switching my file back to my firm's preferred font produced no more errors.

I am having this same issue in 2024. Any solutions?

This is still an issue for me in VW 2024 3.1, however it is hard to recreate the issue after it happens. I rarely use the "add leader" function as it just isn't something I need to use often drafting, but frequently when I do use it, VW crashes, typically after long multi-hour sessions. VW shuts itself down after the freeze, and when I re-open, sometimes it will crash again, other times it will work successfully, repeating the exact same function on the same callout object. It happens frequently enough that I know to save before adding multiple leaders to a callout object.

Discovered a bit of a window bug with the custom window configuration. When switching between "interior right side" and "interior left side," the sash component seems to not switch in the 2d representation. See image below for extra long sash and two equal panes of glass; it should be two unequal panes with default sashes. When I switch back to "interior left-side", everything displays normally (second image.) I think one of the reference points is not switching over, giving two equal panes of glass set to the size i specified for the custom casement. As a work-around, I am setting the "interior side of wall" to the exterior for windows where I need the 2d plan display to show the casement vent in the right location. Consequently generated elevations for window schedules will be incorrect, however that is not an issue for me as I draw them manually. window bug.vwx

I upgraded my laptop to Windows 10 and i was able to activate. Best of luck with the social isolation. I wasn't able to get any help with it, but i figured I had to update Windows from Windows 7. Most of what I saw online was to continue trying, and to make sure that Vectorworks isn't blocked by your firewall. Also you could try running vectoroworks as administrator by right clicking on it.