![](https://forum.vectorworks.net/uploads/set_resources_20/84c1e40ea0e759e3f1505eb1788ddf3c_pattern.png)
doug shaffer
Member-
Posts
230 -
Joined
-
Last visited
Reputation
6 NeutralPersonal Information
-
Occupation
architect
-
Homepage
www.msmkc.com
-
Location
kansas city, mo, usa
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
Representation of Window Sills in Masonry Walls - 2D
doug shaffer replied to doug shaffer's question in Troubleshooting
It appears that VW Update 2 did not address this window issue. Is that correct? Thanks - Doug -
Well, I downloaded VW 2024 Update 2 and there are still problems with windows with custom sash settings. ARGH. In a two sash custom window, strange things happen when making the left sash wider than the right sash. If the left sash is narrower than half the width of the overall window, everything is okay. The attached file shows the problem. I discovered this within five minutes of using VW with Update 2. Please let me know if you can recreate this problem. Very frustrating.
-
Representation of Window Sills in Masonry Walls - 2D
doug shaffer replied to doug shaffer's question in Troubleshooting
That all makes sense, Matt. Thanks for your help! -
Representation of Window Sills in Masonry Walls - 2D
doug shaffer replied to doug shaffer's question in Troubleshooting
Hi, Matt P. - To clarify, are you saying that the VW 2024 Update 1 should fix the issue that I originally posted about? (see first message in this topic) If so, nothing has changed for me since I installed Update 1. And if I rotate the wall containing the window the sills get totally screwed up and I have to move it 0" to get it to reset as you described earlier. I also noticed that if you copy the window, paste it in place outside of the wall then drag to insert back in to the wall (or a different wall), the offset is changed to 0". Update 1 did nothing to change window problems as far as I can tell. See attached screen capture. This and the complex window mullion issue are critical issues that need to be addressed asap. Any timeline for a solution? Thanks - Doug -
I can't seem to find anyone else on the forum that's dealing with this issue. Like it says in the subject line, every time I quit VWA 2023 or 2024 I get an error message saying "Vectorworks 202X quit unexpectedly." I have not noticed that there's any file damage when re-opening the files but it concerns me. Is this a bug in VW or Sonoma? I have all the latest updates for VW and Sonoma and I'm using a 2019 MacBook Pro. I can copy / paste the "Problem Details and System Configuration" if that would be helpful. Thanks for any help you can offer - Doug
-
Representation of Window Sills in Masonry Walls - 2D
doug shaffer replied to doug shaffer's question in Troubleshooting
Hi, Juan - I just sent the file. Let me know if you need anything else. I appreciate you and your team addressing this. Best - Doug -
Hi, again - Yesterday I submitted a question (bug) regarding sills not being represented properly when using the Window tool (Vectorworks Architect 2024 - latest update). Today I discovered another problem the 'Custom' configuration within the Window Settings pane. Basically, when I choose a 'Custom' configuration with multiple 'columns', there is a 'mullion' missing between the first and second columns. AND it appears that this missing mullion shows at the opposite jamb side. Attached are two screen captures showing the issue. Also, where can I submit both of these windows issues as a Vectorworks Architect BUG? Thanks for any help you may be able to offer.
-
Representation of Window Sills in Masonry Walls - 2D
doug shaffer posted a question in Troubleshooting
Hello - I have had this problem for many years and many versions of Vectorworks Architect. I am now using the latest version of VWA 2024. I can get the window with trims to cut multi-component walls as I desire but as soon as I turn on the "Sills" everything gets screwed up. Attached are a couple of screen captures that describe the problem more clearly. This seems like a glitch that has never been addressed. Or perhaps I'm doing something wrong? Any help you can offer is appreciated. Thanks -