Rhino vs. ProE

ProE - features and history, parts and assembliesparametric modeller

Rhino - freeform modeller no features or history or assemblies and not a parametric modeller

Not comparable products but very complementary, its sometimes good to jump into Rhino for a 'quick and dirty' mockup or a more complex freeform surface form - although the popularity and development of ISDX has stalled that a bit in my camp.

Be prepared for some heart ache on the learning curve if your a big ProE user. If you start with Rhino it has a shallower learning curve but moving to it can be problematic at it has a very different philosophy in the building - imagine not being able to easilytweak feature number 2 of 100 and the effect neatly propagating through the model tree? setting geometric conditions does not form a relationship - the condition will not follow changes to surrounding geometry,

Sean

I agree.

Rhino and Pro/E are not comparable. Two totally different modeling methods. Pro/E would be catered more to engineering and design, while Rhino is great for visualization and free form concepts.

If you plan to make changes to a model, Rhino would take a lot more work and limit you in many ways. Pro/E will be very simple and quick to modify. This is assuming you created a good model to work from.

Don't go by the images you see on the Rhino site. That is misleading. If you actually use Rhino, you will realize that it's a completely different animal and would probably not fit in a Design Engineering type of environment.

"Too many people walk around like Clark Kent, because they don't realize they can Fly like Superman"

Meanwhile, there is a free add-on that works in WF4, at least, that is supposed to automatically open a Rhino file and let you generate a Pro/E part.