Solidworks vs proe

[josephlordy]

I understand that it depends on what you are doing. There
are several things in Pro E that I would have liked to
see in Solidworks.

However, although different people use it for different
things, i still found that doing BASIC things such as
extrusions, section views, sketching, and drawings is
still much more laboured than working in Solidworks. I
could not believe the bizzare way I had to generate a BOM
table in a ProE drawing.

I personally have only worked in small companies on local
installations, so I can see how ProE may have many
benefits for different profiles and setups to be loaded
by different people doing different jobs. But once again,
it is the fundamental basics of modelling and drawings
that we ALL do that I find difficult. When I have to go
onto ProE from Solidwork to access our legacy data, it
feels like someone has put the brakes on.

We actually need to do some modifications to a few parts
that were in ProE, but what I did was save the Pro E
files as STEP files, import them into SOlidworks, carry
out all the remodeling and supply toolmakers with the new
files from Solidworks. This was so we could get it done
in time. I then had to retrospectively re-model the ProE
files after the fact, when the pressure was off.

 

[MarkEngr]

Amazing how well SW feature works in translating other file formats, isn't it? ProE in my op does'nt handle this near as well. Yes its justmy self-centered, bizarre or egotistic opinion coming into play here again?
Edited by: MarkEngr

 

[CLBrown]

Amazing how well SW feature works in translating other file formats, isn't it? ProE in my op does'nt handle this near as well. Yes its justmy self-centered, bizarre or egotistic opinion coming into play here again?

The reason Solidworks is able to work with Pro/E files is because they've licenced PTC's "Granite" kernel, which gives them access to Pro/E files. So, yeah, it works very nicely with Pro/E type files because it has some Pro/E code in it.

You should credit PTC for making the Granite kernel "licenseable" for this. Don't give the SW guys credit for their having somehow developed, on their own, this capability.

The total list of file formats Solidworks gives me access to is far, far shorter than those I can access from within Pro/E. And in terms of truly "neutral" file formats... STEP, IGES, etc... Pro/E does a better job, I've found.

And I still can't believe that I can't even export an "OBJ" file from Solidworks... trying to share our design files with our marketing department's graphics team is a nightmare as a result.. The "OBJ" file format is the most common 3d-rendering interchange format, after all.

 

[proximo]

This is getting silly now.

Creo and SolidWorks are both great programs and they both
have their set of limitations. We can sit here and nit
pick all day long but for someone who knows both
programs, I can't see how anyone would argue that
overall, Creo is more powerful.

SolidWorks is compared to Creo because of it's popularity
but let's not forget that Dassault makes a High End CAD
program called CATIA and they make a Mid Level CAD
program called SolidWorks.PTC makes a High End CAD
Program called Creo. Trying to compare SolidWorks to
Creo in total capabilities is silly.

SolidWorks is a fine piece of software but it's not
capable of doing high end functions that Creo can. I did
an evaluation at one point with SolidWorks and it was not
capable of creating the advance surfaces we required and
I had people from SolidWorks try to create the surfaces I
required and they could not. Hands down, Creo is more
powerful.

Creo is more user friendly than Pro/E was, so they are
making changes in the right direction. If you only
require basic to intermediate modeling, SolidWorks and
Creo will both be great choices. If you require more
advanced functions, Creo is the choice.

I also think if anyone says that one is better than the
other "Period", you are not being realistic. This is
suggesting that the software you like has no issues, no
limitation and can do it all. This is not true so making
such statements is silly and goes in line with the
"fanboy" label.

Creo and SolidWorks both have limitations and things they
could do better while at the same time they both have
great features that most people could use to create great
designs.

 

[emilyhu]

Thank you for the excellent useful publish. We can all
agree that nothing is ideal and upgrades will
always be asked for.

I also use SolidWorks but I am not as efficient with it
as Pro/E due to the decades I have invested into Pro/E. I
guess aspect of my observation has to do with how long I
have invested with Pro/E and the sensation I get that PTC is
no a longer period targeted on CAD as they where in the last.

 

[proximo]

