Proper classification and control of a BIM project is very time-consuming. Assigning values through drop-down menus often requires too many clicks, and using Graphic Overrides to control and visualise each property in the drawing can be extremely inefficient.

A dedicated dockable palette for classifications and properties would be a much more practical and efficient solution. In addition, having the option to automatically visualise the values of a selected property directly in the drawing would be a huge improvement to daily workflows (I am aware that an add-on exists for this, but native functionality would be far more robust and accessible).

To handle IFC hotlinks effectively in Teamwork today, IFC libraries must first be exported locally, then manually uploaded to BIMcloud, and finally re-linked into the project.
The option being Embedding them and slowing down the file.
This feels unnecessarily fragmented for a cloud-based workflow.

Why can’t IFC libraries be linked directly through BIMcloud?

And why does every new IFC import generate a completely new library instead of updating the existing one?

Rather than saving the libraries to either Embedded or External location, there should be a third option:

Save to BIMcloud (and link automatically).

Archicad should then recognize and reference the library immediately, without the export-store-upload-relink cycle.

A smoother BIMcloud-based IFC workflow would reduce friction, eliminate redundant file handling, and streamline collaboration.

Before switching to Archicad Studio I was able to use the international English version of Archicad here in Brazil. Apparently the new cloud license only allows me to use the Brazilian Portuguese version. For me, this is a major setback. As an old customer (40+ years of experiencie with CAD, 3D and BIM software), I got used to  English as my working laguage on the computer, as there were no software translations available in the past. I find it particularly annoying to switch languages ​​when using multiple programs at the same time. Not every software has a Portuguese version. My work consists of converting CAD (AutoCAD) and BIM (Archicad, Revit) models created by my clients to FBX or OBJ for further use in advanced 3D visualization and simulation software. I use the converted geometry in 3ds Max and Unreal Engine to create immersive simulations of the proposed buildings. Graphisoft should urgently reconsider this policy, as other companies such as Adobe, Autodesk, McNeel, Trimble, etc. allow you to use their software in any language, regardless of the country where you work. 

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.

My request is for the implementation of IfcAsset and IfcInventory as mappable subtypes within the IfcGroup structure in ARCHICAD's IFC Project Manager. This inclusion would significantly improve the software's capacity to handle complex data structures related to asset management and facility management within the framework of openBIM.

• Currently, ARCHICAD's IFC management tools do not allow for the direct mapping of elements to IfcAsset or IfcInventory entities.
• This limitation restricts the ability to leverage these entities' full potential for data enrichment and integration with external systems.

Understanding IFC Grouping Entities

IfcGroup and Its Hierarchy

IfcGroup acts as a generalisation for grouping objects based on non-geometrical or non-topological aspects. IfcAsset and IfcInventory are subtypes of IfcGroup.

Key Concepts

• An example of an IfcGroup is a system. An IfcDistributionSystem is an example of a group representing a system.

• IfcAsset is a group of elements that represents a single entity of financial value. Maintenance operations are usually undertaken at the asset level.

• IfcInventory is a list of items within an enterprise. The IfcInventoryTypeEnum identifies the type of inventory, including:

  • Space
  • Asset
  • Furniture

Related Entities

IfcSystem is another subtype of IfcGroup, grouping elements based on their roles. For example:

• IfcBuildingSystem
• IfcDistributionSystem

These are subtypes of IfcSystem that group building and distribution components, respectively.

Special Case: IfcZone

IfcZone is not a subtype of IfcGroup or IfcSystem but a spatial element that can be referenced by an IfcGroup using the IfcRelReferencedInSpatialStructure relationship.

Example: A mechanical distribution system (an IfcGroup) can refer to a building (which may contain IfcZone elements).

Benefits of the Feature Request

Implementing this feature request would offer several advantages to ARCHICAD users, particularly those involved in asset and facility management workflows.

• Improved Data Organisation: The IfcAsset entity enables the grouping of building elements into manageable units based on their function or financial value. This logical grouping facilitates better organisation and tracking of assets throughout their lifecycle.
• Enhanced Data Enrichment: IfcAsset allows association with various objectified relationships such as IfcAssignToActor, IfcAssignToControl, IfcAssignToProcess, and IfcAssignToResources. This functionality enables the linking of assets with actors, controls, processes, and resources, providing a more comprehensive understanding of asset performance and management.
• Streamlined Data Exchange: By mapping elements to IfcAsset and IfcInventory, ARCHICAD would align with the IFC 4.3 schema's capabilities for asset management. This alignment ensures smoother data exchange between ARCHICAD and other software platforms that support this schema, including asset management systems.
• Support for Existing Buildings: The IfcSharedFacilitiesElements schema can be utilised to manage both geometric and semantic data of existing and new IFC objects, aiding in the integration of real-time data. This is crucial for asset management in existing buildings, which often lack comprehensive as-built BIM data.

Integration with IFC Project Manager and Assignments

Integrating IfcAsset and IfcInventory mapping within the IFC Project Manager and Assignments function would primarily focus on:

