Wishlist

There are almost 1000 wishes in this forum. Many of them would be obvious improvements - making the software more functional, intuitive, integrated, and dynamic.

Instead of waiting for TWO HUNDRED people to express dissatisfaction on this forum, how about somebody from Graphisoft regularly reviews the wishes for what are almost objectively good ideas and works to get them on the roadmap and into the software?

I've been on this Wishlist since it was created and there's a lot of gold in here. I don't know that we deserve compensation for these wishes as another user has suggested, but I would like all of the good ideas we are putting forth to actually help improve the software.  I know wishes are moving to "Under Consideration" with 20, 30, 40 upvotes. I'm just saying can we restructure this a little?

The community provides good ideas -> Graphisoft reviews *ALL* of them -> The good ones get incorporated, *especially* the ones with many upvotes.

Would anyone else like to see more than a handful of these ideas get into the software?

EDIT: (moving this from a comment into the post)

I think part of what is happening is that the Wishlist forum is fielding both Wishes with a capital W ("wouldn't it be cool if Archicad could ___"), and User Experience feedback ("this tool isn't working as expected", "there are inconsistencies in your interface", "I'm not able to ___ when this happens, but it works everywhere else", "in your latest update, you lost this feature").

There is so much UX feedback - we have essentially become a global UX team, which on the one hand is great - we use the product day in and day out and can easily notice when the experience isn't meeting par. The key is that Graphisoft needs to sort out which "wishes" are aspirational and which are essential. As a daily U, this would greatly improve my X.

The Problem: Architectural drawings are often filled with notes (specifically talking about notes/labels with pointers). To keep the drawings looking orderly, we often try and align our notes to one another. The issue, however, is that the Force Snap Reference command (Q), which allows one to create snap guides from nodes of your choosing....doesn't work when moving parts of a note around.

The solution: Make Force Snap Reference available when moving parts of a note/label with pointer.

Small things make a big difference in day to day work in Archicad. Anyone else?

The ci Keynotes tool was able to generate a keynotes legend that contained all keynotes visible in ALL layouts. This feature was useful in creating a master keynote legend for a project that contractors could reference and also helped with bulk keynote QA. 

As far as I can tell, the Archicad keynote legend object can only list all keynotes or only keynotes present on the sheet the legend is placed to (filtered to the keynote subfolders).

Please expand the legend's filtering options to pull visible keynotes from all layouts, or better yet, pull data from a specific subset of layouts.

The wish is for a view's orientation to be accessible in the view settings, project index and in GDL for drawing titles.

Being visible in the view settings would allow multiple views to be edited simultaneously.  A lot of our standard plan views are set up in the template.  When a project comes along that needs the views rotated, we have to go one by one, redefining the views.  Imagine having to redefine layer combinations this way.

Being visible in the project index would allow all views to list their orientation, allowing a quick QA check.  The "Ignore zoom and rotation when opening this view" setting always finds a way of turning itself on.  This leads to staff thinking a view has been rotated, when it's using the last view's rotation and ignoring the current view's rotation.

Lastly, being visible in GDL would allow a 100% fool-proof north point.   This is an existing wish by Mark Davis and an old desire of mine that keeps coming back.  Ideally the north point on a layout should be generated by the drawing title as this has access to all of the relevant information. 

Design options should be applicable to drawings and figures

Design options should be included in edit selection set

It would be helpful to be able to define the "printable area" - or placement/reference window - as an additional option to be stored potentially in the view map together with the other view related settings. This way the drag and drop of a saved view on a layout (ex. worksheet area) would automatically come in the right format

For now the saved view (of a worksheet with the zoomed area option) is placed on the layout with the window size linked to the scale making numerical adjustments of the frame impossible. Being able to set the window size numerically would also speed up layouting.

Changing any number in the size and Appearance affects all others

Another somewhat similar wish here:

https://community.graphisoft.com/t5/Wishlist/Graphical-adjust-Master-Layout-grids-and-have-it-act-as...

OUTLINE:

Working in a large practice working on high rise buildings often means setting up transmittals with numerous drawings from different drawing typologies - details/GA drawings/Planning drawings/Technical RIBA 4-5 stage drawings/BSR & building control submissions/ etc. This can mean 100+ drawings from various layout folders are added to a transmittal that then cannot be issued due to a delay beyond the control of the architect, but sometimes other drawings need to go out meaning one has to cancel the list and start a new one. 

WISH: Currently only one transmittal can be set up with a single list. It would be really useful if several transmittals could be opened and be held open until closed - like having several Outboxes that would allow various teamworking members to create and populate transmittals and close them when the contents are ready to be issued. 

Being able to create a new transmittal from a historic transmittal could also be useful

WORKAROUND: is taking screenshots and recreating the transmittal but this is time consuming, tedious and subject to error.

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.

When exporting to DWG with "Save Layout into > Paper Space with Cropped View's content", the autotexts related to the Layout info are not shown. Instead they come up as: for example #LayID. We are using title blocks that are placed on the Master layout from a saved worksheet view.

This needs to be fixed, so that it shows correctly on export. 

As this thread remains unsolved for more than 10 years, I believe there should be a wish to solve that: Autotext on Master Layout missings on DWG export - Graphisoft Community

Kia ora,

It would be amazing to have custom line types in ArchiCAD using a fill with selected outline and fill colour.

In addition to this could arrowheads have the option for an outline and a different fill colour?

Can the lines of the arrow head join with a sharp angle rather than a rounded angle, regardless of their thickness?

Here is an example of what I mean:

Thank you

Short Summary:

Please allow selective inclusion of nested modules when linking hotlinks.

Currently, we can only include all or skip all nested modules, which leads to duplication issues in multi-file workflows.

