The Global ARCHICAD Community

Stay informed. Get help. Share your knowledge.

Plot Control, Publishing, Import-Export (DXF/DWG, PDF...), IFC…

Moderators: Karl Ottenstein, LaszloNagy, ejrolon, Barry Kelly, gkmethy

Advanced module publishing options. publish more than a floorplan ?

Essential
1
33%
Important
2
67%
Average
No votes
0%
Not Important
No votes
0%
Not Needed
No votes
0%
User avatar
By Lukas Zeleny
#312028
Archicad is able to publish Module (.MOD) file only from Floor plans Views, It would be handy to be able to publish also other Views like 3D views or other preset selections

In large scale projects and urban project is working with module essentials but we lack the ability to update them more automatic. Many times you need model only from section of building or model and now you have to save it from selection manually. Updates are then time consuming.
User avatar
By Barry Kelly
#312051
Obviously I have no idea of exactly what you are trying to do.
But when you 'save selection as module', you have an option to replace the selection with the module.
Then you will have a MOD file (which you would have had even with out this option) that you can modify should you need to make changes to it.
Because you replaced the original selection, it will update as you change the MOD file (and simply save it) together with all the other linked modules.
No need to actually publish anything - just update the original MOD file then update all other files that have the MOD hotlink in it.

The only downside I see to this is that the MOD is now in a separate file if you need to edit it, so you won't have that contextual interaction with the rest of the model if you need it for editing purposes.
Unless you hotlink the main file into the MOD file - ignoring nested modules so it doesn't bring in the same module you are trying to edit.


Barry.
User avatar
By Lukas Zeleny
#312069
Barry Kelly wrote:
Mon Jun 15, 2020 2:34 am
Obviously I have no idea of exactly what you are trying to do.
But when you 'save selection as module', you have an option to replace the selection with the module.
Then you will have a MOD file (which you would have had even with out this option) that you can modify should you need to make changes to it.
Because you replaced the original selection, it will update as you change the MOD file (and simply save it) together with all the other linked modules.
No need to actually publish anything - just update the original MOD file then update all other files that have the MOD hotlink in it.

The only downside I see to this is that the MOD is now in a separate file if you need to edit it, so you won't have that contextual interaction with the rest of the model if you need it for editing purposes.
Unless you hotlink the main file into the MOD file - ignoring nested modules so it doesn't bring in the same module you are trying to edit.


Barry.
I dont want to replace part of model with module. I want to export this part ind use it in other model. Yes now I can select it and save as mod. But next time when I change something I have to select it again and replace the previous mod file. Simple publish buttom woud be faster and less prone to human error.
User avatar
By Barry Kelly
#312075
Lukas Zeleny wrote:
Mon Jun 15, 2020 9:53 am
I want to export this part ind use it in other model.

That is the whole idea of creating a MOD file, you can use it as many times as you want in as many files as you want.

Lukas Zeleny wrote:
Mon Jun 15, 2020 9:53 am
Yes now I can select it and save as mod. But next time when I change something I have to select it again and replace the previous mod file.

That is why I said that you edit the saved MOD file when you want to make changes.
The problem is that it is the module on its own so you don't have the context of the rest of the model around it - unless you hotlink in the entire model into the MOD file.

Actually it doesn't even need to be a .MOD file, it can just be saved as a .PLN file as well.
You can HOTLINK either .PLN or .MOD files.
.MOD file only contain the attributes they use where as a .PLN file will contain all attributes in the model, even if they are not used.


Barry.