1. Adding IfcAsset and IfcInventory as Selectable Subtypes: The IFC Project Manager interface should be updated to include IfcAsset and IfcInventory as options when assigning IFC types to elements or groups.
2. Mapping Elements to Assets and Inventories: Users should be able to easily select elements or groups within the ARCHICAD model and assign them to specific IfcAsset or IfcInventory entities created within the IFC Project Manager.

Note: Since ARCHICAD already supports the implementation of official IFC Property Sets once the IFC classes are properly implemented, no additional property definition interface would be required. The existing Property Sets functionality would automatically handle the standard IFC properties for these entities.

Implementing these changes would significantly enhance ARCHICAD's capabilities for managing and exchanging asset information, promoting interoperability and streamlining asset management workflows while leveraging the software's existing robust Property Sets implementation.

The publisher is a pretty great thing, but it falls down for three reasons.

1. It doesnt address modern file transfer. Most practices use some form of file sharing like dropbox, one drive, etc. to send out their files. Once published we want to right click on a single folder and generate a single link and email it out. In the publisher you cant place multiple 'shortcut' folders into a dumb folder with an autodate. What the heck? I want a live folder of PDFs and a live folder of DWGs and a couple of my IFC views in a single folder so i can click publish once, and all of that goes to a single folder with an autotext name (<SHORTDATE> <PROJECTNAME> COORDINATION SET) for example. I dont want to write the damn date out every time i have to publish. and ive spend days trying every other permutation of that darn thing, and nothing allows me to make it a one-click publish exercise. 

2. The publish button and [selected items, entire set, transmittal list] should be merged into one button in both Navigator and Organiser. The UI here is infuriatingly clumsy and because the tri list is hidden in navigator, you have to click it every damn time to check what it's set to. This brings undue admin to the user. The reason for not having the organiser open full time is that it slows down archicad. Yes, thats still an issue, even on my 12th gen intel with 64GB ram.

3. the 'add shortcut' button doesnt mean anything to anyone. call it what it is. 'add live layouts', or 'add live subsets'..... anything that directly tells the user what it is and what it does, and doesnt allow users to unknowingly use only dumb folders for YEARS. There doesnt need to be an entire team of software engineers dedicated to useless help prompts,. please make the options self explanatory and not convoluted.

It appears this feature got dropped recently in the Archicad 27 update...

When doing a find and select, you can eyedrop to pick up the attributes or properties of any element and that changes all of the added criteria to match. BUT! Please add back in the feature that any NEW criteria you add will also match the previously eye-dropped element's properties. This would be so great. Anyone else?

• It would be great if there would be a possibility to have a beam and column intersect cleanly in 3d without having to manually adjust the end angles of the beam and of the column so they match.

• It would be usefull to have one more possibility of moving freely (a combination of changing the length and changing the angle at the same time) constrained to the plane of the beam

Hi all,

This wish is for more granularity regarding nested hotlinks. For many years we have had the option to "Skip Nested Modules" which for simple buildings worked ok for exluding nested hotlinks that you had used for context, but it fell apart if you started using Hotlinks to for modular layouting. There was no way to skip the neighbouring building but keep the bathrooms. For a long time you would just hide the hosting Hotlink Master Layer, but with the advent of Design Options, the nested hotlinks can be placed on a specific Option to later be completely excluded. Another area where we resort to hybridising Design Options to resolve issues with the functionality of other features...

Sticking to the current UI, a solution could be to identify .pln verse .mod Hotlinks and only exclude .pln when skipping nested. This would consolidate the identity of .mod files, which until we can edit in place, feel like they have very limited advantages over a clean, culled back .pln file. It's great when you Edit Module in seperate ArchiCAD and the attributes are not identical, and attribute folders may as well not exist...

An alternative, which I feel is more streamlined, is to invert the functionalities depth. Instead of Skipping Nested Modules, the toggle would then skip the placed Hotlink when nested. In a model heirachy of A=>B=>C, instead of toggling the setting when placing B into A, to exclude C, you would instead toggle it when placing C into B. Put the control in the file that hosts the nested module. I have yet to encounter a situation where I have only sometimes needed to exclude a nested module...

Another option would be to expand the current UI by adding a dialogue to pick which nested modules are excluded, much like the Design Options dialogue.

A non-option is to just put everything in a single file with only one layer of hotlinks, because we all know how well AC goes with high polygons, and not everyone needs a super computer...

Ling.

I really wish we had a Rhino-style Gumball-cursor or a Microstation-like Accudraw. 

Attributes, such as Composites, Surfaces, Complex Profiles should allow for the creation of Custom Data Fields.

For example, wall types are typically created as Composites.

There are performance data that belong to the Wall Type and not to the components of the wall type.
Such as:

Wall Type Code

-All walls that use the same composite would be coded / documented as the same wall type, therefore the wall type can't / should not be allocated at the instance level, but it should be assigned at the composite (attribute) level.

Fire Performance

- It is defined by the wall type, not the individual layers of the wall buildup.
In other words, you can't get the Fire performance of a wall by adding up the Fire Performance values of it's components.

