Window sill/header height bug?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2020-12-12
12:54 PM
- last edited on
2023-05-26
02:10 PM
by
Rubia Torres
EDIT: After playing around with this some more, it seems like the bug only shows up BEFORE you place a window. It works as I think it should if you are editing an already-placed window.
--------------------------
Richard Morrison, Architect-Interior Designer
AC26 (since AC6.0), Win10

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2020-12-13 06:01 PM
So, it seems to me that when the "Sill or Header Height" field is using the "Header to Story" option, and I modify the Height of the Window, the Height value field will update and display an incorrect result. However, when I place it, it turns out that it places it correctly. So for me, it is only the field that displays the incorrect result prior to placement.
AMD Ryzen9 5900X CPU, 64 GB RAM 3600 MHz, Nvidia GTX 1060 6GB, 500 GB NVMe SSD
2x28" (2560x1440), Windows 10 PRO ENG, Ac20-Ac28
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2020-12-13 06:41 PM
--------------------------
Richard Morrison, Architect-Interior Designer
AC26 (since AC6.0), Win10

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2020-12-16 10:45 PM
Can you point me to the right direction? Are we talking about the same parameter?
Here is my test with a default setting dialog (before a window is placed). As you can see, I set the "Sill/Header value" to use "Header to Story 0", changing the window's height does not affect the other value.

Best regards,
Minh
Minh Nguyen
Technical Support Engineer
GRAPHISOFT
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2020-12-17 12:31 AM
--------------------------
Richard Morrison, Architect-Interior Designer
AC26 (since AC6.0), Win10

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2020-12-17 04:49 PM
After some trial-and-error, I managed to reproduce the issue. It happens if you switch to another type of door/window while changing the Default Settings. As Richard already pointed out, this is just a visual glitch, and won't affect the real position of the door/window. The
I entered it as a defect in our database. Hopefully, it won't be a difficult one to fix!
Thank you very much for reporting this, Richard! It is definitely a well-hidden one!
Best regards,
Minh
Minh Nguyen
Technical Support Engineer
GRAPHISOFT

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2020-12-19 01:12 AM
I entered the values in the Info Box, that is where I reproduced the issue, I have not entered the Settings Dialog.
AMD Ryzen9 5900X CPU, 64 GB RAM 3600 MHz, Nvidia GTX 1060 6GB, 500 GB NVMe SSD
2x28" (2560x1440), Windows 10 PRO ENG, Ac20-Ac28

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2020-12-21 03:15 PM
Thanks for the new info! I just tried it out and indeed it happens with the Info Box. I updated the defect entry with this comment.
Have a great day!
Best regards,
Minh
Minh Nguyen
Technical Support Engineer
GRAPHISOFT