In these situations, modules are often kept as .pln files instead of .mod due to documentation needs, which further complicates coordination. The ability to choose exactly which nested modules to include (e.g., include module E but exclude module B) would greatly improve control and workflow efficiency.

Description:

I would like to suggest an improvement regarding module linking and nested modules in Archicad.

Currently, when linking a module, we can choose whether to include or exclude its nested modules as a whole. However, there is no option to selectively control which nested modules are included.

I am aware that there is already a similar request regarding nested hotlinks, but I found it somewhat unclear and broad. For that reason, I wanted to describe this specific need in a more objective and practical way. (https://community.graphisoft.com/t5/Wishlist/Nest-Module-Exclusion-Options/idi-p/690669)

In complex project structures, this becomes limiting. For example:

• File A (main/master file)
• File B (site/terrain)
• Files C and D (buildings)
• File E (typical floor module)

Setup:

• File A contains modules B, C, and D
• Files C and D contain module E
• Additionally, files C and D also require module B (site)

As a result:

• File A ends up containing B directly, and also indirectly through C and D
• This creates duplication of module B (in A, C, and D)

Even if B is only placed in either C or D (instead of both), duplication still occurs once everything is brought into file A.

The current workaround is to disable nested modules, but this is not viable because module E (the typical floor) still needs to be included.

Additionally, in many of these workflows, modules are maintained as .pln files instead of .mod files due to documentation requirements. This makes the issue even more relevant, as coordination becomes more complex and the limitations of nested module control are more evident.

Request:

It would be extremely useful to have more granular control when placing modules, specifically:

• The ability to choose which nested modules to include or exclude individually
• For example, when placing modules C and D into file A, I would like to include module E but exclude module B

This feature would significantly improve workflow flexibility and help avoid duplication and coordination issues in multi-file projects.

This feature would significantly improve workflow flexibility and help avoid duplication and coordination issues in multi-file projects.

Recent versions of ArchiCAD have included "field settings" for schedules, where one of the options is to "show zero results" as a custom string.

This is great for results with numerical characters, but does not apply to other "null" results such as custom properties with an empty string or with "Undefined" as custom value.

Although a field with an empty string from a custom property may be individually edited to whatever, this is often not desirable as the property may be displayed in labels etc within the project.

Having the ability to automatically display these non-numerical "zero" results as a custom string (like a dash "-") would be very practical, for example in door schedules with not applicable properties.

Changing the materiality along the length of a wall (e.g. color / cladding change) typically involves breaking the walls as needed. This frequently occurs in alignment with fenestration such as doors and windows. 

Unfortunately it is entirely dependent on 100% accuracy - if the wall is cut the tiniest fraction off, the door or window ends up outside the wall and becomes invisible in plan. Often teams then place said door or window again to get it to display - which effectively duplicates these instances, throwing out the quantity in schedules.

Having a feature such as "highlight doors and windows placed outside wall" would really help with cleaning these instances up!

The automatic dimensioning tool would be greatly improved if it would also be possible to include dimensioning openings placed with the Opening Tool. 

In regard to free form openings one could decide to dimension the opening at the Floor Plan Cut plane level as the default. 

It would be nice if the keynote tool allowed an option to include the text or the keynote tag. Similar to how the CI Keynote tool worked.

Hi,

I would like to request a change regarding how Archicad handles decimal and thousands separators.

Currently, the decimal separator (dot or comma) and the thousands separator (dot, comma, space, etc.) depend entirely on the operating system regional settings (e.g. Windows Control Panel). This creates significant workflow issues when working on projects in different languages.

In many offices, it is common to work simultaneously on:

• English projects (e.g. 1,234.56)

• European projects (e.g. 1.234,56 or 1 234,56)

At the moment, switching between such projects requires manually changing the Windows regional settings every time we switch projects. This is impractical and error-prone. It also makes it very difficult to ensure that all workstations in an office are configured consistently.

Suggested improvement:

The decimal and thousands separators should be defined at the project level, ideally within:

Options → Project Preferences → Dimensions (for example inside “Dimension Preferences”)

This would allow:

• Different projects to follow different numeric conventions

• Proper consistency in team environments

• Elimination of dependency on OS-level settings

• Reduced risk of documentation errors

Number formatting is part of documentation standards and should belong to the project configuration, not to the operating system.

Thank you for considering this improvement.

Dear Graphisoft Product Team,

I would like to submit a feature request regarding the Zone Tool in ArchiCAD.

Currently, the Zone Tool defines spatial boundaries primarily through wall recognition. While this is functional, it reflects a structural logic rather than an architectural one. In the philosophy of architecture, space is fundamentally defined by the floor — the ground plane is where human life begins, and enclosure follows from it.

From this perspective, I would like to propose the following:

→ Allow the Zone Tool to recognize and generate zone boundaries directly from a Slab's outline.

In practical terms, this would mean:
- Selecting a slab and automatically generating a Zone that inherits its boundary geometry
- Or allowing the Zone to stay linked to the slab boundary, updating dynamically when the slab is edited

Currently, the relationship exists in reverse — slabs can reference zones (via Related Zone fields introduced in AC24) — but zones cannot originate from slabs.

This feature would bring the Zone Tool closer to the true architectural concept of space: a vessel for life, rising from the ground. It would also create a more intuitive BIM workflow where space definition and floor definition are unified from the start.

Thank you for considering this request. ArchiCAD has always been the BIM tool most aligned with architectural thinking, and I believe this enhancement would deepen that quality further.

Best regards

Wish to wrap the end of wingwalls with the wall lining with a simple check box rather than make a wall-end

its long past due, if dimensions are going to be pinned to a partial structure display, there needs to be a control, either in partial structure display, or preferably in dimension settings, to control which partial structure display the placed dimensions are pinned to.
virtually every one I train on AC runs into this... too many hours spent redoing dimensions to count.