Post by jon_banquerPost by vinnyc2 surface editing? I didnt realize it had a name.
Tommy Brewer hasn't quite figured out that C2 surfacing in SolidWorks
is parametric where as in Rhino it's not. He's not the sharpest guy in
the world. Tommy Brewer is very much stuck in his own little world and
thinks his narrow little world applies to everyone. Same for Joe788.
Both propaganda gurus are much like Joseph Goebbels with their lies
and tactics.
Without C2 surfacing what you design often looks like a toy vs. the
real thing. It's a must for many users.
Joe788 has never designed anything with cosmetic flowing lines in his
life and has no clue why they would be needed. I doubt Tom Brewer has
either. The best a lying, sodomized shitbag like Joe788 can come up
with it that most machine shops don't need C2 surfacing. His doesn't
but lots of people and some shops do need C2 surfacing. It all depends
on what you want to accomplish. Until SolidWorks got C2 surfacing in
SolidWorks 2007 it was severely handicapped for many users. SolidWorks
no longer is handicapped in this way. What SolidWorks still needs is
much better documentation on surfacing, though. Perhaps Matt Lombard's
next book will be better because it appears to focus on large projects
and it's a lot harder to bore someone to death with bad writing when
http://dezignstuff.com/images/Picture2.jpg
While this is not as original as what James Carruthers does, it does
look to be a big step in the right direction for documenting
SolidWorks surfacing. Here is an example of the kind of extensive
tutorial James Carruthers does for Rhino that I consider to be much
http://www.hydraulicdesign.net/fvs3-sample/concept-a-sample.htm
Both Joe788 and Tommy Brewer are also too fucking stupid to understand
why Multi-Bodies are critical for machining job shops using
SolidWorks. After being really impressed with SolidWorks great start,
I and lots of shops I knew put SolidWorks on the self until Multi-Body
support became available. I don't think Multi-Body came into effect
until SolidWorks 2003. Without Multi-Body support you were forced into
assembly mode to do the simplest things. Back in 2007, I was living in
Connecticut and teaching SolidWorks part time. I had a 2 seat
educational license for JB Tech.
Joe788 is also too fucking stupid to know that both CNC Software
(Mastercam) and Surfware (Surfcam) at one time had cam products that
ran inside of SolidWorks but killed development of their products that
ran inside SolidWorks when SolidWorks failed to come-up with a way to
create and edit imported surfaces. CNC Software's product was called
SolidMaster. I think Surfware's product was called NC Solids 2 and NC
Solids 3. Both products were killed for damn good reason... SolidWorks
Corp. failed to put the needed surfacing tools into SolidWorks in a
timely manner! These kinds of FACTS elude lying assholes like Tommy
Brewer and sodomized Joe788 because they wish to rewrite history.
It's been a long evolution from a great start with SolidWorks, to
lagging badly, to becoming the much more real world tool that
SolidWork is today. Both Tommy Brewer and Joe788 much like Joseph
Goebbels wish to restate reality and invent their own. Propaganda is
the right term for what they try and pull. Pretty easy to see though
if one knows their SolidWorks history.
Make no mistake. I don't think this is all about one product. I don't
discount Autodesk Inventor, SolidEdge, Pro/E, etc. ability to compete
with SolidWorks marketshare in the near future.
I also don't dismiss the likelihood of SpaceClaim (non-history based
modeling) to gain acceptance and have cam run inside of it. See the
link below my sig for comments I made that were just published
yesterday. I'm still waiting for Tom Brewer or Joe788 to have any of
their comments on cadcam published in a leading online journal /
blog.
What I do dismiss is legacy code programs like Surfcam, Mastercam and
Gibbscam having any chance of competing with systems that run inside
of SolidWorks, etc. In many ways SolidWorks / HSMWorks already blows
away what's in Mastercam making Mastercam look like the outdated
program it really is.
Jon Banquer
San Diego, CAhttp://worldcadaccess.typepad.com/blog/2007/10/ptc-acquires-co.html#c...
you're talking about.
use assemblies in a CAM program. But now you HAVE to have multi-bodies
Solidworks." Jon Banquer - Oct. 28, 2007