PTC dropped the ball on CAD when they started to focus on
PLM. With the new CEO in place, his mission is for PTC
to once again be the leader in CAD and this is where Creo
came from. They invested 100 million dollars to develop
Creo as their new CAD platform. Creo is far superior to
Pro/E and much easier to use. It's not perfect because
it's software and everyone always wants more
capabilities.

SolidWorks is also a fantastic CAD package and I love
some of the features they have that Creo still needs to
improve on or in some cases implement. But Creo also has
some features that SolidWorks does not yet have or they
must improve.

The bottom line is that SolidWorks makes Creo beter and
Creo makes SolidWorks better. Without competition, there
is no need to innovate and win customers over.

No matter which one you choose, you will have a great CAD
package. No matter which one you choose, you will have
some limitations and frustrations with it.

Just study carefully what type of work you do and choose
the one that fits best. Don't look for perfection
because it does not exist.

Thank you for the excellent useful
publish. We can allagree that nothing is ideal and
upgrades willalways be asked for.I also use SolidWorks
but I am not as efficient with itas Pro/E due to the
decades I have invested into Pro/E. Iguess aspect of my
observation has to do with how long Ihave invested with
Pro/E and the sensation I get that PTC isno a longer
period targeted on CAD as they where in the last.

 

[MarkEngr]

Amazing how well SW feature works in translating other file formats, isn't it? ProE in my op does'nt handle this near as well. Yes its justmy self-centered, bizarre or egotistic opinion coming into play here again?

The reason Solidworks is able to work with Pro/E files is because they've licenced PTC's "Granite" kernel, which gives them access to Pro/E files. So, yeah, it works very nicely with Pro/E type files because it has some Pro/E code in it.

You should credit PTC for making the Granite kernel "licenseable" for this. Don't give the SW guys credit for their having somehow developed, on their own, this capability.

The total list of file formats Solidworks gives me access to is far, far shorter than those I can access from within Pro/E. And in terms of truly "neutral" file formats... STEP, IGES, etc... Pro/E does a better job, I've found.

And I still can't believe that I can't even export an "OBJ" file from Solidworks... trying to share our design files with our marketing department's graphics team is a nightmare as a result.. The "OBJ" file format is the most common 3d-rendering interchange format, after all.

Actually SW Feature Works does the best job at rebuilding an editable feature tree from my experience bar none; stp, iges, & native proE files. Why does ProE not import a native SW sldprt file from their drop down listing of types?; Why? are they frightened. This is not an egotistic/biased statement. Where is a Toolbox alternative in ProE & what the heck does Y-factor in the program regarding sheetmetal have to do with anything, since it is a func of Y-factor& Y-fact is the decades old nomenclature used virtually everywhere else. So the answer from my perspective is that SW imports/translates other file formats much better hands down when obtaining model data from other vendors.


& Once you use their sheetmetal app you wont go back, not to mention the intuitivenes of the program itself.
Edited by: MarkEngr

 

[slashct]

Why does ProE not import a native SW sldprt file from their drop
down listing of types?; Why? are they frightened. This is not an
egotistic/biased statement.


Not Egotistical but must be from a Solidworks User that Knows NADA about Pro/ENGINEER. YOU CAN Import directly into Pro/ENGINEER you need SW design explorer, why BECAUSE YOUR BELOVED SW Corporation won't allow PTC to do so directly. You can get a dll that is needed, again not from PTC BUT FROM SW.. SW requires you to register with them to get the needed files.... PTC is not allowed to distribute them.

 

[MarkEngr]

Nada? now really Slash. Now where is the 'beloved' as you say equivalent in ProE to SW's Toolbox? Instead of 'Unhiding' a feature item in Pro, I can simply show it in SW. It's called logic & there arenumberous other examples of such between the 2 programs.
Edited by: MarkEngr

 

[proximo]

PTC made their Granite Engine open to everyone which is
what SolidWorks is using to open native Pro/E files.
SolidWorks did not do this for their kernel which means
they are the scared ones.

Don't give SolidWorks credit for PTC's willingness to
share their Kernel externally for this purpose.

Amazing how well SW feature works in
translating other file formats, isn't it?