Re: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve
Posted by
Keith Rumley
on 2002-11-07 10:39:20 UTC
Hi,
I use 3D CAD daily (commercially), as well. As Tim has mentioned, what you
want it for has much to do with what you should choose. Skills transfer
between programs doesn't touch the hobby market, but is important in
business.
Tim G. wrote:
for me Vector's user interface was a paradigm shift from the majority of
common commercially used programs.
Rhino's interface allows ACAD power users to get up to speed quickly. Having
ACAD experience, Rhino doesn't require of me the learning curve Vector
would.
I chose to go the route of having separate programs for CAD and CAM, for the
reasons above.
Vector is a good choice if you need both in one package, will stick with it
during the learning curve, and are not planning on moving to other packages
within the time you'd need to justify some repetition of learning curve.
- Keith Rumley
My perspective of CAD programs and their generalized USER INTERFACE
ease-of-skill transfer family:
(definitely NOT by capability)
Family 1 (Wireframe-ish base)
Vector
Family 2 = (Wireframe-ish base)
BobCAD
AutoCAD R(x)
IntelliCAD
Rhino (probably the best NURBS surface tool out today)
CADKEY
MasterCAM
SurfCAM
OneCNC
Family 3 (Solid-ish)
ProDesktop Express
ProDesktop
Alibre Design
IronCAD
Inovate
ProEngineer
SolidWorks
SolidEdge
TurboSolid (My current 'if-I-could-justify-it' favourite)
DelCAM
Unigraphics
Ashlar-Vellum (Cobalt, etc)
Inventor
Mechanical Desktop
CADKEY (sort of)
OneCNC (sort of)
I use 3D CAD daily (commercially), as well. As Tim has mentioned, what you
want it for has much to do with what you should choose. Skills transfer
between programs doesn't touch the hobby market, but is important in
business.
Tim G. wrote:
> So, I sit by my contention. Vector is an easy to learn and useIt seems to me that it is the issue of skills transfer here. I found that
> CAD/CAM program. While it is very capable even in the NURBS
> version it is not as powerful as Rhino. That is the reason I am
> working at becoming a Rhino user.
for me Vector's user interface was a paradigm shift from the majority of
common commercially used programs.
Rhino's interface allows ACAD power users to get up to speed quickly. Having
ACAD experience, Rhino doesn't require of me the learning curve Vector
would.
I chose to go the route of having separate programs for CAD and CAM, for the
reasons above.
Vector is a good choice if you need both in one package, will stick with it
during the learning curve, and are not planning on moving to other packages
within the time you'd need to justify some repetition of learning curve.
- Keith Rumley
My perspective of CAD programs and their generalized USER INTERFACE
ease-of-skill transfer family:
(definitely NOT by capability)
Family 1 (Wireframe-ish base)
Vector
Family 2 = (Wireframe-ish base)
BobCAD
AutoCAD R(x)
IntelliCAD
Rhino (probably the best NURBS surface tool out today)
CADKEY
MasterCAM
SurfCAM
OneCNC
Family 3 (Solid-ish)
ProDesktop Express
ProDesktop
Alibre Design
IronCAD
Inovate
ProEngineer
SolidWorks
SolidEdge
TurboSolid (My current 'if-I-could-justify-it' favourite)
DelCAM
Unigraphics
Ashlar-Vellum (Cobalt, etc)
Inventor
Mechanical Desktop
CADKEY (sort of)
OneCNC (sort of)
Discussion Thread
Tim Goldstein
2002-11-05 18:51:02 UTC
Re: [CAD_CAM_EDM_DRO] vector's learning curve too big, any other suggestions
Scott A. Stephens
2002-11-05 18:55:31 UTC
Re: [CAD_CAM_EDM_DRO] vector's learning curve too big, any other suggestions
Tim Goldstein
2002-11-05 21:11:05 UTC
RE: [CAD_CAM_EDM_DRO] Rhino, Was:vector's learning curve
Ian W. Wright
2002-11-06 02:02:01 UTC
Re: [CAD_CAM_EDM_DRO] Rhino, Was:vector's learning curve
Andrew Werby
2002-11-06 13:52:22 UTC
Re: Rhino, Was:vector's learning curve
Tim Goldstein
2002-11-06 14:22:21 UTC
Re: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve
stevenson_engineers
2002-11-06 14:45:32 UTC
Re: Rhino, Was:vector's learning curve
Tim Goldstein
2002-11-06 14:58:49 UTC
Re: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve
Carlos Guillermo
2002-11-06 16:26:14 UTC
RE: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve
Scott A. Stephens
2002-11-06 16:46:35 UTC
Re: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve
thomasm923@a...
2002-11-06 20:16:10 UTC
Re: Rhino, Was:vector's learning curve
Chris L
2002-11-06 21:49:24 UTC
Re: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve
Chris L
2002-11-06 22:02:18 UTC
Re: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve
stevenson_engineers
2002-11-07 00:50:54 UTC
Re: Rhino, Was:vector's learning curve
Ian W. Wright
2002-11-07 01:44:41 UTC
Re: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve
Ian W. Wright
2002-11-07 06:16:29 UTC
Re: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve
CL
2002-11-07 10:19:57 UTC
Re: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve
Keith Rumley
2002-11-07 10:39:20 UTC
Re: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve
Keith Rumley
2002-11-07 10:39:22 UTC
Re: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve
Keith Rumley
2002-11-07 10:39:24 UTC
Re: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve
Keith Rumley
2002-11-07 10:48:03 UTC
Re: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve
Fred Smith
2002-11-07 14:36:52 UTC
Re: productivity in drawing, was Rhino, Was:vector's learning curve