Totally disagree. I am very proficient in both packages,and really enjoy using both. However, if I need to build something fast, or sketch out ideas, I go to Rhino every time. It is so much faster to build in than SW, and lets my ideas flow more.MK19 wrote:I may be biased because I am a long time SolidWorks user but I am now learning to use Rhino because I am going to be teaching it come September to university students.
I can honestly say that I see absolutely no point in learning Rhino whatsoever. The notion that it is easier or faster than SolidWorks is entirely false in my experience thus far. With a good SolidWorks teacher you will pick it up as fast as Rhino and it is infinitely easier to model to scale and account for manufacturing, etc, etc.
Well this was the point I was going to make also. If you are using Rhino you have to know EXACTLY what dimensions your design is going to be before you model it up. Properly modelling in SolidWorks you can change the dimensions of a part with one change and everything updates? Rhino? Make one change and almost start again.SoOnAndSoForth wrote: To fully define a sketch in SW so that it is editable later (which is really the benefit of SW) takes way longer than creating that same shape in Rhino.
This is why I never got round to learning it, as much as I'd like to and as much support and tutorials etc that are out there it is time that blocks it. I don't know how much leeway they will make in industry until more universities adopt it and that is happening in the UK slowly.SoOnAndSoForth wrote:we are always under a time crunch, so we almost never have the extra time it would take to model a design in a package we aren't familiar with. We are chipping away at it slowly, and Autodesk have been amazing in offering support and free onsite training. I think they will definitely be growing their base in the next few years.