I wish that Archicad could import, display and export the USD File format. USD is widely adopted by many industries and offers great flexibility.
Key benefits and features are:
In the context of Archicad, it would allow for a direct import and export of these Files. Importing for using 3D Modells as a Reference, and Exporting for using our Projects directly within VR/AR headsets or Export the Modell for Rendering within another Software.
This wish also tightly integrates MaterialX Support, which is another Wish I suggested.
BIMx is an incredible tool for sharing and exploring 3D models interactively — but it has untapped potential.
Imagine if users could monetize access to BIMx models — turning them into a publishing platform, similar to how apps, books, or online courses are sold today.
Proposal:
Add monetization features to BIMx for models shared through the BIMx cloud or other Graphisoft-hosted services.
Options could include:
Paid access to certain models (one-time purchase, rental, or subscription).
Freemium models, where part of the model is free and full access is paid.
Private client portals with secure, paid entry.
Integrated payment gateways (Stripe, PayPal, etc.) managed by the model author.
BIMx could be more than a viewer — it could become a full publishing and monetization platform.
Unlock a new dimension for creators, architects, and businesses — and boost the value of the Graphisoft ecosystem at the same time.
Archicad needs real NURBS-based modeling — not just faceted approximations.
Bring true curves and smooth surfaces to Meshes, Shells, Curved Walls, Slabs, Roofs, and beyond.
Why?
True Curves: No more fake polygonal curves — get mathematically clean surfaces.
Better Performance: Smooth, editable surfaces without needing thousands of facets.
More Design Freedom: Create organic, fluid forms natively inside Archicad (no Rhino detours).
Future-Proof BIM: Support the next wave of architectural forms and workflows.
Notes:
Of course, this would be a big change, but even starting with a few tools (Meshes, Shells) would be a huge step forward.
Let's bring true surface control to BIM — it's time.
Often, we need to visualize only the terrain with the section line, without projection lines. Or we might want to display only the contours in a floor plan. Sometimes, we just need a few specific ridges. Currently, it's not possible to achieve this directly, and we always have to rely on complicated workarounds. My proposal:
- Add a checkbox to deactivate outline visualization
- Add a context menu option to hide/show individual ridges of a mesh
The A.I. render does not work in teamwork files.
In my opinion, when using Collaborate, there shouldn't be features that don't work just because it's a teamwork setting. However, I understand if there are technical issues, such as the reservation of the A.I. window. On the other hand, this feature is somewhat outside the main project and saves a picture outside the BIMCloud.
I think this feature is a fun experiment. But in the future, I believe more A.I. will be implemented in Archicad. It's important that these features work seamlessly in a teamwork environment.
Setting whether a PDF should be exported flat or rasterized should not require external applications. Currently, PDFs generated by Archicad are still very hard to view or work with in other applications and by different parties.
Similarly, the publishing image formats from the layouts should give the user much more control over the generated quality of the image, not using a slider which has little to no influence on the generated content but by usual means such as setting the DPI.
We urgently need much better control of surface merging.
Everybody knows the issue: You model e.g. two beams, made out of the same BMAT – boom! they merge unintentionally, leading to very strange workarounds of either duplicating all the BMats (not helping often enough in more complex situations) or model pieces a thousand of a millimeter away (BAD practice as it introduces dimensional errors later on).
We need to be able to select for each tool if they should surface join on touch or not!
In the meantime it would be nice if at least the proper funtioning of the special layer intersection group "0" (zero) would be restored.
If a layer has its intersection group set to 0 none of the elements in it should surface join even with each other.
With today's BIM requirements, engineers and architects are asked to each have their own IFC model with only the elements relevant to them.
In this case, for the “architectural” parts, we are asked to export our IFC model without the structure and other technical lots.
However, when we use composite elements with finishing/technical and structural layers, we can't separate them from the “core” layer, in other words, the structural part.
We're therefore obliged to create structural materials dedicated to load-bearing elements (“STR wood”, “STR concrete”, etc.) and replace them with “empty” material each time we export an IFC, then go back and replace our load-bearing materials. This method is by all means functional, but very artisanal and time-consuming.
However, we have noticed that there is a “partial structure display” function that filters the 3D layers of the model, allowing only the structural elements and load-bearing “cores” to be displayed.
We'd be interested in having the opposite function of this setting: filter and hide only the structural parts and “cores” of elements, so as to have only an architectural model visualization that can be exported to IFC (finishes, cladding, doors, windows, ceilings, etc.).
And just to be clear, we're french and this was translated with DeepL.com (free version), so sorry about the possibles english mistakes.
Thank you for reading and even more if Graphisoft realise this wish
Archicad is still approximatinmg Arcs (from Polylines) with short line segments in its PDF output.
The help falsely claims it would not be possible in general, but lo and behold:
That's a PDF. Exported from Allplan 2008 (!).
So it is possible.
Pure, vile, ugliness ensured in AC with polylines:
After investigating I found out that this is ONLY an issue with polylines. GDL objects and circles are not affected.
Also: It is a crime that 3D Arcs are already angular-shaped in Archicad instead of nicely round and smooth.
Looking at you, Profiles and Shells!
When you need the ability to change units not per entire schedule rather than a simple Field, this feature sounds useful.
Currently in AC28 when you need to change the units for your schedules, you need to either change the Calculation or Working units or change the Saved View's Units (not working always) (reference image attached)
Instead of that, should be useful to express or show different units per field on Schemas or Quantity Tables. This should be done easily by adding features to schemas when you click on a field having settings to adjust units directly on tables.
For Example:
In Latin American countries, we work MEP elements in both Metric and Imperial Units. Actually, you should change the calculation units to do this, instead of that should be helpful to change how the units are shown per field. So you can have length in the Metric System and diameters or section sizes working with Imperial Units (fractional inches which is the most annoying thing)
Maybe, by common sense, you would think to save the view in imperial system but that would affect the entire schedule. So this doesn't works. So you dig into the next step.
The next common thing is to change the Calculation Units, considering this would affect the whole project should be considered as a partial solution. This should change the whole units schedule. The work around for this is to make a property to convert from fractional inches to meters for the length, and then to a STRING, and that's it but it's frustrating to have this long workaround for something that could be simply done.
The images and examples are for references only.
Feel free to request for adaptation or commenting to add examples.
In 3d using different 3d styles set by selection. For instance surroundings, terrain, non focus areas in display "model , black and white" (3d style a) and the new buildings in "detailled color" (3d style b) please.
I would like to be able to partially color elements, to be able to hand color elements. Like coloring a drawing with pencils and paint, so with differences in amount of color and touch. Elements like roofs, walls, slabs, beams, etc. could get much better artistic / visual appealing results, also it should work on the fly to be able to see the results quick while modeling instead of stepping out, going to Photoshop, uploading the surface which can not be changed in position, size, etc.. Like a partial gradient on the side of a beam, or a part of a wall which has paint vs the rest no paint, etc.
Oftentimes we have to have two textures for oriented textures (i.e. wood) for beam and column elements because they are not automatically aligned with the longitudinal axis of the element. Of course all work-arrounds with using Align Texture and such are valid, however deep during the project process things get messy having to keep in check whether the texture is meant for the columns or for the beams... It seems that the code to orient the texture for either the column or beam element should be slightly changed to orient the texture's X (U) axis in alignment with the longer axis of the element. Of course there will be exceptions (i.e. really short colums used instead of walls) but in general workflow directional textures should align with the longest dimension of the element.
I would like the functionality of Redshift renderer to be improved. My two main wishes are:
For ease of use and clarity we aim to create graphic override rules that are general and apply broadly. It would be helpful to have a "use original pen" or "use original surface" setting alongside existing options like "use pen 5" or "use surface X."
For instance, a rule to make all cut surfaces solid black is simpler than creating separate rules for walls, slabs, roofs, and other elements. Similarly, highlighting objects, like marking load-bearing walls orange, is easily managed using the override priority system.
However, there are cases where we want to highlight objects by displaying them in their original state rather than applying an additional override. For example, in a facade drawing with several houses, you might want the entire drawing in black and white except for one house shown in its original materials. Creating a rule to make this module (or however it is categorized to separate it) "brick surface" could override other materials like doors or roofs and require updates if the material changes.
An alternative is to set rules like "make everything white except A, B, or C," but this can quickly become overly complex. A cleaner approach would be an option in graphic overrides for "use original" or "disregard override." This you could make a rule saying "make everything white" and above it in priority place a rule saying "except this, make this unaffected by override/use original color".
A similar feature already exists for zone pens, which can use "zone category" as an option. Adding "original color" would extend this functionality.
It would be useful if it for sections/elevations was possible to show the content in 3D with the range as a limiter as it would make it easy to jump between 2D and 3D as needed without having to reorient and setup cutting planes. It would be preferable if this was done by automatically created cutting planes rather than a marquee effect as it would make it easy to expand the range in 3D if needed.
Don't know if it's on the route, but I miss BIMx to be open to another type of files.
Example: Our architecture files come from archicad, but mep files come from revit, and another complex geometry comes from blender/rhino... If there is not an archicad file with all this files together, there is no way to have them all in the BIMx to share with the client...
You can add differents files to Autodesk viewer (really easy). In this case, you only need a link to visualize everywhere, mobile included, without having to download apps. This is important to some clients.
In the roadmap I haven't found anything like this wish, don't know if it's something about it. But I think that BIMx should be the CDE viewer of files hosted in Bimcloud SaaS, like Autodesk solution if Graphisoft like to reach them.
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.
Currenty, when we choose to apply a fill from a Graphic Override, it will be shown at the default orientation of the fill, ie. it will disregard any manually set origin and rotation and scaling of the fill it replaces.
I can of course see a purpose for this behavior also, but probably more often than not, if the fill origin, rotation etc. has been manually edited, there will be good grounds to preserve it also when the fill pattern changed with a Graphic Override.
Could we have an option to select, whether the Graphic Override fill will follow whatever is set for the object's fill orientation settings?
I keep running into issues with Presentation files where 2, 3 or more files get hotlinked into a standalone file, and the attributes all go wonky due to Surface, Building Material and complex profile Index Clashes.
Rather than having an archicad file act as the receiver of all of these individual files...allow Bimx to add more archicad files into, similar to how Rendering Programs like Twinmotion can work with multiple files.
This will help limit some of the attribute chaos that is bound to happening with multiple file projects, since we can't have a Central attribute manager.