Favorites are great, and will vastly improve our Template for new projects. However, I have made a lot of new helpful favorites in our company template that staff want to use now, in their active project.

When I export any Favorites from the template that contain custom Profiles (to give to folks who want them now), I have to also manually export and then import those Profiles, and hope that adding by Index doesn't overwrite something important in the receiving file. I wish that exporting a Favorite would bring along any of it's attributes, even if I have to manage the Index numbering upon import in the receiving file.

This is most important for Curtain Wall favorites, because we use that tool for everything (usually with custom profiled frames), given that a dedicated ceiling tool doesn't exist.

The new experimental physical renderer appears okay for external building 3d views.  But for internal views there is a strong dark blue cast to shadows which makes the physical renderer useless and unusable for interiors.  This is quite a major oversight, please can you resolve this.  Support say I can't change this:  

'as it's controlled by the procedural skydome which the ambient colour cannot be changed. You can request for the control of this on our public wishlist'

Can this feature be developed into a proper feature as it has value.  I really like the current 'sketch-up' type aesthetic of the current 3d view, and the physical renderer is not yet good enough to use as an alternative.  Thank you.

The amount of used navigator items grows with the project but not all of them are relevant or actively used simultaneously. For views and layouts folders can be used to collapse the structure but the item will still be returned in searches and just having the collapsed top node visible and selectable adds to cognitive load.

To avoid this we first the ability to set the status of an navigator item to inactive and then the ability to filter based on this status in the navigator akin to "hide inactive".

Larger companies using Archicad would like to see the Multi-factor authentication (MFA) controlled on administration level (GSID) to up the security, and not only on user level as it is now.

Ref. to the following page for more information:

https://support.graphisoft.com/hc/en-us/articles/30578874208017-About-Multi-Factor-Authentication-MF...

It would be beneficial to see the advancement of schedules for elements other than doors and windows, such as beams, columns, slabs, and other assorted objects or designing elements. 

Improvements such as,

• Model accurate representations (2D Plan views, Elevations, and 3D Axonometric Views) that reflect the modelled element rather than a generic 1 x 1 cube,
• Better customisability in the Annotate option of these views, ect., 
• Ability to change measured distances from m, cm or mm, 
• Ability to have different views, (plan, elevation, 3D) at different scales, 
• Ability to re-centre, annotated or customised views (as noted above), to mitigate wasted space around the view,
• Beams, columns and other elements that have mitred or angled edges to be reflected within the schedule,
• Being able to add a photo into the schedule (think a fixtures and finishes schedule, where an image of the bathroom vanity can be placed next to the information about the vanity),

ArchiCAD has implemented some of these customisations in window and door schedules, but hasn't extended the same curtsey to other elements, this development would allow for object schedules to be done in ArchiCAD, and detailed element schedules to go to steel (or other) manufacturers, along with a more accurate element schedules for builders.

Though it is welcome for new users this screen is bloatware for older users and we should be able to disable it completely and/or able to remove unnecessary bloat

It would be great to have this option.

Sometimes it's necessary to fix the size of the Labels without taking the scale in consideration.

Thanks

@GabrielGG  

Scheduler for automatic publishing from Archicad. Both TW and Solo.

Purpose is to run autonomus publishing during night, week-ends etc. Preferably from BIMcloud.

Workflow: Choose Publisher set/sets and set start time of publish. Progress report sent to email when publishing is done or failed.

I would like to enter a wish to make it possible to edit the model in the explore model view in order to prevent the automatic jump back to the regular 3D view when clicking/selecting elements in the explore model view. 

In many workflows, there is a critical need to control the door opening angle individually per view, and per door, to reflect specific functional or regulatory requirements.

When producing evacuation plans for the fire department, we need to show certain doors along the evacuation route in the open position, while other doors marked “close in case of fire” must appear closed. This differentiation is essential for clear communication and compliance with fire safety regulations.

At present, door opening angles can only be controlled manually per object (static, not view-dependent), or globally via the Model View Options (MVO), which applies the same state to all doors in a given view.

This means we cannot have different doors shown open or closed within the same view;

We propose the following enhancements to door behavior in Archicad:

1. Per-view control: Allow the door opening angle to be defined differently per view.

2. Per-instance override: Allow exceptions per door object within a view—e.g., door A open, door B closed—without affecting all doors.

3. Integration options: This control could be added to:

   • The View Settings,

   • The Model View Options,

   • Graphic Override rules

   • As a new parameter linked to Properties or Classification.

    

This is just a very simple one, why can't we group something that is already inside a group?

Difficulties can arise when trying to merge files with different stories. In the following example, two IFC files are to be merged - architectural (left) and mechanical (right). The mechanical IFC file has had stories broken down further, causing a mismatch. 

From this window, there is no way to add in the extra stories on the left. The only workaround currently is to close this, and modify the architectural file beforehand manually to match the structure. It is also challenging to do that as new stories shift the structure around due to Height To Next, with no option to insert a new storey at a specific height while keeping the other stories the same.

This window could have increased flexibility allowing you to insert new stories to match the structure, as well as more flexibility in general when adjusting stories.

My wishlist

When viewing a specific publisher set in the navigator, to add additional new sheets, you must click the sandwich panel and select Show organizer

It frustratingly does not open the the organizer with the specific publisher set I am looking at, to edit.  

When dealing with many similar yet different publisher sets. Its a minor inconvenience, but an inconvenience no less.

Currently, Archicad displays boundary lines between every Zone, even when multiple Zones logically belong to the same area (e.g., split due to varying heights or modeling constraints). Unlike Slabs, which can visually merge when adjacent, Zones cannot be visually merged.

We propose adding a “Visual Merge” option that:

• Allows adjacent Zones to visually merge into a single envelope,
• Lets the user define which attributes must match (e.g., Category, Function, Use Type),
• Lets the user ignore other attributes (e.g., Name or ID), so Zones named “ZoneA.1” and “ZoneA.2” can still merge as one “ZoneA”,
• Aggregates the displayed area and properties accordingly, while keeping the underlying separate Zones intact for data granularity.

Example use case:

A building floor is divided into multiple Zones (ZoneA.1, ZoneA.2) to handle different ceiling heights. Despite being logically one functional unit (ZoneA), it appears with internal separation lines. With “Visual Merge”, the floorplan could show it as one unified Zone for clarity, while internally preserving sub‑Zones for height calculations.

Why this is useful:

• Clean, realistic floorplans without unnecessary internal boundary lines.
• Flexible attribute matching to control what triggers merging.
• Maintains detailed Zone segmentation (e.g., heights) without duplicating data or losing total area reporting.
• Consistency with existing Slab visual merge behavior.

Custom Parameters can be called in Schedule. It would be nice if thi feature was available in Autotext fields, and in the Parameter list in the Property editor.

Now - I have created a parametric bicycle parking rack. This object automatically returns the value of parking spaces, this value can be added in a Schedule, but there´s no way to add this “custom” parameter in a Label textfield, or a Property that will read this value.