placing doors and windows

[Anonymous]

in ac10 after merging walls to form a complex profile i can not get doors and windows to appear when i place them in my custom complex profile. has this been encountered before and is there a fix available?

[TomWaltz]

Are your doors/windows at a height that shows on the current story?

I've seen a lot of instances where windows are being placed at 6'-8".... relative to a floor three levels above the current one.

[Anonymous]

i do have multiple stories but i am indeed on the correct story, the bottom of door is at 0 relative to my story (i just double checked) another part to this problem is that when placing a door an empty opening equal to the opening i made in the parameters dialog box appears with a blue dot in the middle and the dimensions of the door per usual, however the door symbol and swing does not appear, furthermore if i select the door and open the door tool i receive a warning "Index value greater than array dimension at line 156 in the Master script of file wa_trim_us_10.gsm." i am using ac10 doors from the out of box library not any doors that i have created

[Anonymous]

When you speak of "merging walls" I assume you are referring to a profile wall.

I have also seen this problem with that particular GDL macro. It seems that wall skin definitions in the profiled walls are handled in way that the macro can't handle. That particular macro is elsewhere becoming known as "notorious".

[Anonymous]

i used the merge wall function as follows; drew to walls parallel to each other (cmu wall with furring) then went to Design > Complex Profiles > Merge Walls. i gave it a name and this is what i have been referring to as "complex profile" or "profile wall"

[Anonymous]

adamh wrote:
i used the merge wall function as follows; drew to walls parallel to each other (cmu wall with furring) then went to Design > Complex Profiles > Merge Walls. i gave it a name and this is what i have been referring to as "complex profile" or "profile wall"

That's what I thought. What I said before about some windows in the profiled walls still applies. Until the parts are fixed, the only solutions are to use a different window or figure a way to avoid using the profiled wall.

[Anonymous]

Well...

I've got another solution.

I just fixed the wa_trim_us_10.gsm macro (attached).

It now seems to work with a profiled wall. I have only tested a single instance where I know it was failing and it now works fine in this one case. It should work in all profiled walls now. (There may be other problems with this part that are not fixed by this repair.)

To use it, you will need to extract the library container file and replace the old macro with this one. You can find it in the extracted library at:

//Object Library 10/MACROS 10/D-W Accessories 10/Window Accessories 10/Trim Macros 10

BTW: If you extract the library to the same folder it is already in you will need to remove the .lcf file or you will end up with over 7000 duplicate library parts.

[Anonymous]

Hello Matthew,
May I ask what you did to fix the wa_trim_us_10.gsm macro ?
Peter Devlin

[Anonymous]

Peter wrote:
Hello Matthew,
May I ask what you did to fix the wa_trim_us_10.gsm macro ?
Peter Devlin

I went to line 156 in the master script and found an IF statement that essentially said "If there is more than one wall skin assign all the following values..."

Apparently the profiled wall has more than one skin but not all eight that are assigned (used or not) to composites.

I just changed it to the following:

!! BRICK VENEER CALCULATION !!
ws1=WALL_SKINS_PARAMS[1][2]
IF WALL_SKINS_NUMBER >1 	THEN		ws2=WALL_SKINS_PARAMS[2][2]
IF WALL_SKINS_NUMBER >2 	THEN		ws3=WALL_SKINS_PARAMS[3][2]
IF WALL_SKINS_NUMBER >3 	THEN		ws4=WALL_SKINS_PARAMS[4][2]
IF WALL_SKINS_NUMBER >4 	THEN		ws5=WALL_SKINS_PARAMS[5][2]
IF WALL_SKINS_NUMBER >5 	THEN		ws6=WALL_SKINS_PARAMS[6][2]
IF WALL_SKINS_NUMBER >6 	THEN		ws7=WALL_SKINS_PARAMS[7][2]
IF WALL_SKINS_NUMBER >7 	THEN		ws8=WALL_SKINS_PARAMS[8][2]

This performs the identical function as far as composites are concerned so it shouldn't break anything that the part already does. It burns a few extra clock cycles, but I didn't feel like performance tuning it. Of course this doesn't mean that the trims will actually work in any predictable way with profiled walls, they just don't break the whole window.

[Anonymous]

Hello Matthew,
Thank you for posting back and answering my question.
When you posted your fixed version I immediately
downloaded it and without hesitation replaced the one in my library,
thinking to myself if Matthew worked on it its got to be better.
I then thought to myself, man, Matthew Lohden has
a lot of guts to start fiddling with that macro that I have
looked at and have come away thoroughly daunted.

I salute you and thank you for making it work better.
Peter Devlin