Matt Panzer

OK great! I'm guessing WinDoor was updated to fix the issue at some point.

Try going to Install Partner Products and choose "Reinstall" under WinDoor.

Strange. I don't see this issue in you file on VW 2023 SP7 or VW 2024. Have you tried restarting Vectorworks? Or maybe reinstall/update WinDoor?

Thanks for pointing these out and for the file. We are aware of issues related to the gap under leaf (VB-198298). However, I attached your file to make sure the fix will include these cases.

OK, right. And the centers are snappable in a regular wireframe viewport as well because the model is shown as a whole.

I think this is a bug & it needs to be picked up by any VW people reading this. I don't know if it's related to what's discussed here: https://forum.vectorworks.net/index.php?/topic/111074-radial-dimension-tool-not-working/ I would say this is a technical limitation rather than a bug. Hidden Line renders are a collection of lines generated from the model. So, those circles are no longer circles. Actually, since those are really holes subtracted from a solid, I'm not sure you can snap to the centers in the model either (I'd need to test). I certainly get why you want to have this but wanted to explain why it is the way it is.

What version of Vectorworks are you using? Can you attach a simple file with the wall and window in it?

In Vectorworks 2023 and later, you can use interactive sizing (with the Selection Tool) to do this with doors and windows. ScreenFlow.mp4

Thank you for bringing this to our attention! I am able to reproduce this issue as well. Bug reported (VB-200911).

Right. This may very well be "by design" given that the window would have to decide which sashes to change. Probably the best way to deal with this is to lock the sash width/height you want to keep before changing the mullion dimensions. However, changing the column or row number is another story.

Thanks for the file. I see the problem as well and reported it (VB-200905). A workaround is to select the "Use wall closure" option in the Plug-in Object Options for the window.

OK thanks! I can reproduce and reported the issue (VB-200901).

Yeah. About 5 Kilometers from the origin seems to be where things get weird. I believe this more of a floating point math limitation in computers (or graphic cards) than it is a software issue. Either that or maybe it’s due to an artificial limitation for performance reasons. I do know other software has similar limits.

Can you attache a VWX file with that window in it?

Great to hear that fixed it! 🙂