Hi BurrMan,

The next thing i want is a computer
like HAL 9000 'A Space Odyssey'
(just joking)

I think programs like Moi3d are already
a good step in the right direction
So i can't pretend to much from programmers
like Michael

50 jears ago nobody could imagine that we
modeled something using nurbs

The next thing i want is a computer
like HAL 9000 'A Space Odyssey'
(just joking)>>>>

My first computer was an Apple given to me with no OS on it. I turned it on and saw a blinking cursor......

I typed "HELLO"......., waiting for a response. :)

Called a friend who programmed at NASA and asked why it didnt respond and he told me to get a book on programming. I wrote my first goto, and so it began. I am interested in the design thing.

Oh yea, HAL is here!

Thanks,
Burr

Hi Burr,

> an NX guy, could probably open Rhino and go to work.
> definatley MoI and do sweeps, revovles etc.
> The knowledge of the general nature of things makes him "A qualified Designer".
> The move to a new software would more or less be a bit of time learning the
> interface and a few lingo differences.

I feel there is a misconception here, please correct me if I'm wrong.
In some ways the above statement is true, once you've gained experience in modeling with one 3d software if you use another 3d software the learning curve is greatly reduced compared to someone who has just started out in the 3d world.
But, using NX does not make you a better designer than someone using MoI or Rhino, these are just tools used to express ideas and designs in this digital world of ours, otherwise as in the past we would still have great ideas and designs but would be presented via some other medium, be it on paper or an actual hand crafted model.

> could and nx guy step into archi software and learn buildings?
> Could a buildings guy do mold injection?

Yes, but both guys would have to be trained in these fields and gain experience, you have to realize that the software doesn't teach you how to design, the designer uses the software to convey their ideas.

I've always had the belief, If you are passionate about something, I mean real passion and interest, you will learn everything there is to know about that subject, so if a Mechanical Designer has a passion and interest in Architecture they would learn everything there is to know about it and become a good architect because they enjoy doing it.
But on the other hand if you are passionate about 3D modeling you will become a good 3D modeler, but it doesn't make you a designer.


> I suppose I want to be able to do Plastic injection Molding, and
> Parametric change design, and also draw a 50 story building with all the detail.
> Where is my 2 year training best spent. Are the 2 training courses complimentary or exclusive?

When you say training, is that training in the aspect of those fields of expertise, because there is a lot more theory and experience involved in these fields than there is 3d modeling, as I mentioned before 3d modeling software is only a tool just like the 'T' Square and drawing board was in the past.

Hope we're on the same page here.

Sure Danny your right on. If I can convey my intrest I'm sure you could answer.

When I say training, I'm not going to college to become a Mechanical Engineer. I mean going to "Solidworks" Classes or "Rhino" Classes. I think the softwares offer training. I would have to start at "Know's Nothing" and progress through to a point where my intrest, ability and needs are met.

Lets seperate 2 area's here.

1.Design, inspiration and ability (Individual)
2.Tools available, Environment exposure, resources to draw from (circumstances)

I'm refering more to 2.

When I talk of you being proficient in NX I mean we dont have to explain "2 rail sweep" to you. more so there are functions in Rhino or Solidworks I would not understand as MoI is not in this area. You would know this as it must be standard stuff.

>>Yes, but both guys would have to be trained in these fields and gain experience, you have to realize that the software doesn't teach you how to design, the designer uses the software to convey their ideas.
>>.

Theres the point. An artistic guy would have to know what the toolset is capable of and be aware of whats available to move forward. Learning the software opens the possibilities and also "I beleive" sets limitations.(These limitations are overcome by the experience you mention, but I would be limited in my approach until I gain this experience. ie; different software does different things). With this I could utilize different tools in the future as i realize what I need to perform.

Hence, Taking a Rhino Class to learn their software will open many avenues for me. ("I never thought of it like that!).

So I guess does the 2 equate (Solidworks and Rhino) is a question to expound on. Does one give a more "Well rounded" experience or are they so mutually exclusive that you need both classes? Does well versed in one move easier into the other? (a Solidworks guy may use rhino for that thing rhino does so well, but he doesnt have to be an expert to utilize rhino... already knows functions of design, but may not work vise-versa, ie; would rhino guy be able to or need to utilize solidworks?.)

This could go on forever I suppose.

I'll be designing actual parts and things like assemblies, but i wont be designing buildings. Interoperabilty is a key factor.

Burr

Hi Burr,

> I'll be designing actual parts and things like assemblies,
> but i wont be designing buildings. Interoperabilty is a key factor.

Well there's a key word that points to Solidworks, "assemblies".

This is where Solidworks has it's strengths over Rhino, for example in Solidworks when you do an assembly you have the parts 'mated' and these mated faces are remembered by the software so if you move a face in one part say by making it slightly thicker, the mated part would automatically adjust to it, or if you have a shaft diameter linked to a hole diameter in another part, when you change the hole diameter the shaft will adjust accordingly, this is what parametrically linked is.
But Solidworks is mainly a solid modeler the surface toolset is not as rich as Rhino's, like it would be more difficult to achieve more organic shapes in Solidworks than it would in Rhino or MoI.

So you have to weigh up the strengths and weaknesses of each software with what you want to use it for.

Hope this helps.

Thanks Danny,
Seems they are just 2 different animals. May start with Rhino and later move to the parametric stuff. It's feature rich and I should learn most design concepts from there, and then expand out later.

MoI is allowing me to build some fundamentals to take to the next level as a base.

Burr

BTW: Can Parametric be NURBS? What is solidworks?

Hi Burr,

> BTW: Can Parametric be NURBS?

Yes - the standard type of parametric software generates NURBS objects. The objects themselves are NURBS using the same type of geometry that MoI use.

The stuff that makes it "parametric" is the workflow, the UI, and all the other history mechanisms and editing tools which are all extra things than just the NURBS surface geometry.


> What is solidworks?

It's a parametric history-based solid modeler.

- Michael

Hi Burr & All....

Basically I come from solidworks. I have been use solidworks for 3 years. Its a powerful solid & surface modeling also. The big different is solidworks have a parametric concept like Michael mentioned before. As I know solidworks is the easiest parametric modeling software.

But today my favourite software is MoI ( because the easy to use workflow & of course MoI is very affordable ).
You can open MoI file directly use solidworks. So it will give you a good combination.

You can find some solidworks video here : http://www.solidworks.com/pages/products/swofficepro/SWOfficePremium_VidVau_fore.html
Also check this link : http://download.rhino3d.com/download.asp?id=rhino-solidworks

OK, that is my opinion ;)

Thanks guy's. I think I would utilize both. The training I will start with Rhino for a bas then move to solidworks to add to the toolset.

Thanks again.
Burr