Page 1 of 1

A ProE Plugin

Posted: Wed Dec 06, 2006 2:39 am
by Tea_Bag
I know this problem would prob never happen due to next limit dealing with solid works but its a wish! :wink:


Thanks
Tea_bag

Posted: Wed Dec 06, 2006 10:42 am
by Miles
I doubt that "dealing with SolidWorks" would have any bearing on this. It would be a bit more realistic to ask for STEP import capability, though :wink:

Posted: Thu Jan 04, 2007 4:10 pm
by stonelli
Miles I am not sure STEP is something that Studio could import.
I thknk it can be solids based and Studio can only import meshes.

Posted: Thu Jan 04, 2007 4:26 pm
by Miles
Hi stonelli,

I guess they'd have to invest in a STEP converter :) Surely it's easier to go from Nurbs to Poly than the other way round? After all, they seem to have managed ok in the SolidWorks plug-in.

With STEP import you could have access from most MCAD software.

Maybe 3D PDF will be the new intermediary format.....?

Posted: Thu Jan 04, 2007 4:37 pm
by stonelli
Problem is that they have refused to import DXF with ACIS solids (and DWG) stating that they only import pre-meshed formats so your suggestion would require a change or mind.
There are a lot of programs (AutoCAD, for one) that would benefit if Studio could mesh solids at imoport so it definitley would be nice if NL had a change of mind.
Incidentally, I think our product team have found a decent workflow for ProE. If you are interested I will try to find out what they do.

Posted: Thu Jan 04, 2007 5:08 pm
by Miles
I didn't know that. I think they're making it difficult for a whole segment of the market, if that is the case. I'm not sure I understand the difference between using Parasolid in the SolidWorks plug-in and importing Step into Studio. Or can they use the display mesh in SolidWorks?

Perhaps the problem with AutoCAD is that Megalodesk went their own way since ACIS V7, I think. We're now on ACIS 16....

Thanks, I'm interested. My present workflow is pretty good, though: Step import into Rhino (evaluation version) and then use the Rhinoll plug-in to export to mxs. Part names are retained etc.

Posted: Thu Jan 04, 2007 6:18 pm
by stonelli
Miles wrote:I didn't know that. I think they're making it difficult for a whole segment of the market, if that is the case. I'm not sure I understand the difference between using Parasolid in the SolidWorks plug-in and importing Step into Studio. Or can they use the display mesh in SolidWorks?
PE and SW are not my bag so I don't really know :-)
Miles wrote:Perhaps the problem with AutoCAD is that Megalodesk went their own way since ACIS V7, I think. We're now on ACIS 16....
I use Microstation which is fully AC2007 compliant through the use of the OpenDWG libraries so if NL wanted to it could import DWG no problem.
Though, Automegalodesk has definitley pulled some kind of trick with AC2007 file format because even though AC opnes the DWGs exported from MS with no problem and MAX does as well, the File Link utility in MAX does not work properly with DWGs exported from MS but is fine with ones from AC....
Miles wrote:Thanks, I'm interested. My present workflow is pretty good, though: Step import into Rhino (evaluation version) and then use the Rhinoll plug-in to export to mxs. Part names are retained etc.
Will see what I can find out. The guy that I remember telling me he had figured it out is still on hols. I think he found a way to go out to OBJ that was coming into Studio fine, but I don't know whether parts were retained or not.