- Joined
- Jun 24, 2010
- Messages
- 2,444
- Reaction score
- 967
I'm mostly self taught too. 2D Autocad v14 through evening college classes, then what was it, DesignCad? (AC 2d lookalike), then Rhino v4 3D. Then SW around 2010/11. I got a freebie course of the basics at the time, but most of what I've learned has been doing, instructional texts & some good online video courses made available through Lynda.com, now LinkedIn learning (free subscription through my local library). YouTube is a dangerous place, some good stuff & some.... less than good.
Rhino was a good example of what we are talking about. Like AC it provides no visual feedback that a sketch was 'correct'. Say 2 lines that are supposed to meet don't actually meet. Separated by a screen pixel. Because models have computational tolerance, it may still make a (albeit non-air tight) 3D model of sorts that also looks good from across the room. Things are going marvy as the features get extruded & manipulated. Then you notice this edge fillets & that one doesn't. Why? Then another click & the entire model blows up. Hmmmm... 2 issues here. 1) the imbedded sketch problem was never properly identified to the designer so its hidden. Maybe there are many more similar issues, identification is painful, no diagnostic debugger. 2) Rhino is not parametric like SW, so you cant even back up the tree to see where things have gone awry. (Rhino is 1/5 the price which explain some of the issue).
Rhino was a good example of what we are talking about. Like AC it provides no visual feedback that a sketch was 'correct'. Say 2 lines that are supposed to meet don't actually meet. Separated by a screen pixel. Because models have computational tolerance, it may still make a (albeit non-air tight) 3D model of sorts that also looks good from across the room. Things are going marvy as the features get extruded & manipulated. Then you notice this edge fillets & that one doesn't. Why? Then another click & the entire model blows up. Hmmmm... 2 issues here. 1) the imbedded sketch problem was never properly identified to the designer so its hidden. Maybe there are many more similar issues, identification is painful, no diagnostic debugger. 2) Rhino is not parametric like SW, so you cant even back up the tree to see where things have gone awry. (Rhino is 1/5 the price which explain some of the issue).
Last edited: