2005-10-17 03:32 PM - last edited yesterday by Molinda Prey
2005-10-17 04:30 PM
2005-10-17 05:08 PM
jonthepain wrote:Jon,
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
2005-10-17 08:45 PM
2005-10-17 08:56 PM
jonthepain wrote:You should look at getting the "Project Framework" book from ObjectsOnline.com. It is a pretty solid guide on how to use Archicad in the real world.
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
2005-10-17 08:59 PM
2005-10-17 09:25 PM
jonthepain wrote:Amazon's last Project Framework was for Archicad 6.5 The latest edition covers Archicad 8.1 (even though 9 is the current version).
Will do. I was concerned about which book to choose after reading some very negative reviews about some of them on Amazon.
2005-10-17 11:12 PM
2005-10-18 02:52 AM
jonthepain wrote:No, just use Chief Architect in Render mode with the "dolly" tool active. ArchiCAD can generate MOVIES in a way that Chief can't, but for real-time movement within a model with the client sitting next to me, Chief does as well as ArchiCAD, IMO, maybe better.
Rashid,
Re: Reasons for a big change-
My boss-the lead designer-needs a smooth walkthrough because he often modifies his design with the clients in his office. CA takes several seconds to render each camera view; there is no walkthrough capability.
By the same token, I need software that changes from 2D to 3D windows quickly. It is frustrating for the designer to watch me waiting for a 3D view to render for 20 seconds so that I can check my work.You can have both 2D & 3D windows open concurrently in Chief, just like AC. If you're taking 20 sec. to render, something is wrong-- bad hardware, too large of a model, etc.
My want is a 2D interface that is similar to Autodesk products. CA is frustrating to use in drafting mode for someone with Autodesk experience.Well, AC's 2D drafting tools are superior to CA's, as is the whole area of CD production, but I would try to get AutoCAD out of your bones before using ANY other drafting program. If you try to treat them as similar, you will just get frustrated.
2005-10-18 03:21 AM
2005-10-18 02:58 PM
2005-10-18 04:01 PM
jonthepain 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."
Richard,
we are giving it a week.
2005-10-18 04:16 PM
Richard wrote: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.
[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."
2005-10-18 06:05 PM
2005-10-18 06:43 PM
TomWaltz wrote: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.Richard wrote: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.
[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."
2005-10-18 09:41 PM
Richard wrote:how about the tutorial that comes with the software?(it's actually kinda fun so far)TomWaltz wrote:Richard wrote: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.
[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."
for a second there i thought you were giving someone the benefit of the doubt.
Forty hours is probably MORE than enough time to explore whether the package has the features you need and whether you like the interface.Butok here it comesit was my impression that the OPi have a name (mud, apparently)was talking about putting the package INTO PRODUCTIONno need to shoutfor 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 IMOyou certainly have those, would be to take 3 or 4 days of trainingthat'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 weekyou don't have to insult meon 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'lldoes 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.gee, what're they?
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 .
2005-10-18 09:57 PM
2005-10-18 10:08 PM
2005-10-19 01:06 AM
2005-10-20 02:27 PM
2005-10-21 12:38 AM