Continue to Site

Welcome to MCAD Central

Join our MCAD Central community forums, the largest resource for MCAD (Mechanical Computer-Aided Design) professionals, including files, forums, jobs, articles, calendar, and more.

WF 5.0 can call up SolidWorks files

Moroso

New member
In Wildfire 5.0 you can now call up native SolidWorks files without having to convert it to step or etc..


This is a huge step for me, great job on this PTC
 
Perhaps you can get Native proe files in Solidworks
too...who knows... this is corporate existence perhaps.
OR...
Could it be that PTC is buying Solidworks !!!!
smiley4.gif

smiley36.gif
smiley36.gif
 
Solidworks had this feature for a long time, list knock the .1 off the part file and it will call Pro/E parts
 
What version of SW files will it call up? I'm assuming you get just a dumb blob, no features, right? That would be something if we got features too. Still, skipping the IGES/STEP is an improvement.
 
It worked on a 2008 SolidWorks file.


It brought it in as an assy with a neutral feature and the part being imported.
Edited by: Moroso
 
Well you obviously wont get a full model tree....I'm right in assuming that???


So really...whats the point in it??? If your working on a complex surface model, molding etc for production... and you get given a Solid girl file to use you can still only add/take away...you wont be able to edit an existing feature or such like...So its still a surf ref or skelleton at best isn't it.....

Infact I think the only real reason this feature has been added is so that PTC can push another release of Pro E out with some more "essential time saving / improoved work flow" features....

How often is this a problem for most designers/engineers?? If your forced to work cross platforms with other companies / designers or engineers..9/10 you can either ask for a STEP or IGES as both progams can import / export well with these formats...

I guess if it is able to retain information such as a B.O.M, materials, mechanism info etc it could be worth while...

Has anyone put it to the test?

Sounds like a load of old coblers! And PTC will probably pump WF5.0 up an extra $5K for this Solid girl "feature"....
 
I think any time you eliminate a step, you've go the opportunity to get cleaner geometry. Each translation, out of SW to IGES or STEP and then into Pro|E from IGES or STEP, introduces the possibility for errors. Direct from SW to Pro|E is nice.

As a consultant, the ability to take either a SW or Pro|E model (we have SW anyway, but the theory applies) is a plus. Even if we didn't have SW, I can tell a client that I can read their SW files. Of course, I'd have to be up front about what software I'm going to use, but in some cases we only need to view the models as a reference. Then the client doesn't have to do anything but email me files. I don't know how many times I've ended up in several phone conversations or emails to get the right combination of file types so that we can open someone's files. They thought we could read native Catia, now marketing needs engineering to call us. Engineering takes a couple days and sends an IGES. The IGES is full of holes so we have to request a STEP. We might loose 3-4 days in the process. I'd love it if Pro|E could read any standard 3D CAD file as a dumb blob.

I love things that make it easier for folks to work with us.
 
You bring up some good points Doug.


We, on the other hand, have had trouble with SW2005 opening ProE models. Nothing told us something was wrong or failed but features would have "moved".


We have both SW and ProE but use STEP or Parasolid to transfer data.


Once bitten twice shy.


Kevin
 
Yeah, we've found that STEP works pretty well between SW & Pro|E. I thought the SW option of opening native Pro|E files went away when Pro|E went to the Granite kernel back in 2001 or WF1.
 

Sponsor

Back
Top