Migrating from Chief Architect

[Anonymous]

I am migrating our office from Chief Architect to ArchiCad later this week. Do you have any suggestions or advice for us to minimize the designer's trauma? This was my idea so any issues that crop up will be rightly laid in my lap.

Thanks
Jon

[Anonymous]

Richard,
re:no walkthrough-my mistake, i misstated. also choppy in dolly mode. re: bad hardware-2G RAM, 3.2G cpu, geForce 256k 5200-should be enough. re: 2 windows-yes sometimes i draw like that but it still takes too long to update the other screen. re: too large of a model-ok, 350000 textures is alot, however, it is what it is, and i'd like to smooth it out. re: bones-i'm sure if i stay in this anti-autodesk environment for a few years it'll get gone.

we are giving it a week. maybe i'll recommend Revit or sticking with CA. one thing going for CA, it has an extraordinarily helpful and friendly online community.

s2art,
hey, i spent all day on that render!

[Richard Morrison]

jonthepain wrote:
Richard,

we are giving it a week.

This isn't really an adequate time to evaluate it from the perspective of a user in practice. Can you imagine someone without AutoCAD training saying, "Okay, we're giving AutoCAD a week to prove itself, and then moving on if it's too slow."

[TomWaltz]

Richard wrote:
[This isn't really an adequate time to evaluate it from the perspective of a user in practice. Can you imagine someone without AutoCAD training saying, "Okay, we're giving AutoCAD a week to prove itself, and then moving on if it's too slow."

It may not be enough time to learn everything you need in the program, but it (40 hours, not 1 calendar week) is probably enough to find out if Archicad is capable of doing what you want.

If you looked at Archicad for a week and Revit for a week, you could have a decent idea of their comparative features, and which one you might want to go with.

A few years ago, I spent 8 hours each on almost every CAD software I could find trying to pick a new one.... I dug a little deeper once I had a "top 3", which each got another day.

I was surprised at how much "feature information" could be gathered in that amount of time.

[Anonymous]

OK, I guess I have to justify myself now.

I've been taking an ADT/Viz course at night for the last 9 weeks in order to evaluate that one. I've got the timed demo for Revit that I've been playing with for maybe a month. They are very similar.

I'd do the same for ArchiCAD if it was offered at any of the local univ's. (NC State, UNC Chapel Hill, Duke.) However, I have talked at length with a close friend who is a CAD Tech (currently using Revit) who's last contract was with an ArchiCAD office, who's previous office was AutoCAD, reviewing our wants/needs/options.

Last week the co. flew me to Baltimore to explore a variety of programs at the home show there.

I am hoping that a week-probably 40 hrs out of my typical (unfortunately salaried) 55 will be enough. I'd like more, of course, but Mr. Lead Designer is picking up the tab for my perhaps unproductive perhaps not 40 hours. He has been using CA for the past 7 years and may decide to just stick with that (and dump the CDs in my lap.) This is a big decision for us, however, a week is all that he is willing to spend on it.

We have a small project for a test case and an 8000 sq footer coming up that I'd like to put into ArchiCAD from the get go. If.

My manager has not had any previous ArchiCAD experience, however, he is picking it up very quickly because of his expertise with CA. I think the concepts cross over somewhat-if you know what to draw, you should be able to adapt to the interface. So I am not sure that the "we're giving AutoCAD a week" analogy applies. As someone trained in AutoCAD, I had trouble with CA, but the ADT classes have helped-same concepts, different interface.

I am seriously trying to do due diligence, which is why I have solicited input from you, experienced ArchiCAD users, which I am not. Hopefully I'll build some long term relationships here. I have certainly had that experience in other forums.

And Tom, thank you. I can use some encouragement.

Jon

[Richard Morrison]

TomWaltz wrote:

Richard wrote:
[This isn't really an adequate time to evaluate it from the perspective of a user in practice. Can you imagine someone without AutoCAD training saying, "Okay, we're giving AutoCAD a week to prove itself, and then moving on if it's too slow."

It may not be enough time to learn everything you need in the program, but it (40 hours, not 1 calendar week) is probably enough to find out if Archicad is capable of doing what you want.

Forty hours is probably MORE than enough time to explore whether the package has the features you need and whether you like the interface. But it was my impression that the OP was talking about putting the package INTO PRODUCTION for a week to see how it compares to the current software. For this kind of time investment, a better approach IMO, would be to take 3 or 4 days of training and then work on a tiny project for one or two days. Just mucking around on a project for only a week on such a complex piece of software while you're trying to learn it is going to lead to frustration and an inaccurate perception of the software. And then, because the project isn't even close to finished, he'll have to go back to the old software to redo it and then everybody in the office is unhappy.

To Jon, this software CAN be very fast and efficient, but this will require getting the project set up correctly initially with layers, view sets, lineweights, "favorites", etc. If the project isn't set up well from the beginning, you will end up living with drudgery and a mess to straighten out. If you absolutely can't get training, then I'd recommend at least starting with a template that has already been set up, such as Eric Batte's at www.getstandardized.com .

[Anonymous]

Richard wrote:

TomWaltz wrote:

Richard wrote:
[This isn't really an adequate time to evaluate it from the perspective of a user in practice. Can you imagine someone without AutoCAD training saying, "Okay, we're giving AutoCAD a week to prove itself, and then moving on if it's too slow."

It may not be enough time to learn everything you need in the program, but it (40 hours, not 1 calendar week) is probably enough to find out if Archicad is capable of doing what you want.

Forty hours is probably MORE than enough time to explore whether the package has the features you need and whether you like the interface.

for a second there i thought you were giving someone the benefit of the doubt.

But

ok here it comes

it was my impression that the OP

i have a name (mud, apparently)

was talking about putting the package INTO PRODUCTION

no need to shout

for a week to see how it compares to the current software.

that's what ya get fer thinkin.

For this kind of time investment, a better approach IMO

you certainly have those

, would be to take 3 or 4 days of training

that'd be great, especially since you get 2 free days of training with purchase. in Baltimore. boss says he needs me here in raleigh.

and then work on a tiny project for one or two days.

yes that was exactly the idea (see previous post).

Just mucking around on a project for only a week

you don't have to insult me

on such a complex piece of software while you're trying to learn it is going to lead to frustration and an inaccurate perception of the software. And then, because the project isn't even close to finished, he'll

does that mean me?

have to go back to the old software to redo it and then everybody in the office is unhappy.

not as unhappy as they'd be if you worked here.

To Jon, this software CAN be very fast and efficient, but this will require getting the project set up correctly initially with layers, view sets, lineweights, "favorites", etc.

gee, what're they?

If the project isn't set up well from the beginning, you will end up living with drudgery and a mess to straighten out. If you absolutely can't get training, then I'd recommend at least starting with a template that has already been set up, such as Eric Batte's at www.getstandardized.com .

how about the tutorial that comes with the software?(it's actually kinda fun so far)
.
.
.

aren't there other threads where you could be helpful instead of disparaging would-be customers of ArchiCAD?

[Anonymous]

Tom, Richard.. go vote..

http://archicad-talk.graphisoft.com/viewtopic.php?t=8376

I must have been clairvoyant or something...

Jon,

Richard has other things to do besides help you. I saw nothing insulting in his advice to you. Very suprised at your reply to him. Things are hectic for all of us, but no need to unload on others.

[Anonymous]

Jonthepain (how did you get your name, by the way?)

If you look at Richard's thread he is directing the first paragraph at Tom. You can see at the start of the 2nd paragraph he addresses you directly.

You are asking for comments and these guys are giving both sides of the story. This IS a very helpful community here. There are MANY (oops sorry for shouting) people out there that are only too happy to offer advice, but remember, it's usually just one person's opinion. Someone else may have a different idea. There are also a few people out there who do try to stir things up a bit - these guys aren't them.

ArchiCAD is a great programme, yes, it does have its foibles (but what doesn't), give it a crack and make your own mind up.

Cheers

[Aaron Bourgoin]

Calling Steve Fullalove.

Where are you now?

[Ben Cohen]

Jon

The best advise is to see your local reseller. (if you havent already)