Downside of Renaming Elements with every new version of ArchiCAD

[KCSFCA]

As someone who has been using & updating ArchiCAD for 23 years - THE major & extremely time consuming issues for offices with each upgrade is:

-- We lose our custom tool palettes & along with that - their orientation on the screen.  They have to be very laboriously redesigned every time

-- Anything that can be modeled in 3D gets renamed '27' when it used to be '26' (and poor me... '7').  Because of that - in your existing projects - you lose every piece of furniture, every window, every door, every water heater... & have to go through scores of new settings to get them back.  I'm 3 days into this already.  I have to fix the elements on at least 10 open projects.  When any past client returns for a new project - I'll have to do it in their files as well.

These are both issues I've been complaining about to Graphisoft for DECADES.  I'm so old I'm in the 2002 Marten / Peters book - 'ArchiCAD'.

When you add features - why can't you just keep the name of the piece & add the features so it updates without erasing years of someone else's work?

I'm replacing furniture items that are the same exact piece of furniture they have been for decades. The only change is the name - to '27'

Operating system used: Mac Intel-based

[Barry Kelly]

I hate to say it but you have been doing it all the hard way.

Custom tool palettes are Work Environment settings that you can export/and import to each new version.

Every new version, I import my old Work Environment (because it is sett up the way I like it), and then I add any new commands to it.

I open say 26 & 27 side by side and compare the WE in both to spot any changes.

Conveniently there is also a list on new commands when it comes to toolbars and menus.

As for the library objects, all you need to do is load the migration libraries as well as the library for the new version.

Most (not all) library objects will be converted (migrated) for you.

Some are changed so much that they will not convert automatically.

You can keep using them as they are (the older version) or you can manually swap to the newer version as you have been doing.

Warning, library migration changes completely in version 28 (there is no migration from 27 to 28), but we will worry about that when 28 is released.

If you are part of the Technology Preview program, you should already be aware of it).

Barry.

[KCSFCA]

Actually - my toolbar did not import at all.  And my work environment profile - also did not import.

Maybe this is b/c I was switching from ArchiCAD 22 to 27.

I update as infrequently as possible b/c it is usually catastrophic to do so.
i still use some library parts & lots of textures I'd been using since ArchiCAD 7.  I'd also still been using some library parts from 9.

Those did not migrate.

Every piece of furniture that disappeared is still used in ArchiCAD 27 - but now it's called '27' & so it disappeared. 

A lot of the chairs rejustified to alternate centers - so after I replace them / reset all their settings - I have to relocate them as well.  Just to have the same old chair.

None of my windows & doors came over.  That's a pain b/c there are so many types.  Even with elements I can batch select - I still have to go in & redo all the casing, frame & fill pen settings b/c many of these settings do not let me change by batch.

It's disheartening to hear that 28 will eliminate migration after doing all of this.  I've only been able to fix one project & one file I always keep open b/c it has my previously used furniture layouts / elevation drawings, etc. 

I haven't had time to redo my other active projects yet. 

And I have over 150 closed jobs that will need to be done later any time I want to use them as a reference. 

This is A LOT.

[Patrick M]

here is what I do:
-rebuild template favorites with the 'new library parts' to avoid the migration library in the template

-migrated projects have the migration libraries with them, so there are little or no missing parts to re-assign

literally just need to add the migration libraries to your project, and there is almost no need to do what you are describing.

that said, it seems like once the .libpack stuff is sorted out (still waiting on that finalization, and not holding my breath), we will no longer have this issue.

[Patrick M]

the work environment is another issue. if you have custom tool bars, they can be brought in, but generally I spend about 1-2 days (not 16 hours, just a little bit here and there) rebuilding my w/e with every release.
the only thing I ever recommend bringing forward are custom kbs (keyboard shortcuts); since any migrated palette schemes, etc. will likely result in missing features.

since you've been using AC for a couple decades, I have to assume you are versed in your custom w/e, and shouldn't take long to integrate it into the new build. IME, a few hours of rebuilding my w/e is well worth the effort for what I get out of it over the course of the year I'll be using it. 

Additionally, I never look at my w/e (or template) as a finished product. It's always a work in progress. 

Over the year, I'll have w/e 27.1, 27.2, 27.3... 28 is about to come out and my w/e is on version 27.18, and may even be adjusted before I start finalizing my 28 w/e

[Patrick M]

Closed projects should be archived, so the .pla contains all relevant placed elements. You only need to sort out the library issues if/when you need to re-open them as an active project. It's happened to me, and that can be time consuming; but at that point, they are likely a remodel or minor project, in which case you are either starting over, or good to work with whatever is in the .pla library.

I definitely don't advise maintaining libraries and build/version numbers on non-active projects.

[KCSFCA]

Right - the 7 & 9 .pla files were 'incompatible' with 27.

Even with remodels - I have a lot of 4 story existing & proposed to redo.

At least now that I have fixed the file I created to save various furniture layouts - I only have to delete & paste in on the remaining projects for that.

Also in this file - I have a little template I created that has strips of wall with all the windows & doors I use with their various casing details & I bring that into every project to start.  I still will have to suck up & inject the parameters into windows & doors on every story / existing & proposed for other projects.

Is template favorites just the star in the top bar of the element menu for objects / windows / doors, etc.?
I've never used that b/c I always just keep my 'parts' file open to the side & grab things from there.

[Patrick M]

yeah, going back 20 years in any software, I would think I would have to redo a lot of work. Honestly, a 20 year old build, I'd be happy if I just got a shell and core and maybe some basic openings to work with. Hopefully you have pdf and dwg's to coordinate the rebuild from.

Yes, the favorites are the star icon in element settings; also available in the tool bar pop out, and in the window > pallets > favorites. The favorites are a must have for any template. Build them out with the "best starting options" for each tool. Don't overload them, just have a couple basic interior and exterior walls, most commonly used door and window configurations, and basic plumbing, casework, appliances, etc. objects. 

Also very useful for basic annotation (grids, marker types -for markers not pre-placed in your template-, dimensions, labels, etc. 

A graphic favorite is not a bad way to go for detailing, IMO; or any kind of repeat template style layout (I use graphic favorites for I/E clean up, for example). But the saved favorites are a life saver