Rhino was pretty alien to me for a long time, as I've been using AutoCad for years. I forced myself to get to grips with it a couple of years ago, when we went on a quiet holiday (no TV, phone, internet etc). I took a laptop, loaded with Rhino, plus a printout of the manual, and spent a week un-learning AutoCad and translating things to Rhino.

I think the problem, at least for me, is that Rhino is quite intuitive, provided that you've not got 20+ years of AutoCad experience. I'm pretty sure that it's the Autocad interface that's really the problem, as intuitive it isn't.

Rhino is worth persevering with though, especially if you want to produce nice 3D surfaces. Like all 3D CAD packages it's approach seems a bit odd for those of us with years of working on paper, then CAD systems that emulate paper.

Jeremy