Rhino kind of used to *suck* for making 2D drawings (construction docs), but it's pretty much caught up to AutoCAD in the last few years.Īnd recently it's trying to catch up to Revit. I think of Rhino as AutoCAD with much better 3D capabilities and slightly worse annotation. I also came to Rhino after AutoCAD (using the tricks a few people have mentioned: aliasing Rhino commands to the shortcuts i was used to in Acad). All of the Above.Ĭhances are you'll need some part of all of these tools to get your design from concept-in-your-head to built reality.
You could learn that in a day if you had to. Revit is super super easy to learn, so I wouldn't worry about it at all.
They might require you to learn GC or Catia or SolidWorks or Digital Project, and those take some time to learn. The Adobe Suite is a no-brainer and it's been out for mac for almost a decade. And get V-Ray for Rhino and you'll have almost a complete package for undergrad.
#Autocad for mac 3d modeling free
Also, the plug in known as grasshopper is free and incredibly intuitive to use. You can change the aliases to align with AutoCAD if you wish. It can 'talk', as I said, to almost any program we use. The advantage of Rhino is that it's incredibly intuitive, easily customizable and ridiculously open. That's about it, but it is a hefty advantage to have every consultant on the same page in terms of file reciprocity. I think the advantage of AutoCAD is that everyone in the US uses it. For example, back in the day I would even use it as a bridge from 3dsMax to Maya. Rhino can read and write almost any file type we use. There is complete interoperability between the twain. If you're starting from scratch, there's quite a bit of overlap of concepts, so learning one will probably help you in the other(s). Ultimately, you'll want both (as well as BIM, which is conceptually different) fortunately, you'll have a lot of flexibility to use all of them in one capacity or another, and figure out which works best for what you're doing. Plus, scripting in Rhino seems to be a lot more powerful and easier (VBscript isn't that hard to learn, and if you'd rather not learn it there's Grasshopper) - this can save you tons of time, and is probably the more valuable skill set to have in terms of where things are going. They have their different strengths AutoCAD is stronger in annotation systems and layouts, while Rhino is a lot stronger and more flexible on the modeling end. IIRC, Rhino was created by a former Autodesk distributor, and it actually seems a lot closer in many ways to AutoCAD than other modeling programs I've tried (Max? Even Sketchup?). I think it could work the other way as well, at least for basic things. I learned AutoCAD in R12 (hooray DOS), and was able to easily alias similar Rhino commands/shortcuts to be more AutoCAD-like (in addition to having all the great object-manipulation and analysis tools and whatnot). Autocad and Rhino aren't all that different to learn once you've learned the processes and concepts of one one (at least through using typed commands), the other becomes easier. I don't know if I'd agree with the lack of overlap between the two.
0 kommentar(er)
