Mass family is not displaying properly when loaded into project

[mpukas]

I've created my own mass family by copying the OOTB Mass Gable family. I added some new parameters and changed some view names. When I make some modifications/additions/changes to the mass family (adding addition masses and void cuts) and load it into the project, the changes are not displaying the same as in the mass family itself. The new masses and voids are not in the same place in relation to the main mass - they are not aligned to faces of the primary mass. 

PS - I tried to upload my mass family but for some reason I get yelled at and can't 

[mpukas]

nope, won't let me upload the mass family in a reply either... 

[barthbradley]

Sounds like something in the family isn't constrained properly. Hard to know for sure without seeing the family.  Maybe the Forum will allow you to attach a zipped file?  

[mpukas]

.zip of mass family

[mpukas]

OK that worked to upload a .zip. 

@barthbradley I was thinking something similar, but why the #$#*$& would something created in a family move it's location when loaded into a project???!!!

[barthbradley · Accepted solution]

A lot of stuff in you mass family is unconstrained. Plus your Parameters are Instance Type. They won't be overwritten when reloading. Change all your Parameters to Type kind and it should work.  

Just to be clear: the family doesn't flex properly, because it isn't constrained properly.  I would remove the parameter/labeled dimensions altogether, or constrain the geometry so that it can be flexed properly.   

[mpukas]

@barthbradley   OK I get it now. Thanks! 

But there is still something strange - I create a void extrusion to cut the main mass, lock it's outside edge to the front and side reference planes so it flexes with the main mass; then I create left/right and front/back dimensions and lock them from said reference places to the faces of the void. When I flex the mass left/right the dimension lock constraint stays and the void moves with the mass and stays the same size. But when I flex the mass front/back the other dimension lock constraint throws up an error and has to be removed, and the front of the void moves with the mass but the back isn't constrained so it's size changes. 

I've noticed this sort of behavior in Revit in other cases, where a constraint will work in one direction, but the same type of constraint will not work in another direction. Or one side will work and the other side will not. I seem to encounter an endless number of Revit quirks over the years that I have spent hours upon hours trying to trouble shoot and find work-arounds.