Gunther

@KevinF1973Okay, your issue definitely sounds different compared to the delay I was encountering. The bug I mentioned previously will be resolved in a future update. If you can duplicate at will, this longer stall, a video would be great and we can test further.

Bug officially assigned to Engineering for investigation: VB-211068 Adding of cable break points with the context menu is slow in this file

You're welcome to submit a bug with a file and be sure to mention it could be related to the main topic of this forum thread. Thanks!!

Seems users of camera raw files are running into a similar issue:

Official announcement with more information:

Engineering is reviewing the supplied file and time it takes to add the cable breaks.

If I try to perform a break across 6-7 cables at a time, it does take my Windows 10 computer with Vectorworks 2025 Update 4 about 20 seconds to perform the action. It appears to hang, though eventually succeeds. How long are you waiting before force quitting Vectorworks? I'll keep trying...

We're working on a couple public notifications. It appears Apple has broken some aspects of image handling in macOS update 15.4. We have reported the issue to Apple.

I was hoping dual monitor issues were a thing of the past, after all the issues we encountered with Sonoma from Apple. I have yet to hear this issue with Vectorworks specifically and checking with Tech Support for any similar reports. Searching the web in general, many Mac users encountered new dual monitor issues once updating to Sequoia. In most cases second displays are completely black or not recognized by the OS. Continuing to dig and ask around...

@Sam_UK Are you using a laptop? If so, the computer may not be switching to use the higher graphics option on launch. Windows 11 has introduced custom graphics options for applications. It should not be necessary to add Vectorworks to this listing, though it’s worth a try if Vectorworks graphics performance feels slower or you have graphical issues. -Close Vectorworks if it's running -Go to System > Display > Graphics -Browse to add the Vectorworks application file in question -Then choose Vectorworks from the list below, followed by clicking, “Options” -Choose the, “High performance” option and click, “Save” -Try Vectorworks again to see if graphical issue goes away

The command is not in the workspace editor - it is hardcoded and should always be available. The only cases it wouldn't be there are: -The user is not currently using a Design Series license -The object is already styled @Pat Stanford When time permits, would you mind submitting a bug with your Designer workspace that's not displaying the command? Please share any past history with the workspace that you recall and we'll take another look. Thanks!!

I have confirmed Migrating a stock workspace (in my case Designer/Design Suite) from 2016-2024 into 2025 retains the context menu, "New Roof from Unstyled Roof" command. Best I can tell, the command is not being removed, if it previously existed. Which points to Patrick's comment, the issue may stem from using an earlier workspace where the command did not previously exist. I'm not aware of a way to add these command via the Workspace Editor and let me see what I can find out...

We'll be curious to what you find. Possibly a support file from 3rd party software is overwriting the same file we install, just a different version?

Thanks for the additional notes @AlanW By chance, do you still have the install of Vectorworks that fails with the mentioned menu items? If so, I'm curious if a, 'Repair' would restore their functionality? If you still have the install: -Open your Vectorworks application folder -Open the, "Vectorworks 2025 Install Manager" folder -Launch, "Vectorworks 2025 Install Manager.exe" -Refresh/update if asked -In the upper-right corner, click the three line icon (hamburger) and choose, "Repair" -Try those menu commands again once the repair is finished

I'm curious to know what happens when you attempt to execute the commands you mentioned. Do you receive an error, does it do nothing or...? Can you confirm the issue is on Mac or Win?