Acoustic Performance
- Same as Fire Performance, Acoustic performance belongs to the Composite, not to the elements of the composite

etc

Currently the only data field available for composites is their name.

Using a very cumbersome workaround, we can name the composites in a particular way, putting all the relevant info into the name field, then we can split the info using expressions, however this is a very clunky and error prone workaround.

A wall type legend, similar to below is commonly used.

These wall types then are annotated in plan view using labels.

Attribute level properties should be edited at each attribute's editing window.

These attributes belong to that specific set of attribute only, not used anywhere else.

For example:

Composits should have their own set of properties / custom data fields that should be set up and edited in the Composite Settings dialogue box.

A thread working towards similar goal is IDs for Surfaces , however that wish only asks for ID's for surfaces.
I am certain that something like what I wish for is a more global solution and would please many-many users.

Hello Team

PS: based on feedback from Laszlo Nagy in the comments below, he confirmed that the Project Info fields are already accessible from Publisher.

So the outcome of my wish should just change to: "see everything as in all data access cases like this. If the data is too long, make the groups collapsible + make the list scrollable & searchable".

================

I want to propose / request to improve the ability to have access to Project Info (and all other data) fields from Publisher.

I have been looking for the most efficient way to build my template for ISO 19650 compliant naming of Auto Text on my Masters & output file names via the Publisher. The ISO 19650 file naming have some fields that are consistent for the practice (ie. Project Number, Originator) and others that are variable by Layout or Sub-Set.

This image shows my current setup where I "Rename" the Layouts in the Publisher with most of the ISO fields as custom Layout Info fields, apart from native Layout, Publisher, Changes & Revision fields.

Although I have come to a point where I have this working well, the limitation in Archicad for Publisher not able to access Project Info fields makes the entry & management of the ISO 19650 outputs (auto text on Masters & published file names) not ideal.

If it was possible to have access to Project Info fields from Publisher renaming function, then we can pull Project Number, Originator directly from one single entry in Project Info instead of having to enter it into Layout specific fields for every Layout in the project as well.

It makes sense (to me at least) that entering the consistent fields in one place & call it up everywhere needed (1) would save time and (2) remove the possibility for user errors (ie. missing the entry on some Layouts and (3) constantly going back to enter the same info on new Layouts created as we work.

The new design option system has great potential but some aspects are lacking. We use hotlinks extensively, often together with layer combinations to say export interior walls to one module, exterior and stairs to another, furniture variations to a third and then combining them in a main model while still being able to work on the entire floor together in the module file.

Now with the design options this gives even greater flexibility, but when exporting a mod there are only two options for what to include: All elements or Visible elements only. This option treats objects on hidden layers the same as objects in another design option, which is the wrong approach in my opinion. The layer combination should be able to be used to filter broad strokes, and then the design option for variations. I would like to be able to export a mod-file that has only load-bearing walls but say three different options for their layout. The simplest solution as it is now is to export everything and then filter again in the main file but this leads to an unnecessary amount of objects, for many instances of the module maybe I only need the load bearing walls, not every piece of furniture, measurement, label etc.

It possible to copy/past (or drag and drop) a picture from windows folder (or internet ...) but then that picture cannot be cropped as when using the "drawing tool". 
I WISH  a "CROPPING" option. Or the possibility to change that picture into a drawing so I get the same option than with drawing tool. 
The "drawing tool" work fine but it's long and annoying to search in deep folder.  

Problem: Cannot use the stretch tool in the 3D window. 

Pretty self-explanatory, but I simply want to use a marquee or lasso to select a portion of elements and stretch them similar to how it's done in 2D, but in 3D. This would speed a lot of editing up in 3d. 

Hi,

I would love to have the possibility to work in more than one tab at a time. One simple example could be to work in 2d plan and at the same time you have a 3d view that constantly updates, and vice versa. Today you must change something in one tab, and the change to another tab. This makes the user experience not very seamless.

One good example is how Rhinoceros 3d has solved this with 4 viewports, where you more or less are working in all these at once, and you have control over 4 views at the same time. If archicad could do 2 or more tabs/viewports at once would give you more control over your geometry.

Modelling complex stairs and railing and many other situations would really benefit from this kind of interface flexibility.

This is a relatively simple one. I am constantly selecting elevation and section markers by mistake when working in the floor plan, because they all have hotlines at the cut line, and also at the near and far clip lines. My wish would be for these hotlines to be optional. I tried doing it in a custom elevation marker object but the GDL only affects the markers, not the lines.

it would be great to expand the work environment settings for the pet pallet; maybe a color scheme or appearance setting, maybe a size setting independent of screen resolution.
the follow cursor or go to predefined location has always been an option, but if we could change it to bright red buttons or something, so it stands out, we wouldn't need to play hide and seek with it quite so often.

File browser dialogues should use the windows default dialogue, allowing searching, copying and pasting of file paths, access to pinned folder etc. having to navigate our vast project library each time is annoying and time consuming. 

 Current arrangement:

Proposed: