https://community.graphisoft.com/t5/Modeling/Adjacent-sites-with-conflicting-stories/m-p/282893#M146273 Rather than bringing in a multi-storey hotlink you can bring in each storey as a separate hotlink.<BR /> You then place these in the storey of the master that best matches (although that really doesn't matter) and then manually adjust the height of the hotlink so it all looks normal again.<BR /> <BR /> Or you can save as a GDL object and just add that object to your other file - a morph should work as well.<BR /> <BR /> Barry. Wed, 15 Jul 2015 03:48:38 GMT Barry Kelly 2015-07-15T03:48:38Z https://community.graphisoft.com/t5/Modeling/Adjacent-sites-with-conflicting-stories/m-p/282892#M146272 <DIV class="actalk-migrated-content"><T>Hi all,<BR /> <BR /> I'm working on two projects for a client. They are side by side on a sloping site. I've designed one residence already. It has multiple levels/stories. I'm now working on the site next door and I would like to present the two designs to the client in a single project so that I can render and fly around the the projects.<BR /> <BR /> I am wondering what is the the most efficient way to do this? I can't seem to find a way to bring in a hot linked module with many conflicting storey heights. Alternatively should I convert the first design to a different file and play with the stories?<BR /> <BR /> Perhaps I could convert the entire job into a morph?<BR /> <BR /> I work solely on single low and med density residential projects and this is rarely an issue. But I would imagine everyone who works in large projects has a work around for this issue. Would someone please enlighten me or direct me to a thread or blog that addresses this issue?<BR /> <BR /> Many thanks everyone.</T></DIV> Wed, 24 May 2023 17:26:30 GMT https://community.graphisoft.com/t5/Modeling/Adjacent-sites-with-conflicting-stories/m-p/282892#M146272 Anonymous 2023-05-24T17:26:30Z https://community.graphisoft.com/t5/Modeling/Adjacent-sites-with-conflicting-stories/m-p/282893#M146273 Rather than bringing in a multi-storey hotlink you can bring in each storey as a separate hotlink.<BR /> You then place these in the storey of the master that best matches (although that really doesn't matter) and then manually adjust the height of the hotlink so it all looks normal again.<BR /> <BR /> Or you can save as a GDL object and just add that object to your other file - a morph should work as well.<BR /> <BR /> Barry. Wed, 15 Jul 2015 03:48:38 GMT https://community.graphisoft.com/t5/Modeling/Adjacent-sites-with-conflicting-stories/m-p/282893#M146273 Barry Kelly 2015-07-15T03:48:38Z https://community.graphisoft.com/t5/Modeling/Adjacent-sites-with-conflicting-stories/m-p/282894#M146274 Thanks Barry. I went with the morph in this instance. If anyone else is wondering about this topic, I found this conversation quite helpful.<BR /> <BR /> <A href="https://www.linkedin.com/grp/post/796267-5844516897051152387" target="_blank"><LINK_TEXT text="https://www.linkedin.com/grp/post/79626 ... 7051152387">https://www.linkedin.com/grp/post/796267-5844516897051152387</LINK_TEXT></A><BR /> <BR /> Cheers Wed, 15 Jul 2015 03:52:30 GMT https://community.graphisoft.com/t5/Modeling/Adjacent-sites-with-conflicting-stories/m-p/282894#M146274 Anonymous 2015-07-15T03:52:30Z https://community.graphisoft.com/t5/Modeling/Adjacent-sites-with-conflicting-stories/m-p/282895#M146275 There is another option if one project is completed <BR /> That is to simply merge the completed project into the new story structure of the new project, remove the top links and Preserve Model Geometry.<BR /> This is how IMHO the hotlinks should work.....but the merge helps Sun, 19 Jul 2015 09:29:31 GMT https://community.graphisoft.com/t5/Modeling/Adjacent-sites-with-conflicting-stories/m-p/282895#M146275 David Shorter 2015-07-19T09:29:31Z