Revit Architecture Forum
Welcome to Autodesk’s Revit Architecture Forums. Share your knowledge, ask questions, and explore popular Revit Architecture topics.
abbrechen
Suchergebnisse werden angezeigt für 
Anzeigen  nur  | Stattdessen suchen nach 
Meintest du: 

Stacked walls split apart after linking into model and " bind" - best practice to model so that future linking and binding works

18 ANTWORTEN 18
GELÖST
Antworten
Nachricht 1 von 19
HVAC-Novice
1051 Aufrufe, 18 Antworten

Stacked walls split apart after linking into model and " bind" - best practice to model so that future linking and binding works

A few years ago I started a project and modelled the existing building. then the project died, and now got re-surrected. Since I now have a better template, i started a fresh project in R2024, upgraded that old project to R2024. So far so good.

 

Then I linked the old project into the new project and did the " bind" and ungrouped the linked parts. Reason i went this route is that copy/monitor doesn't' work with doors etc. (at least last item i tried). For some reason it had to delete the roofs and I have to re-create them. but what really is odd, that the stacked walls (I had a few walls with 2 walls, and one with 3 wall types). I did that twice just to be sure there isn't something I can check to make this work. 

 

This will require some manual cleanup now, which is fine. But since any of my current projects could be the basis for a future project in the same building, I wonder if I should model in a certain way to avoid those linking mis-haps? I can't retrace why the roofs disappeared. but for staked walls I could theoretically create separate walls to begin with. and I also wonder if there are other issues I could avoid by modeling differently? Or is there a whole better way to use an old model for a new project? I work alone on my models, so I don't link a lot at all. 

 

Edit: to be clear, by splitting the stacked wall apart i mean the sacked walls now are like separate walls individually staked on top of each other. I assume a stacked wall is some sort of " grouping" that disappeared in the process.

Revit version: R2025.4
18 ANTWORTEN 18
Nachricht 2 von 19
barthbradley
als Antwort auf: HVAC-Novice

Something screwy is happening for sure.  Stacked Walls shouldn't "Break-Up" inexplicably.  Post the RVT that you are Linking/Binding/Ungrouping. 

Nachricht 3 von 19
HVAC-Novice
als Antwort auf: barthbradley

Attached the original file from some years ago. For the new project I'll do some manual cleanup an corrections (the old model wasn't complete yet).

 

I don't have screenshots anymore, but the middle-wall of the one 3-stack was actually flipped to be outside in the new model. And one of the error messages when binding had me delete the roofs. 

 

If you can tell me what to do different or better next time, that would be helpful moving forward.  

 

HVACNovice_0-1689683842148.png

 

Revit version: R2025.4
Nachricht 4 von 19
ToanDN
als Antwort auf: HVAC-Novice

I linked your model in a 2024 project (Imperial multi-discipline template), bind, ungroup, and the stacked walls remain intact.

 

ToanDN_0-1689703031191.png

 

 

Nachricht 5 von 19
HVAC-Novice
als Antwort auf: ToanDN

I tried it again with the oob template you used and it still is messed up. The 3 walls are separate walls now and the one in the middle is now sitting outside the wall. Basically the same way my OP was based on. So, it isn't a template issue, but must be an actual Revit setting for my PC. I have the latest R2024.1.

 

I see for you the roof also stayed. 

 

Is there any setting or similar I could check? 

 

HVACNovice_0-1689703730121.png

 

Revit version: R2025.4
Nachricht 6 von 19
barthbradley
als Antwort auf: HVAC-Novice

Might be something in the INI file.  Delete it and let Revit build a new one upon re-launch.  

 

...the one in the User Profile Folder.  

 

Help | About the Revit.ini file | Autodesk

Nachricht 7 von 19
barthbradley
als Antwort auf: HVAC-Novice

BTW: I had no issues either, but the RVT you posted was 2024. The way I understood it, you were having issues when upgrading an RVT created in an earlier version. 

Nachricht 8 von 19
barthbradley
als Antwort auf: HVAC-Novice

Just to confirm: you aren't converting RVT to IFC and opening the IFC; are you?  Stacked Walls will break up then.  

Nachricht 9 von 19
ToanDN
als Antwort auf: HVAC-Novice

Check Levels when binding link.

 

ToanDN_0-1689705494057.png

 

 
Nachricht 10 von 19
HVAC-Novice
als Antwort auf: HVAC-Novice

I re-named the ini file (and it created a new one). I tried again with the oob template. Still the same issue. No IFC. This is just a link of the old model (upgraded to R2024) into the new project. I checked levels and grids. 

 

It warns me that what I'm loading is 10MB or greater (true). at that point the model still looks good. 

 

HVACNovice_3-1689706611810.png

 

 

 

HVACNovice_1-1689706129533.png

then it warns me about duplicate types (no dispute). The the wheel spins for a while. then the first (of many) errors shows up and the walls become messed up and the roof disappeared. 

 

HVACNovice_2-1689706321707.png

If I resolve all the errors it proceeds and i can un-group. If I cancel, it cancels the binding. 

 

 

Revit version: R2025.4
Nachricht 11 von 19
barthbradley
als Antwort auf: HVAC-Novice

How old is this RVT? The recommended way to upgrade a Project is sequentially. Do you have that ability?  In other words, do you have the versions in-between to upgrade to? 

 

...if not, your Autodesk reseller might be able to do it for you.  

Nachricht 12 von 19
ToanDN
als Antwort auf: HVAC-Novice


@HVAC-Novice wrote:

 

then it warns me about duplicate types (no dispute). The the wheel spins for a while. then the first (of many) errors shows up and the walls become messed up and the roof disappeared. 

 

 


Share the 2024 file here (without the link).

Nachricht 13 von 19
HVAC-Novice
als Antwort auf: ToanDN

This is the one I created from the R2024 oob template. it should really be the same you guys have. I sue the elum-tool plugin and that will have added some views and generic families. 

 

The file I linked in I think was an R2022 and I directly converted to R2024 (without interim R2023 conversion). but since i still have 2023 installed, I went through the motions to convert to 2023, and then to 2024. It didn't make a difference for the binding. I don't know if the 2022 already was an upgraded file (probably). 

 

i don't think it matters what positioning I use, but here the linking dialog:

HVACNovice_0-1689709604625.png

 

Revit version: R2025.4
Nachricht 14 von 19
barthbradley
als Antwort auf: HVAC-Novice

Post the 2022 RVT. 

Nachricht 15 von 19
HVAC-Novice
als Antwort auf: barthbradley

This should be the original 2022 version (I don't have 2022 installed).

 

And thanks to both of you for taking the time!

Revit version: R2025.4
Nachricht 16 von 19
ToanDN
als Antwort auf: HVAC-Novice

Transfer Project Standards from the 2022 to the 2024 with overwrite types.

 

ToanDN_0-1689710809572.png

 

p/s: I use Revit 2024.1 so you may want to check if your Revit 2024 is up to date.

Nachricht 17 von 19
HVAC-Novice
als Antwort auf: ToanDN

Huh, that worked. At least now I still have the roofs and the walls didn't look all messed up. 

 

To be safe, I transferred ALL project standards. The problem with that is, now my new project (created from a nice clean template) now has all the stuff from the old project. 

 

But here is a weird one. Since I had all that (now to me useless) items that came in through transferring, I un-did all the binding (with undo button). I started over (without transferring standards), and all of sudden the "bind" worked and only had one error, but that error didn't delete the roof or messed up my walls. 

 

So, for now it works for my new project. but I have no idea how to avoid this in the future or how to model better to facilitate future link/bind operations. 

 

I'm on 2024.1 as well. 

 

Thanks, you so much!

Revit version: R2025.4
Nachricht 18 von 19
barthbradley
als Antwort auf: HVAC-Novice

I thought this whole exercise was to upgrade an older project. Why link/bind/ungroup? You lose a lot of work that way.  2022 upgrades to 2024 fine and dandy for me.  Maybe this what @ToanDN means. Use TPS to transfer your new and improved standards into the upgraded version.  Don't know about overwriting though.  I think you need to be more surgical by using TPS a couple or three times with categories selected to overwrite and not overwrite.  

Nachricht 19 von 19
HVAC-Novice
als Antwort auf: barthbradley

No, I didn't want to just use the old project I had set up many years ago. I wanted to use my newer and better template and start a fresh project, but get the old model. 

 

Maybe this wasn't the best example since that wasn't a completed project. But if for example I had a lighting project for the entire building some years ago, and now have an HVAC project, I don't want to just use the old lighting project and then manually clean up all details, annotation, and so on. I basically just need the model (I realize, i will still have all the model families, like walls, and so on)

 

Linking/binding seemed to be the best way to accomplish that. 

Revit version: R2025.4

Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.

In Foren veröffentlichen  

Autodesk Design & Make Report