This information is from the latest quarterly report on : 15,000 seats of Revit in a 3 month span is impressive. Revit sales are the driving force in Autodesk's recent successes. The worst place to find yourself is when the only workaround is to print out, white out and paste up (been there done that too). They are future new features and without them we often would not be able to get the work out on time. They certainly didn't go to Revit just because it's owned by Autodesk (in many cases that is more of a negative factor). I know from experience that my clients studied the two programs long and hard before choosing ArchiCAD. I do know that Autodesk's purchase and promotion of Revit has driven a lot of ArchiCAD sales, which suggests that quite a few firms - once convinced of the need to move to BIM - are choosing Graphisoft's product over Autodesk's. My lack of recent experience with Revit prevents me from having a strong opinion about which is better and by how much. I don't know how Revit stands up on drafting and documentation but have heard that it is good.
Revit vs archicad how to#
Many people have complained over the years about ArchiCAD's lack of drafting tools but this can only come of not knowing how to use the program. ArchiCAD also has very strong drafting and documentation tools, and the integration of the model and documentation is also very good (and improving substantially with each release of the program). Most I have talked to seem to agree that ArchiCAD is much better in the initial design stages despite that you have to use an add-on (MaxonForm) to do freeform modeling. In Summary: Each program has it's advantages. I believe recent versions are addressing this by allowing you to limit the extent of these relationships.
I have heard of some who had some very unpleasant experiences with automatic relationships doing things that they didn't expect and didn't know about until after the drawings were issued. The other issue is managing all these relationships. Early versions had significant performance problems. While great in principle this has created problems. stretch a dimension string and the associated element changes with it). From the beginning it has worked with relationships between the architectural elements (ie. It is also based on a substantially different premise than ArchiCAD. (It would be interesting to know the difference in hours billed on each program - I imagine that ArchiCAD must be quite a few (tens of?) thousand years ahead by this metric.) But from what I understand Revit are working very hard to catch up. Revit is a newer product and so lacks the time in the field. (I haven't looked at the recent versions of Revit so I don't know how it compares in this regard.)
Revit vs archicad mac#
It was originally developed for the Mac (like Word, Excel, Quark, PageMaker, Photoshop, etc.) and so it still has a legacy of quality interface design that is often lacking in Windows only products though increasing complexity seems to have degraded this somewhat over the years. Using the marquee tool to inspect and work on an arbitrary isolated part of the model is one example of this. It was originally developed on much slower computers and so has many methods for working efficiently on projects that exceed the capacities of the machines. I am not very familiar with more recent versions of Revit so I can only give you some vague generalities.ĪrchiCAD has been around a lot longer and so has had time to develop tools, methods and workarounds* for just about any circumstance. Other than that, is there anything else? i guess, same as kristine, i can feel it in my gut that archicad is a lot better than rev-it but i just need to know specifically why.
but as of now th only thing i noticed is archicad is a lot better when it comes to compatability. As sir matthew sugested, i did read some of the topics concerning the rev-it vs archicad.
0 kommentar(er)
