Can we please have the option to lock the default renovation filter.

The common problem is when selecting New status as the default, it does not remain the default, at some point it goes back to existing status, however drawing work continues without realising the default his now existing.

Later in the day when this error is spotted, time is wasted going back over work and moving things onto new status.

Not sure why this happens, but a simple lock would be great.

Hi Graphisoft,

As a ling time GDL programmer I always wanted a decent code editor just that looks like and feels like Microsoft's Visual Studio Code, and although you have delivered it in AC27, I feel that it was intentionally delivered broken!

1. It's intrusive in the way we like to work with coding
2. Many options are hidden
3. There is no way that we can change the preferences of the default installed settings in GDL Editor,
4. And if I´m wrong, I could find the documentation that will tell me were to look to change those settings.

The textures in archicad are applied based on a global/world reference point.

One example where this option would come in very handy would be:

When working with curtain walls independent panels can be created by either using distinct classes in combination with independent textures or building materials or by creating custom panel objects. Neither of these options however offer the possibility to link an "object" reference point for the applied textures.

We do have the ability to adjust the origin of textures, but apparently not when working on subelements, and even if this option would be available it would be useless in the above mentioned situation.

Having a surface, building material and where possible geometry based tick box overwriting the default reference point for texture would be great.

It should be possible to view attribute structures in a properly expanded one-pane folder view (as it is for the navigator).

Currently we have to choose between seeing a simple list of all attributes in the list view or jump between two panes in the folder view due to its flawed interface. It is really frustrating that the attribute interface was works on a few version ago and yet ended up is such a poor state.

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".

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

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.

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 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.

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 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?

Please provide a simple button to the toolbar which updates all modified hotlinked modules.

Now we always have to open Hotlink Module Manager first, wait for the modules to be checked, select modified modules and click update:

A quick acces button that automates this would save a lot of time.

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. 

As described in the image below, this can helmpfull to schedule exactly what we want, without extra filtering criteria.

a check box in front of each class item will fix it !  

When developing a project, a user very often uses the same project map viewpoints many times as different views, using different scales, pen sets, layer sets, model view options, graphic overrides, renovation statuses... However, when saving a view in view map, ID cannot be automatically assigned as a different value from ID in project map. Meanwhile, in layout map, you can freely assign hierarchical automatic IDs to any layout within any subset, or you can define it manually.

When placing drawings, it is easy to place the wrong view from view map because it is often assigned the same name regardless of the subset it is within. Thus, the drawing list is somewhat useless unless you take time and dilligence to edit all IDs manually.

My workflow is to have a subset in view map for every phase of the project, and within it, subsets for types of drawings: floor plans, sections, elevations, drawings (of all kinds) used for analysis... Ideally, I would automatically assign an ID as <PHASE>.<TYPE>.<PROJECT_MAP_ID> or whatever would be intuitive in a certain project. Unfortunately, while subsets in layout map have plenty of options to do this, you can do basically nothing with subsets (folders) in view map and project map.

It would be fabulous to have an annotation tool on BIMx, specially for mobile devices. I can imagine site inspections with the BIMx model with all the projects plans loaded and be able to make annotations that can be shared with the office or client