If you've ever tried to nest structural columns or structural framing members and made them shared so you can tag the members independently of the host family, then there is a good chance you've come across this issue. That is the column height or beam length defaults to its original size and ignores its constraints set by the host family. Find out how to work around this.
1 comment:
This solution works for fixing column heights.
However the host level of nested columns ignores the host level of the parent family.
The nested columns get put on the lowest level in the project instead of the level the parent is placed on.
Same problem in 2016. Really annoying AutoDesk.
Post a Comment