Parametric Nested Arrays gone awry - NOT!!

[Steve_Stafford]

I'll leave this here because it might help someone with a similar issue but, it is NOT a bug after all. Support dug into the family more closely and discover some poor constraining work. So my bad... "Q"

I encountered some interesting behaviour after attempting to use a parametric louver in another thread CLICK TO READ (http://www.zoogdesign.com/forums/phpBB2/viewtopic.php?t=637). Read through to see what developed.

Finally,

Revit support filed a bug on this one, it is a problem with what level the imported family uses when there are other levelss below Level 1. I don't fully understand what the technical issue is, suffice it to say, Revit Support logged it.

If you are trying to work with nested parametric families and they "act out", you may be running into this issue. It happens when using the commercial default template as the basis for your project, what I submitted to Revit, and I've personally duplicated it in Residential-Default and the construction template too.

Hopefully, this will save someone else time if their attempts go astray.

[gnl]

I just caught up with the latest news on the thread you mentioned.
As I was a part of the family :), I just wanted to let you know that I have been experiencing problems with nested arrays like the ones you mentioned.

I posted a window in the families forum some time ago which works fine but if I use it in the project I made it for, it goes bezerk... so maybe that's the template problem. I think I used the default template on that project but I'll have to check because I have a set of custom templates I use...

Is there any known workaround? I had 2 and also 3 dimensional arrays to work in the family editor but none of them worked in all situations...
I am using the latest build (I have Revit in 2 languages installed on my machine).

ciao
gianluca

[Steve_Stafford]

Since this issue appears to be based upon levels existing below "level 1" in a project template (levels below the level the family is imported on) there appears to be no work around for an existing project, unless you can get rid of the lower levels.

The work around I used was to create families that were exactly what I wanted (two types) so no parametric array inside...not ideal, but I've moved on.

[Steve_Stafford]

See my original post at the start of this thread for my retraction...NOT a bug...bad constraints on my part.

[beegee]

See my original post at the start of this thread for my retraction...NOT a bug...bad constraints on my part.

Q,

I'm confused ..( so, what else is new ).

See my post in this tread ... CLICK HERE (www.zoogdesign.com/forums/phpBB2/viewtopic.php?p=4735#4735)

Was the problem with the family I made, or one you made ?

If it was mine, can you be more specific re constraints problem. ?
If yours, why does mine work in one template and go awry in another

[Steve_Stafford]

Bohfus Beegee, (both of us)...we each did the "same" thing wrong basically. Joe K at Revit was kind enough to email me a fixed copy and a demo parametric array to examine. I post them here tomorrow so you can see it too. I should have done it earlier but our EyeTee guy was doing so destructive testing :D

[beegee]

OK, Thanks, I'll look forward to that, cos, I still don't understand why its working OK in the current project I'm using it in . :?

[Steve_Stafford]

It has to do with how the array was not constrained, so some members of the array "choose" the "wrong" level as the base level to determine placement. The different templates have different default levels so I'm assuming the templates that the family acts out in just happen to happen levels that coincide with what the family is trying to do...how's that for a lot of words and no answer??

Attached are the two families, louver fixed and the sample one I promised. Hope they help...