Wishlist

It would be great to increase the .LCF File Format size limit to allow a large point cloud file import beyond 4GB file size. 

Thank You

If an opening is created from a selected element (e.g. MEP duct, pipe, or a cable tray) it should change as the parent element is changed. Resized, moved, deleted...

... manual corrections are very time consuming and very prone to errors.

Add products that improve the resolution and lower the facets of perceived complication for a element.

Items like Seating for arenas as so faceted that it is difficult to use in Archicad.  3rd party software has to be used to lower the resolution while still providing the model needed.  We need functionality that Revit currently has so we can compete.

Imbed only files you need access to  (Wall types, etc.)

Keep them in a folder(s) grow with organized wall types on the hard drive

Only imbed if being used so that the files stay nimble.

But let the library be seen and a wall be imbedded only when used.

Keeps the model lean and avoids a loss of wall types as they can grow even on a server

A files structure can also grow to organize these assemblies.

I recently noticed an inconsistency in Archicad schedules and calculations regarding Building Component Thickness values.

Currently, even when multiple building components have exactly the same thickness value, Archicad does not allow them to be merged/grouped properly in schedules or calculations. This feels unintuitive, since identical values should logically be combinable the same way as other numeric properties.

It would be very helpful if:

• Building Component Thickness values with identical numeric values could be merged/grouped automatically.
• Thickness parameters could behave more consistently with other measurable properties in schedules.

Additionally, there is a small but frustrating unit-handling issue:
when perimeter values are displayed in meters, thickness values are still forced into the same unit context. As a result, users sometimes need to display perimeter values in millimeters just to keep thickness values readable and technically correct.

It would greatly improve usability if Archicad allowed:

• independent unit formatting for different parameter types within schedules/calculations;
• for example:
  • perimeter → meters (m)
  • thickness → millimeters (mm)

This would make schedules significantly cleaner and more natural to read, especially in professional documentation workflows.

Thank you!

Draw windows and doors as separate 3D elements (i.e., not within a wall). Currently, the library (objects) is very limited in terms of capabilities (models, settings, links, details, ....)

It would be lovely to have a unique GSID for each group that we can create on the licensemanagment.graphisoft site.
this would open up the possibility for external plugin developers to make floating licensing options available with more ease, and we, the users can manage our respective groups on the same platfrom.

I have also made a Topic entry on the Forum where I have written the case study in a bit more detail, but for ease I am writing it here too:

Case study:

We have worked together with Bimdots, the plugin developer team, and took part in the development of their floating licence managament option.

It works well from their side.

But we have encountered an issue:
When we wish to attach our users to the license pools, we have to add them one-by-one for each given pool by providing their unique GSID handle on the plugins licence management site.

For GDPR reasons (understandably), the users' names are omitted on the plugins platforms, thus when we wish to manage our users' access to the given plugins it can be quite a hurdle to check GSIDs, and to find the correct ones to manage.

So the idea came to us: Since there is an option to create user groups on the licensemanagment site, it would make perfect sense to have a unique group GSID for each separate groupings that we crate. Thus for handling the plugins floating licenses we could provide the group GSID, and the team- and access management can be much more streamlined

Problem: In Archicad 27, the library contained Imperial structural steel sizes (sized in inches). As of Archicad 29, the sizes in the USA template are only metric.

Solution: The Archicad 29 USA Template's Library should contain Imperial beam and column sizes.

Has anyone else come across this issue?

Archicad 29 USA - metricArchicad 27 USA - imperial

Can we please have a quick work around to change symbol fills back to 2D lines? If you have a unique cladding pattern that is repeated every 2m or so or a random coursing repeat for stone every 5 courses can we place a sample of the hatch to one side to then convert it back to 2D lines? This will enable the quick dimensioning of coursing or cladding panels for the repeat panel rather than have it on a work sheet that could be accidentally deleted. Its a bit of a 'belt and braces' approach.

would love a graphic override criteria available to review where keynotes are being used vs just manual text/labels... 
I would love to be able to say:
Element Type _IS_ Text OR
Element Type _IS_ Label AND

Keynote _IS_ Any Keynote

...
change all pens to red

Please fix the tool tips - when we hover our cursor over tools they don't appear (yes they are turned on). From NZ.

When entering edit mode in a curtain wall, every change of the curtain wall scheme in a 2D view requires a rebuid, before the ability of moving scheme lines is active again - even with all geometry turned off.

Step 1 - move a scheme grid line

Step 2 - try to move another scheme grid line without rebuilding your model...

At least for this situation - when all geometry is turned off - this requirement of rebuilding should not exist. It costs a lot of time and is also very annoying.

The Grasshopper connection is currently limiting in the sense that information can be read from Archicad, but only Geometry sent/created through the link can be adjusted.

It would be amazing if such a basic thing as having full parametric control over a model or parts of it would be possible. Sometimes it's really just about updating some parameters or properties in Archicad, not necessarily about the geometry.

One example here:

Re: Use Object from library returns Null - Graphisoft Community

Crazy enough this is not possible yet?!

Would be great to be able to toggle between % and ° when needed in the tracker (2D and 3D geometry)

At the moment and actually since it's introduction, param-o is lacking basic functionality. it is at most as noticed by other users as well a preview of what could have been.

I came across a post from a few years back where Graphisoft argues that only 0.2% of users make use of it. Instead of addressing the elephant in the room they seem to have decided to straight up throw it out the window...

It is hard to not notice that param-o was yet another tool incorporated to "make waves" instead of turning into something useful archicad is really lacking - parametric control or multiple potentially different entities - not to be understood as a per object parameter input.

what could be improved to make it a viable tool which more than 0.2% of users will use:

1. multi-entity parametric logic. At the moment there is no direct way of creating relationships across different entities. This is a huge limitation
2. Improve integration with the rest of Archicad tools. At the moment it lacks any dynamic integration of other Archicad tools.
3. Allow more complex tasks to be performed. Add a scripting node/capability to it. At the moment it is lacking functionality to make it useful for experienced users while still feeling too complicated for entry-level users. It alos feels way more like the unborn baby of dynamo rather than other more user-friendly platforms/interfaces.
4. Incorporating iterability. One of the most basic things to incorporate - the ability to iterate/loop

Link to previous discussion on the topic:
make Param-O coder-friendly - Graphisoft Community

Hi all,

Since I ran into this issue again, a simple wish.

https://community.graphisoft.com/t5/Libraries-objects/POCKET-DOOR-LINE-WEIGHT/m-p/288057

Can we unhide the Cut Line Pen (global: WALL_SECT_PEN) parameter for non-basic walls?

Ling.

Here is the problem: when placing cabinets, they come with a lot of nodes. There are nodes that allow you to stretch the cabinet height, which when stretching from the top does just what you'd expect - it fixes the bottom of the cabinet and stretches the cabinet upward or downward from there. BUT! When you try and stretch the bottom of the cabinet, the whole things gets weird. The top starts to move, and nothing works as you'd want or expect. (In the screenshot, you can see I have clicked on the bottom corner in elevation, but the top is stretching.)

A novel solution: have the bottom stretch on cabinets fix the top point and allow you to stretch the cabinet bottom up or down.

Has anyone else encountered this issue?

Based on the long comuting times the Find & Select > Inside Partially/ Inside Entirely requires it seems as if it takes the entire canvas into account, which defeats the purpose of a localized search.

In other words it seems as if it checks all available entities/elements in the entire canvas within or beyond its borders whether they comply with the partial or entire encapsulation in the defined boundaries.

It would be great if the speed of the find&select tool would be reconsidered so as to reduce the computing time on (especially) busy worksheets, floorplans or any other 2d/3d Representations to at least limit the find&select tool to the visible elements within the view window extents.

Here's the problem: I have a drawing on a layout. The view is of a text box with an offset border. In the view, the nodes are on the border and things can snap to the edge or corner, but when placed on a layout, suddenly I can't snap to the offset border, only to the outside of the text (as if no offset - see attached [the blue circle is where the pointer is]), so the border would get cropped out.

Do I need to explain the solution? Allow us to snap to an offset border when views are placed on a layout.

Try it out. It's frustrating. It's frustrating minutiae, but it should be fixed.