Wishlist

I’d like to propose a significant evolution of the Publisher in Archicad: turning it into a workflow automation hub, capable of executing predefined actions or tasks in addition to the current publishing operations (Print, Plot, Save as PDF/DWG/etc.).

Think of it as “Photoshop Actions” for BIM — a customizable list of steps that can be bundled into a single command, reducing repetitive work and improving project consistency.

Key Features:

1. Task-Based Pre/Post Publishing Actions

   • Run housekeeping tasks like:

     • Update & relink Hotlinks

     • Consolidate 2D Drawings

     • Fill consolidation

     • Audit libraries / remove unused items

     • Purge unused attributes

     • Run model checks (collision, model compare, etc.)

     • Compact project files

2. Run Python Scripts

   • Ability to assign custom Python scripts as part of the publishing sequence.

   • Useful for advanced users managing data exchange, IFC manipulation, naming consistency, property population, or custom exports.

3. Sequencing and Dependencies

   • Define the order of operations:

     • e.g. First update hotlinks → then consolidate fills → then save PDF set.

   • Conditional actions (e.g., “only consolidate 2D if drawing count > X”).

4. Presets / Saveable Workflows

   • Allow users to save and share automation presets across projects and teams.

   • Could be integrated with BIMcloud for team-wide deployment.

Why This Matters:

• Saves Time: Reduces repetitive manual setup before every export or issue.

• Increases Consistency: Ensures the project is in a clean, reliable state before deliverables go out.

• Enables Smart Automation: Allows power users to extend Archicad’s capabilities without needing external task runners or scripting tools.

• Scales Across Teams: Supports enterprise-level workflows where manual steps become bottlenecks.

Example Use Case:

At the end of each week, a team member clicks "Issue Set - Week X".
Archicad:

1. Updates all hotlinks

2. Consolidates fills and 2D elements

3. Runs a Python script that renames PDFs with revision data

4. Saves the drawings to PDF and DWG formats

5. Notifies the team via email or places them in a cloud folder

All in one click — no extra steps.

By extending the Publisher into a Task Manager + Automation Tool, Archicad would better support the demands of modern BIM workflows, where repeatable quality and efficiency are key.

Let me know if you'd like me to post this on the Graphisoft forum for you — or would you prefer to post it yourself?

Hey,

in theory edit mode of complex tools like stairs and curtain walls is extremely powerful. In practice, however, this potential is not fully exploited.

So Make Edit Mode available for many more (all) tools and drastically expand its functionality

For Example:

Profiles:

"Editing a Profile in a separat Window without the possibility of a trace...Realising that the Modifiers are not so great as they should be.....NOOOO"

- Just open the placed Profile in edit Mode and change it directly in the View you are in!!

- convert anything you have drawn into a complex profile just with a click

- add formula based modifiers

- create advanced dependencies to other elements

Walls:

"Annoyed by the last Century solution of Building material priority based modelling, forcing you to create the 7th Insulation Material just for proper connection?"

- Change the connections of  wall skins graphically in edit mode

- change the wall to a sloped wall if you desire

- Create Wall segments without splitting it to peaces ....yeah in edit mode

- Alter every skin to your liking in guess what...edit mode

- add formula based modifiers

Morphs

"Tired of the lack of sophisicated modelling capabilites of the polymodelling old morph?"

- Use Parametric Modelling capabilities inside the edit mode

- Create Voids Forms Sweeps etc with history.

- Convert your Morphs to Nurbs

- add formula based modifiers

Doors and Windows

"Doors and Windows....common. Make a better Door and Window Tool finally. I AM GETTING OLD NOW!!!!"

- Edit Doors and Windows graphically like the curtain wall tool

could go there forever and it works with every tool, but I leave the rest to imagination.....

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.

Now it's possible by double clicking on a view to show your design option if saved right in that view. By making multiple views you can show/switch between all different design options.

My wish: an option to save "set as default" in a view. This way it is possible to draw immeditaly on the right design option in stead of having to "relink" new line's/objects after the fact.

So in short: by clicking on a view in the view map "the pen" as shown in the picture below shifts to a desired design option set by the user and saved in a view

Archicad lacks a system for defining global variables that can be referenced throughout the project. This would be a Variable Manager, similar to the Attribute Manager, allowing users to:

• Define custom variables (e.g., zoning limit, roof pitch angle, floor‑to‑floor height).
• Use these variables in element parameters (roofs, beams, walls), ensuring one change updates all linked elements.
• Reference these variables in labels, texts, schedules, and expressions.
• Optionally, define calculated variables (derived from schedules or expressions) to make model behavior data‑driven (e.g., set building heights automatically based on volumetric limits).

Example use cases:

• A single variable for roof pitch, controlling multiple beams and layered roof structures.
• A planning regulation variable (e.g., max GFA) used for live compliance checks and dimension constraints.
• A ventilation area variable, derived from effective openable window sizes, used in multiple calculations and labels without manual updates.
• Variables controlling design option parameters, enabling quick scenario testing.

Why this is useful:

• Introduces true parametric modeling without requiring complex GDL scripting.
• Reduces manual, repetitive edits across the project.
• Makes urban planning and regulatory compliance more efficient.
• Brings Archicad closer to rule‑based BIM, where design can adapt to changing conditions via shared variables.

Provide the option to not auto join beams in plan - beams are typically used to model curbs – should they have different heights we need to show a line in plan where the height changes. Current workarounds require either a 2D line or separating the beam ends by a fraction of an inch to mimic this line.

Also problematic when using the Beam tool to model foundations and footings - when footings have different dimensions and elevations and auto-join, there can be very strange results in 3D.

Currently, Archicad properties can use single-value lists (option sets), text, numbers, or expressions — but often in real-world workflows, we need structured data with multiple related values. I'd like to propose a new type of property: Table-Based Properties.

This would allow users to create or link to a multi-column table (like an Excel or CSV), and assign a row to an element. Each column in that row could represent a related value (e.g., code, description, unit, cost, etc.), with control over which value is used where (display, label, schedule, export).

Core Features:

• Property type: “Table Lookup”

  • Users select one row from a table

  • Each row includes multiple columns (fields)

  • Users can choose which field to output/display per context (label, schedule, IFC, etc.)

• External Table Support:

  • Link or import data from CSV or Excel files

  • Update or refresh table content when the source changes

  • Could also be managed in the Property Manager

• Selectable Fields for Output:

  • Example: Pick a row for a wall type → Schedule displays cost, Label shows description, IFC exports classification code

• Optional Field Mapping:

  • Define which column maps to which IFC field or Archicad property (e.g., “Cost” → Classification, “Weight” → Quantity)

Why This Is Useful:

• Reduces Redundancy: Avoids having to create multiple properties (e.g., Material Code, Description, Cost) and maintain them manually

• Supports Data-Rich Workflows: Ideal for specification management, classification systems, pricing, cataloged components, etc.

• Improves Consistency: Selecting a single row ensures all related values are in sync — no more mismatched descriptions and codes

• Connects with Excel-Based Teams: Lets non-Archicad users (specifiers, cost consultants) maintain data that syncs back into the model

Example Use Case:

For a wall element, select “W-01” from a lookup table:

• Label shows: “Ext. Insulated Wall”

• Schedule shows: U-Value, Cost

• IFC export includes Fire Rating

This kind of structured property would bring Archicad closer to data-driven design and connected workflows, making it easier to manage specifications, cost plans, and compliance data in complex projects.

This could work beautifully alongside Archicad’s Property Expressions and Python API — let me know if you'd like a combined post about advanced data workflows!

I’d like to see Archicad provide the ability to display U-values directly on labels or automate them through properties, using the assigned physical properties of composites and complex profiles. This would greatly streamline energy performance assessments and documentation.

Additionally, while Archicad currently allows users to add custom physical properties, these are project-specific and must be recreated for every new project. It would be highly beneficial to have a centralised material property manager or library where custom physical properties can be stored and shared across multiple projects. This would increase efficiency, maintain consistency, and expand the available material database for future use.

These features would enhance workflows for energy analysis, compliance reporting, and material specification. I’d love to hear if others see the benefit of this as well!

Diego Rojas

BIM Architect

You can switch the reference lines of Walls and Slabs without changing their overall position, but you can’t do that for Beams and Columns.

(not to mention that roofs have their reflines always on the wrong – the lower – side which of course should be the opposite )

A vote for more consistency

Allow all GDL-object related parameters/attributes to be changed via Property Values/Excel

As part of the awesome features of Archicad is the way to extract or show native 2D / 3D previews for each elements on Schedules. 
Since Archicad 27, MEP elements aren't capable to show this previews. Instead you get a blank cell. This is sad.
Why loosing an awesome feature with a "hopefully. near future" awesome MEP Modeler?

This is important due to:

1. Gives to the viewer, designer, reviser and client the capability to know wich element is beign extracted
2. Gives the designer to take notes over the preview 2D / 3D cells (as you can do on Door or Window schedules)
3. Communication is important, so graphical communication is a distinctive of Archicad. Please mantain that.

Simple one from me this time I promise!

Do you know how CTRL+Up/Down means you can easily move through Stories?

Let's do the same thing for Elevation Sets, you could even change it up and do CTRL+Left/Right if you wanted to be cool!

