class A surfacing | classasurfacing | class A surface| Digital Sculpting
September 04, 2010, 11:43:10 PM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Welcome to Class-A Surfacing, a learning resource for industrial cosmetic surface geometry creation. You will see tons of new content in the coming weeks. Ask you questions and please give us more of what you would like to see.

If you have a need for one of the experts on the forum for consulting or design work please contact mail@classasurfacing.com.

Best regards

Class_A_Surfacing
 
   Home   Help Tags GoogleTagged Login Register  
Pages: [1]
  Print  
Author Topic: the CAD religions  (Read 439 times)
adam
Newbie
*
Posts: 11


« on: February 27, 2009, 05:50:21 AM »

Everybody that does serious CAD for a living stands by their tool of choice as though it were the most sacred of religions. Some of the most fierce are (strangely enough) Rhino users. It's crazy!

I wish CAD packages would work more towards interoperability. SpaceClaim is a big help with this, as it can read almost any format and make direct modifications to almost any geometry.

So what do you guys think? Is it better to stick with one monolithic package for all-things-CAD, or to use specific packages for their specific advantages?
Logged
Stevo
Global Moderator
Newbie
*****
Posts: 13


« Reply #1 on: February 28, 2009, 09:04:02 AM »

You do bring up some good points Adam.

In my vast years of experience the true culprit for bad interoperability is poor modeling technique. Surface is a surface is a surface. If modeled correctly than translations are easy. Real easy. The issue is if I take a final design out of lets say UGNX and translate it to Alias can the math be easily represented. UGNX can have 24 degree surfaces. Alias can not. At this point is where the translation becomes dodgy. If the correct modeling practices were used there should never really be an issue as the highest level of surface complexity will never surpass what a system can handle in translations.
Logged
nicolas
Newbie
*
Posts: 8


« Reply #2 on: April 06, 2009, 09:31:26 AM »

In my point of view, using only ONE package to do all should be an utopy. I did not think one software could build "well" our 3D data from the styling to the tooling...

Also I did not like the "trust" position for this kind of soft... Cause in case of only ONE soft stay in the industrial market, which price we will pay for buy it, without concurances?

At this moment, many "translated" issues (move from one software to another one) come from the complexity and the different level of all these siftware we are using now. Means we can not use all the new functions according to the last release of our sofware and we need to find some "standard" according to our knowledge of the industry where we are working day by day.

For me all A-Class standard from the car industry come from at least 10 years ago... Anyway, these standards are good but probably it will be nice to make some adjustements to match with the new tools and working way. But it is another story!
Logged
Tags:
Pages: [1]
  Print  
 
Jump to:  

sitemap1 sitemap2
Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC
SMFAds for Free Forums
Valid XHTML 1.0! Valid CSS!