Door inverted on placement in plan views

[b-paige]

I'm trying to finish a door family that I've created. When I go to place the door for the first time in a wall in a project, the door is shown inverted or on the wrong side of the wall... After I place it once, the second placement appears correctly.... I would be okay with this however, when the family gets edited or reloaded, it does the same thing on the initial placement... 

Everything is behaving the way I want it to in the family. Is there a setting that needs to be updated that I'm not thinking about or are the elements possibly not being aligned to the correct reference plane? Not sure if it is relevant but the family also includes nested families (plan swing, HM frame, and door panel). Any help would be greatly appreciated.

[joe_keogh]

Hi @b-paige 

Would you be able to share the family so that we can test it?  There are just too many variables to speculate.

[b-paige]

See attached. The nested families I mentioned earlier are also included in my single HM door family which are also associated to the same shared parameters.

[b-paige]

Attached is also the Single HM door

[barthbradley]

Seems to work fine.  Do you mean the facing/orientation in wall? The family as "Flip" arrows to control its orientation on the wall in the Project. 

Flip.png

BTW: Nice job.  

[joe_keogh]

Hi @b-paige 

I'm sorry I am not able to replicate the issue.  was it the double door that was coming in with one leaf swinging the wrong way? 

[b-paige]

The flip commands after it's hosted I understand; it's just the initial placement I'm having issues with. 

[joe_keogh]

I notice you have a lot of Shared Parameters in the Door Family.  Without sharing the Shared Parameter file we can't really confirm what is happening when you load the family.

Is there a Shared Parameter which is controlling the swing of the door, "Swing Internal"  or something like that for example?

[b-paige]

Yeah it was the double door with the one leaf swinging the wrong way. But that's okay. It's a very minor issue. It sounds like it is working okay for you guys so maybe I'll try this on a few other projects and revisit if needed. I just wanted to make sure that I wasn't missing anything obvious before researching further...

I made this based off a family a previous coworker created as well as some research online. You are definitely right that there are a ton of shared parameters (I'm still trying to wrap my head around everything). The door swing is associated with a DOOR PLAN SWING which is tied to both the Door Panel and the Door family itself.

Besides being a little 'buggy' just on the initial placement, I'm sure our office will work through this. Thanks for taking the time to look into this!

[Viveka_CD]

@b-paige 

On further testing your family, there seem to be no issues.

What version of Revit are you using?

Can you shared the shared parameter file and a brief screencast of what you are trying to do?

Regards,

[b-paige]

See screencast and attached shared parameter file below.

[b-paige]

Screencast

[ToanDN · Accepted solution]

Because the nested family is shared.  Make it non shared will eliminate the glitch.  I would just leave it the way it is since there are no sequential issues.

Revised file attached.

[b-paige]

That did it, thanks! I thought it was standard practice to make a family shared if it was nested inside another family but I guess that is not the case.. Can you provide a brief explanation or link on when to make a family shared vs non shared? 

[ToanDN · Accepted solution]

The pros of using shared nested families are:

- schedule-able in projects
- easier to edit - revise it once and load in project instead of load it in several parent families
- control visibility graphics independently from the parent family with TAB select in project


The cons are:

- bloated project browser with shared families / types register
- too many entries to choose from within project if you happen to use Family Type parameters under the same category
- occasional graphics glitches like what you have