AC11 is full with bugs - going back to 10!

[Anonymous]

I write this post to express my deepest disappointment with AC11.

It is the buggiest version I have ever worked with! It has even more bugs than AC8!

Today I finally decided to go back to AC10!

Even the curved Custom profiles and Trace&Reference are not enough to make up for the poor release! I would gladly trade them for stability!

It is offending to the users to release such a raw and unstable product to the market. I suppose this is due to the 1-year-development-period for new versions. If so, this is a bad direction for Graphisoft.

[Rakela Raul]

i dont understand my wifes' reasoning either ....."what a great price, lets buy it"...but we dont need it !!!! ..."who cares just buy it"

[Anonymous]

Like many on this forum, we have not had a smooth transition either.

Of greatest concern to me is that GS has moved to a yearly upgrade cycle but really has not put the framework in place for smooth transitions.
- We still have a very clumsy way of dealing with library parts between releases. Why they all get new names, which do not reliably 'path' between versions - which is a real problem.

This really is getting worse as time passes. The best advice in this forum is to leave a project in the version it was created in. In our experience that is absolutely true. But it means we now have files in versions 8 through 11 inclusive! Heaven help us when we inadvertently open one project in the wrong version - it can cost us DAYS in lost productivity! Even if you do update the file & all the parts it runs so slooowwly as to be unworkable! (most recently that was a 10 to 11 file!)
Then add in the complexity of add-ons....what a nightmare! GS tout one of AC's benefits is the availability of add-ons. These should be built in OR properly supported too, so they have a timely release with the main software.

Interestingly enough it is not a "new feature", but management, which may prove a fundamental part of ArchiCADs future.

[Rob]

The best advice in this forum is to leave a project in the version it was created in.

I disagree with this (well, partly at least). I would keep anything that runs on AC+PM (so from AC9 downwards) as it is and migrate AC10 to AC11.
I have found third-party add-ons as a major disaster during migrating process. I try to refrain from using them as much as I can. Same with the customised markers. Our library has only necessary customised parts like a zone stamp, label and drawing titleblock. So I am not touching anything that can be addressed by built-in elements.

[stefan]

While I did not experience the buggy behaviour, I agree on many parts:

• -- a yearly update for a complex CAD/BIM program is too soon for anything but a one-man office

• -- the reliance on Add-ons is forcing people not to upgrade. This is due to the fact that each new upgrade will make ALL add-ons incompatible. The problem: many add-ons are just not developed anymore, so they disappear with the version they were created for...

• -- I don't like subscription schemes, but every company is doing it

• -- And there should be a reliable approach to migrate libraries between versions. There are ways to go forward (e.g. from 10 to 11) but not the other way around.

I teached ArchiCAD last year (r10) and our classroom is still using r10, but students will be able to register for r11 only. I expect problems!

[Anonymous]

Finally migrated one of my current projects to AC10! What a pleasure to work without bugs and screen-flickering!

It took me half a day for a small project to reassign all the library parts from AC11 to A10, because there is not backward compatability, as Stefan mentioned before. When Doors and Windows change they do not remember their pens, door panels and even he position of the Dimension makers! Everything has to be started from scratch! Which means it is not possible to send your project to a colleague who is working on AC10! You have to make it dwg so he could see it right!

Thomas wrote:
I don't understand the reasoning here. No one is forcing you to upgrade as soon as the new version CD arrives.

I had to upgrade because I teach AC at the university. I even risked to make the above mentioned small project in AC11. Lucky me I did not start with the large one which I am finishing now!

[Markus Denzlinger]

stefan wrote:
I teached ArchiCAD last year (r10) and our classroom is still using r10, but students will be able to register for r11 only. I expect problems!

The registration key also works with ARCHICAD 10.

Markus

[Anonymous]

Markus wrote:

The registration key also works with ARCHICAD 10.

Thank you, Markus! Just on time as I was planning to make a post asking this question.

Due to some misunderstanding with the IT support at the university we had AC10 installed there. So I teach AC10 to students and I was telling them the previous lecture not to install AC11.

[Anonymous]

I recently have been thinking of recommending my office commit to a particular version, and not upgrade ANYTHING for 8 years.

GS gets $500 US per seat per year, and after 8 years, we could simply buy whatever new version or better software is out there...

Why?

Because at some point, (maybe release 12) it will do enough for us to produce our work efficiently, and we will fine-tune and hone that given tool and equipment. Not to mention that we then need to buy new computers every 3 years to keep up with the increase CPU requirements. The old ones end up in landfills, which turns my stomach.

The last 3 years, each spring has meant lost work while we change systems, and migrate versions. While there is always some benefit, there is also an associated cost.

Software programs are like musical instruments, the more you practice, the better you get. But imagine what it would be like if someone changed the fingering on the clarinet every year...

just my two cents.

[Rakela Raul]

Software programs are like musical instruments, the more you practice, the better you get. But imagine what it would be like if someone changed the fingering on the clarinet every year...

excelent !!

[Laszlo Nagy]

Nathan wrote:
I recently have been thinking of recommending my office commit to a particular version, and not upgrade ANYTHING for 8 years.

GS gets $500 US per seat per year, and after 8 years, we could simply buy whatever new version or better software is out there...

8 years seems like too much for me.
Maybe 2 or 3 years, but 8???