3 weeks ago
Hello -
I'm updating our office template from AC27 to AC29 and therefore switching from the monolith library to global library packs. I downloaded the step by step migration guide from Graphisoft and I need some help with section 6 (see attached). Can someone please walk me through how to update tool defaults? The guide simply says "For each tool, review and apply the correct default settings to ensure they start with the appropriate configurations in your projects." and "Use your updated Favorites to quickly set the correct defaults for each tool."
How do I actually do that, step-by-step? I know I'm missing some general understanding of how default settings and favorites interact, but it's frustrating that this guide is not more specific.
Thank you!!
Operating system used: Windows
3 weeks ago
It's less complicated than it sounds: Whatever is used as current setting becomes the "default" on saving the template.
So you just walk through all the sections and put in some sensible data, that makes sense for you and for your work.
I actually rolled out "reset" favorites for my office – when in doubt the user can go back to these and have a good starting point.
You can also use the eyedropper, that way you ingest everything from a placed element.
3 weeks ago
- last edited
2 weeks ago
by
Laszlo Nagy
Hi,
First of all, thank you for the methods you mentioned.
I just want to add a small note about using the eye dropper tool. You may already be using this.
I think it’s critical to modify the element transfer settings that appear before injecting the parameters. If the properties of the elements to be transferred aren’t set correctly here, there may be issues.
Br,
Sefa
3 weeks ago
Thanks you two! I now understand that it's as simple as opening each tool, adjusting it's settings, clicking "OK", saving, and then closing the template. That being said, I still have some questions:
@sefa Can you please expand on that and give an example of how there may be issues?
In general, I'm confused by the sections in my attachment that say "it is essential to update these defaults before applying your template to prevent missing library parts"and"These components also require default settings, so ensure they are properly updated to match your defaults and prevent missing library parts".
I'm struggling to understand how not setting default changes could result in "missing library parts". Can someone please enlighten me?
Thank you!
3 weeks ago
@RileyDA schrieb:I'm struggling to understand how not setting default changes could result in "missing library parts". Can someone please enlighten me?
If you do not check and change it the tools will still try to refer to the old, monolithic objects.
Which of course are not available anymore after you switched to the global lib.
3 weeks ago
I think I'm getting confused by how you're using the words 'tools' vs. 'objects' vs. 'library parts'.
I understand that the monolith library objects won't work if I have global libraries packages loaded. I don't really understand how a 'tool' (such as the stair or curtain wall tools) could be missing. Maybe some one could break it down for me piece by peice with a hypothetical example of how incorrect default settings could result in missing library parts.
Sorry I'm not getting it!
2 weeks ago - last edited 2 weeks ago
Well, the tools from the tool box in your Archicad obviously stay where they are and don't go missing themself.
A tool in the context of Archicad usually means a tool that models a certain construction element. So the wall tool draws a wall. So far so unsurprising and pretty obvious.
Now, some tools employ user programmable elements. Those are better know as objects, or library parts. Every object is part of a library. And the library is a collection of objects. If a library is not loaded then the placed objects will go missing: They are replaced by a big fat black dot in plan.
The tool with the little chair as an icon is the object tool.
The object tool is the most obvious way to place a library part. E.g. furniture.
Now, there are other tools that can use library parts to form itself. Doors and windows come to mind. They are actually objects. You could (with a lot of elbow grease) script them yourself! They differ internally so that only the specific tool can use these objects, i.e. you can not place a window with the door tool or the stair tool.
However, the list goes on. Stairs, Railings and CWs also consist out of library parts.
Hope that clears it!
2 weeks ago
Thank you so much for breaking that down, @runxel! Your explanation does match my understanding, but I'm still missing what this has to do with default settings. I should add that my library manager is not reporting any missing library parts, so I'm guessing I don't need to worry about this too much, but I'd still like to understand the logic.
Would you mind giving me a hypothetical example of how incorrect default settings could result in missing library parts.?
2 weeks ago - last edited 2 weeks ago
Just because the library manager does not report anything doesn't mean you're out of trouble (e.g. missing macros could be skipped over, but let's not get too technical here). It reports only missing objects from already placed elements (note: Favorites are virtually placed, so they count here as well).
However, I just tested it a bit, and usually the non-deletable integrated library parts should take over and prevent referencing missing, unloaded library parts.
But I know that I've definitely seen it in the past. So it's just a double check, and for sure if you want to place an element you want some sensible defaults. But again, that's of course doable by just employing a base line favorite as well.