macOS 26 Tahoe - ArchiCAD 27 Incompatibilities / No plans to fix?

[Jeff Griffin]

So, let me get this straight.  Can someone please tell me why ArchiCAD 27 will not receive any hotfixes to make it compatible with macOS Tahoe?

According to Graphisoft's own support policy, hotfixes are issued for the two most current versions of ArchiCAD.  As of today (Monday, September 15th, 2025), Graphisoft has no plans to release compatibility updates for the previous version of ArchiCAD, which is currently ArchiCAD 27?  ArchiCAD 28 is the most current version. Until ArchiCAD 29 is actually released to the public (not a Tech Preview), it cannot be considered the latest version of ArchiCAD. 

The first developer beta for macOS Tahoe was released on June 9, 2025 (98 days ago as of this post).  Are you telling me that Graphisoft was once again BLINDSIDED by the annual update to macOS, even though they had nearly 100 days to prepare for it? Please tell me that this isn't the case.  

[Marc_Voumard]

Hi Jeff,

You can find more information in this article about macOS 26 : macOS 26 Tahoe - Graphisoft Community

[Jeff Griffin]

Hi Marc,

Thanks for directing me to the very page where I read that Graphisoft only supports the current version of ArchiCAD, version 28. Not the two most current versions of ArchiCAD (version 27 & 28).  At that page, Graphisoft described three known issues and then stated that one of the issues has no workaround. Indicating that the "solution" was that "the issue was fixed in ArchiCAD 28" falls woefully short of being an actual solution to the issues encountered in version 27, hence my inquiry.

Maybe you can answer my questions:

1. Can you please tell me why ArchiCAD 27 will not receive any hotfixes to make it compatible with macOS Tahoe?

2. Are you telling me that Graphisoft was once again BLINDSIDED by the annual update to macOS, even though they had nearly 100 days to prepare for it?

---

[Marc_Voumard · Accepted solution]

Hi Jeff,

Regarding ArchiCAD 27 on macOS Tahoe, you are right that there may be some minor visual issues. These do not affect core functionality and remain manageable in daily work. In line with our long-standing policy – which is also industry standard – we focus compatibility updates on the two most recent versions of Archicad, which this year means Archicad 28 and the upcoming Archicad 29.

On your second point, we do test Archicad extensively with the macOS developer releases from day one. However, Apple often introduces last-minute changes during the beta phase, and these can occasionally result in unexpected issues appearing in the final release. While we work hard to anticipate and minimize such situations, it is not always possible to address them ahead of time.

I completely understand your concerns, and I assure you that our teams are committed to ensuring the best possible experience on the latest macOS systems. Our recommendation at this stage is to remain on macOS 15 Sequoia, which continues to be fully supported by Apple and ensures the most stable experience with Archicad 27.

[Jeff Griffin]

Thanks Marc.

[laembert]

We're not looking for information, we're paying for updates.

[Davidbarnard]

This is frankly not good enough. And I suspect is not complying with Australian Consumer Law. The product should be maintained for a reasonable period reflecting the write down period for the product. This would typically be about 3 years. It seems ridiculous to be required to update a licence every year when the improvements in most cases are so minor or certainly not relevant to me. This attitude from Graphisoft and the excessive subscription fees is sadly leading me to consider other options. I have been using ArchiCAD since version 6!!!!.

I will be raising this issue with the Australian Distributor and if need be, the relevant consumer authorities.

[Tex]

Hi, I agree completely with my colleagues here. What Graphisoft is forgetting with their 2 version policy is that larger offices need to complete their projects in the version it was started in or, at least be able to migrate easely. This policy needs in particular to be changed this year since the introduction of lib packs in 28 makes it extra difficult to migrate from 27 to 28. We have projects that span over multiple years and will not be able to use lib packs as it would mean remodeling most of the project which is not an option. Graphisoft needs to solve this migration problem for projects in 27 and earlier. If that was fixed I could agree on a 2 version policy but not as it stands today.

[Barry Kelly]

---

@Tex wrote:

We have projects that span over multiple years and will not be able to use lib packs as it would mean remodeling most of the project which is not an option. Graphisoft needs to solve this migration problem for projects in 27 and earlier.

---

You can open your old projects up in version 28 or 29, and not use the new library packs.

Just load the old libraries as you did in the old versions.

They will work perfectly fine.

Barry.