We have had some issues trying to change levels in Revit models, e.g. when storey heights or slab widths changes from original design after we placed all building levels in our project. Typical troubles related to this are missing groups or conflict on level-constrained families, even damage or corrupt models due inconsistences generated by this. The question is: does exist a way to automate levels in order to change storey heights, slab widths or distance of multiple levels without all this mess? We tried to solve this assigning a global parameter for building general dimensions, but we noticed this does not apply when changes are made on all levels at the same time.
Sounds like you need more constraints. For instance, pulling and locking dimensions between Levels (in Elevation) would mitigate some the issues you are talking about.
It seems to be that easy, but trouble comes when you start unlocking and changing dimensions between levels, especially when they are mutually constrained.
@jvpantin2 That's the route I would have taken too - create the levels, dimension them, and lock the dimensions. If a level needs to be modified, unlock the dimension first and change the level - the levels constrained by the locked dimensions should move up accordingly.
yeah, that's only one solution. You are describing a hodgepodge of issues in your first post. Hard to advise you with seeing the file. There may be a hodgepodge of solutions.
Out of curiosity, how many unresolved warnings in your project?
Hi @Sahay_R, let me explain it this way, you have a multistorey building and need to change ALL levels at the same time, and also need to change constrains on groups or families related to original distance between levels. If you do the way showed before, you have to change manually each level, and this change won't affect constrains on level-related elementes, such ceilings or lighting fixtures. Maybe I'm asking something wich exceed Revit capabilities or has to be done whit Dynamo. Anyways, thanks for your help!
Yes, @barthbradley, it looks more like a hodgepodge of issues, but think it goes specifically about associate levels with parameters. Now I'm wondering how it works by creating a global parameter (e.g., distance between floors or levels) and apply to dimensions (like in @Sahay_R example). I will try this, but I wanted to hear some experiences before breaking my model. I'm not working on it now but, in fact, there was A LOT of warnings!
Associate dimensions between levels with a global parameter only helps you changing those dimensions more quickly, not eradicating the errors or warnings. If you want to go to the bottom of it, you need to change level one by one, look carefully at each warning and errors to fix them. Then go to other levels, one by one, and take care of similar issues before moving the levels.
I'm also thinking Group issues.
Here are some best practices to follow. Note bullet: "Don't use attached relationships in groups".
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.