Forum Replies Created
-
Posts
-
In this situation there are 2 workarounds: if there is a limited number of editable hotspots or user parameters then you can add normal parameters for editing, and store their values in arrays. The other way is to have 2 arrays, and if one is edited, then check the differences and modify the other coordinate.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEThe tube command has some limitations: when any parts of your tube is nearly vertical in your current local coordinate system, then the cross section can be twisted, this causes your shadows. The only solution is to split up it to some parts and avoid vertical parts. Maybe an updated tube command can solve this limitation in a future version, but now you can only split it up to parts.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEUnfortunately it is not possible – and I think it won’t be possible in the near future. There are workarounds for many cases – can you tell me the problem with some more details?
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEThanks for the report, I could reproduce it and asked my colleagues to investigate the problem. I’ll come back later if we find any solutions.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEThere are 2 fields in compatibility options which need to be filled with correct values to let the zone determine the depth of the wall and let ARCHICAD flip the window. First you have to set the Nominal Frame Thickness – usually simply gs_frame_thk, but in your object it seems to be the sum of 2 values. Then you have to set the Parapet Wall Inset, which is usually a long calculation, based on some globals and own parameters – this will determine the depth of zone niche.
Did you fill both of them? If yes, and it still not work, please attach a sample, to let me check it.Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEBarry, you don’t need to load the old library when you saving back. It is just needed when you want to use it in the previous version.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEFor the first check I found 2 things:
- Migration table shouldn’t contain the new objects ID – just the IDs of the “old” objects – now only “0E7CFEF3-E934-4BB0-A6AF-949DE2230811” ID should be there
- You need to add the old ARCHICAD version to the migration table – in your example 15 instead of 0, if you want to migrate back between 15 and 16
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEThen it seems it will be a script or migration table problem. Please attach a sample element pair, to let me check it. (If you don’t want others to download your complex objects, then create samples please. It is an open forum, to help each other learn from the problems, so objects uploaded will be available for everybody, we won’t delete them.)
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEBarry,
Backward migration script should be written in the “new” library. This migration process starts, when you save a plan to ARCHICAD n-1 version. Then AC iterates on all placed libpart instances and runs the backward migration scripts and changes the data stored in the project file.
It can’t be done with a simple library change, as it is done in the forward migration.Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEHere is my version – with 3 added editable hotspots for the else branch, and eliminated all other hotspots. I also added 2 length type parameters for the and len.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEThere are examples for the add-on in the Library Developer toolkit, and you can check the “Sill” and “Board” macros in the standard library for examples of using the addon. They are not about the offset function, but they shows how to use the contour array.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEGeoff,
It seems to be a bug in ARCHICAD, I’ll add it to our bug database. While testing it, I found a “dirty hack” as workaroud: if I add the same amount of hotspots in the same order to both the mirrored and normal sides, then all the hotspots starts to work normally. To reach this, I added the len and thk values as params, and created editable hotspots to the block side of your objects, and commented out all non-editable hotspots from your script. I also commented the text type editing hotspot – so I only had 2 editable hotspots on both sides. I hope it helps a bit.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEHeimo,
You should cut the exact size and form of the wallhole you need. You can check the WallholeCut macro in the library – that simple macro creates all the magic about wallholes for our library.
To be able to create smaller polygons for cutting the wall, you can use the PolyOperations addon, which helps you modifying polygons.Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEGeoff, as I said before, there is no guarantee for the upcoming versions. I can’t promise you anything about that.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SEYou can use the font names from our master file, but there can be problems:
- you can’t use those objects without the standard ARCHICAD library
- if we change our master file, then there is no guarantee that your object will work with an upcoming version
If you decide to use our file, you don’t need to script anything, just add one of the font parameters from the master file to your object, and it will work.
Gergely Fehér
Team Leader, Library Team
GRAPHISOFT SE