I mean there are cameras too, but hey, if they can't do it...

The short and simple version:

We would like to be able to move the Graphisoft folder under the user profile (C:\Users\%Username%\Graphisoft).

Extended with context: ArchiCad has a lot of cache functionality built in, that needs to be stored somewhere. The Graphisoft folder is the spot for most of this data. The (usually) largest sub folder amongst these was the TW data folder, which we're now able to relocate. And we are very thankful for that. 

But there are other reasons why the main Graphisoft folder can grow (too) large in size (>100GB). We can delete some older files from previous versions, but that is -sadly- not enough. Therefore, we would like it if we had the option in AC to move this Graphisoft folder to a different location. 

Oddly enough, people who use ArchiCAD tend to also use various graphic design applications too.

As a result, there are typically hundreds of accumulated installed fonts on a user's system.

Currently the ArchiCAD font selection drop down within GDL objects is thus excruciating to use - the only navigation option within the dropdown is by RSI-inducing mouse wheel scrolling - meaning the user can spend a frustrating minute or two scrolling, every time, before they find the font they want.

What should be in these dialogs to help the user get directly to the required font is:

1. Slider gadget down the side of the list
2. Name search field
3. And of course, a favourites option - where the last used 5-10 fonts appear at the top of the list in their own small quick select preview window, with the dialog focus starting on those favourites, rather than at the bottom end of the list, hundreds of fonts away.
4. Optional office standards 'enforcement' override that simply defaults to (and self-updates when there are changes) to a centrally managed office or project standard font & pen.

All of the first three navigation features should also be applied to drop downs for line styles, fills, and all other properties selection dialogs.  Including when those dialogs are invoked by library parts.

Right now we don't even have consistency between font and line style dropdowns - line style dropdowns do currently have the slider and search field at least, even if lacking the favourites.  Fonts however have nothing but the scroll wheel.

Related to this 'office standards enforcement' idea is that any object containing text should be subject to it -  notes, dims, markers and text elements, and even text generated by GDL, should respect the user's office standards, even in the case of GDL if the fonts, sizes or pens are hard coded or controlled by deeply buried parameters that would otherwise take an age to find, and even when the object was created long before office standards enforcement was contemplated.  The GDL interpreter should have an interrupt for any text generated

Where the results are not as desired, the override mode can be disabled for that object instance.

This would cut through the timewasting pain, trial, and error that results whenever many ill-disciplined hands touch the project, or even when you make a careless mistake yourself, or import objects and files from other office's projects and platforms, or even your own office, that were created long before the adoption of your current office graphical standards.

This could be a separate wish, except for the fact that as an option 4, there would be value in including the 'enforcement' option in font dropdowns - right where the user can simply click to instantly respect the prevailing font - or explicitly choose to make an exception and override it

The renovation filter in the windows and doors tools offers greater flexibility.

It allows users to specify that only the window is being replaced while keeping the existing opening in the wall. It also allows users to choose to demolish only the shutters, not the entire window.

The same applies to doors: users can specify that only the panel is being replaced, not the frame. Alternatively, they can demolish the door but keep the existing opening in the wall, without having to create a new one if it already exists.

Possibilité d'avoir plus de flexibilité avec le filtre de rénovation dans les outils fenêtres et portes.

Pouvoir dire que c'est uniquement la fenêtre que l'on change et garder le trou dans le mur comme existant. Pouvoir dire que l'on démoli que les volet et non toute la fenêtre.

Idem pour les portes, pouvoir dire que l'on change que le panneau et non le cadre. Ou démolir la porte mais garder le trou dans le mur comme existant sans devoir remettre une ouverture à construire alors qu'elle existe déjà.

It would be useful if element surfaces were linked to design options. This would be especially helpful for apartment block designs, as the Hotlinked units are the same across the various floors, expect the exterior cladding typically changes.

Currently you have to create whole new walls and assign these to different options. This becomes cumbersome when changing windows and doors, and is confusing for less experienced users.

We need a simple button that deactivates auto update of views on all layouts.

When working on many layouts right before a deadline, auto update of views is a complete time thief.

Having everything on manual update is nice, but I think many would prefer to have things on auto update and then be able to enable / disable it "globally".

There should be an options to set colors in layout book and project map for easier visual navigation.

We need to be able to import/export toolbars and menus between Command Layout Schemes. Every time I migrate to a new version I either need to rebuild all my custom menus and toolbars OR carefully add all the new toolbars and menus to my previous WE. It's insanely annoying and a waste of time. If I could just import my toolbars and menus into the default Command Layout Scheme, I would save SO much time every version. It'd also allow me to better customize Archicad because I wouldn't be worried that I have to redo work every year.