hotlinking modules with different story-settings

[Kamelite]

Right now I'm having a problem With hotlinking modules that have different story-settings, how do I keep the individual settings when hotlinking?

Thnx

.Thag

[NCornia]

Kamelite,

At this time you will need to either have identical story settings in both module (Mod or PLN) and master PLN or you should use a method to bring in the module as an element hosted on a single common story.

Are you trying to hotline a building into a site alongside another building or is it a situation where you are hotlinking repeating rooms such as in a hotel or hospital?

If it is the former situation then you should employ a method to bring the building in as a single story element and place it at the appropriate height. One such workflow would be to save the entire building from the Hotlink as a .GSM object and place the object in the master project. As the module model changes you can re-save the .GSM and overwrite the previous one to update the master project.

For the latter situation you can import the hotlink module and choose which story of the Hotlink corresponds to the story in the master project.

We actively discuss the need for more flexible story handling between project files. I will add your post to our next meeting about desired features. Thank you for the post.

Best regards,

[Kamelite]

"NCornia" wrote:
Kamelite,

At this time you will need to either have identical story settings in both module (Mod or PLN) and master PLN or you should use a method to bring in the module as an element hosted on a single common story.

Are you trying to hotline a building into a site alongside another building or is it a situation where you are hotlinking repeating rooms such as in a hotel or hospital?

If it is the former situation then you should employ a method to bring the building in as a single story element and place it at the appropriate height. One such workflow would be to save the entire building from the Hotlink as a .GSM object and place the object in the master project. As the module model changes you can re-save the .GSM and overwrite the previous one to update the master project.

For the latter situation you can import the hotlink module and choose which story of the Hotlink corresponds to the story in the master project.

We actively discuss the need for more flexible story handling between project files. I will add your post to our next meeting about desired features. Thank you for the post.

Best regards,

I have a site, and would like to Place both the house and the garage on the site, for 3D-renderings and such.. But not having the same story height turned out to be a problem 🙂. I'll see what kind of workaround that will work best i my case. I might just don't render the 3D-views from the angles where the height-issue is visible 🙂, since it really isn't that many inches off..

Thnx a lot for the fast reply, highly appreciated!

.Thag

[Anonymous]

NCornia wrote:
Kamelite,

We actively discuss the need for more flexible story handling between project files. I will add your post to our next meeting about desired features. Thank you for the post.

Best regards,

Yes please! Not only the ability to handle storys better, but also Solid Element Operations. I recently had huge problems when I did a project consisting of two buildings on adjacent sites. I modeled each building in its on PLN file, using the same story levels in each file, but when they were hotlinked together, all the SEO's were disregarded and I had a mess!

[Anonymous]

NCornia wrote:
Kamelite,

At this time you will need to either have identical story settings in both module (Mod or PLN) and master PLN or you should use a method to bring in the module as an element hosted on a single common story.

Are you trying to hotline a building into a site alongside another building or is it a situation where you are hotlinking repeating rooms such as in a hotel or hospital?

If it is the former situation then you should employ a method to bring the building in as a single story element and place it at the appropriate height. One such workflow would be to save the entire building from the Hotlink as a .GSM object and place the object in the master project. As the module model changes you can re-save the .GSM and overwrite the previous one to update the master project.

For the latter situation you can import the hotlink module and choose which story of the Hotlink corresponds to the story in the master project.

We actively discuss the need for more flexible story handling between project files. I will add your post to our next meeting about desired features. Thank you for the post.

Best regards,

At times I try the .gsm option when dealing with buildings having different storey settings. Unfortunately when I project a 3D view, the gsm object doesn't appear, or simply appears a simple object such as a portal frame. What could be the issue and how can I resolve that?

[Anonymous]

Hey guys.
The other questions about modules and story settings. We are designing base camp. Now we are making sketch plans (LOD 100) of two buildings (#1 an #2). They are designed at a same time and conjugated but independent for each other by separating of expansion joint. They are performed in different scales (1:100, 1:175 for the correct display of axes, dimensions, etc). I have divided these two blocks in to different Teamwork files and added cross-references for these modules (#1 mod in #2 pln and #2 mod in #1 pln in Teamwork). It helps to display them correctly on working plan and rotate individually with their own scales (#1 — 1:100, #2 — 1:175).

Here is the question. Story settings of #1 block differ from story settings of #2 block. This height difference influence correct displaying of 3D model.
How can I link module (with own story settings ) in teamwork file despite the height of levels with opportunities to restore Teamwork modules?
look at the pictures:

#1 PLN
(Teamwork file with own storey settings)

#1 MOD in #2 PLN
(Teamwork module with incorrect storey settings)

[tworks]

NCornia wrote:
We actively discuss the need for more flexible story handling between project files. I will add your post to our next meeting about desired features. Thank you for the post.
Best regards,

IS there any news on this to be adjusted in future ArchiCAD.
because , yes... this is a big miss... and imo should have priority

It is very time consuming and also easy to make mistakes to adjust all different modules to get them with same story settings.

And it seems so obvious to have it possible to keep their own story settings when assembling different moduels in one master file.
ArchiCAD is a 3d architecture developing software.
In architecture, buildings just do not have the same storysettings.
To make an urban assembly of different buildings is just not possible in an easy manner and it should be.
Making gsm or Sketchup files and then assembly is a workaround, which loses all the benefits of adjusting settings in ArchiCAD, i.e. a complex wall structure is not to be adjusted in the master file influencing the modules.

pleas do make this possible in future... (or did I miss it and is it already possible in AC20?)

with kind regards,

[jakubc7]

Does anyone know if Graphisoft has this on their radar as a fix for v21?
So many things have improved over the years but this really stands out as a long overdue "fix".

As mentioned in previous post, bringing in each individual storey is a decent option, however I have encountered issues using this method where I lost solid element operations between elements hosted on different storeys.

Hope this gets a fix.

[Ruben V]

• - import every story of your HLM as single story
  - unlink heights (option when placing HLM)
  - place it at the appropriate offset on the 'best fitting' story in your assembly-PLN
  - repeat for every story of every HLM you need

Is a big work at first, but when well executed should work properly...

[Anonymous]

I have also encountered this issue.

I am working on a four unit townhouse development on a sloped site, where each unit sits at a different storey height. Currently I am doing everything in one file, and manually drawing my storey reference lines, but that would mean all the schedules are in the wrong sill heights and etc. Which is quite silly, but I don't know how to do better yet.

Hope this is going to be improved in the next version.

Cheers