SolidWorks .exe file? How to import it in Sketchup?
-
@watkins said:
If you client has sent you an assembly, then ask him/her to send you the individual parts as .sat files and then go the AutoCAD route. Not sure what else to suggest.
And then assembly them manually in sketchup? Is this a way too... there are not so many elements.
Thanks. -
I'd be interested too but I think those exe files are compressed and locked. The last time I had one, I just rebuilt the whole system myself. My guess is that you ask fr 3dxml files or other editable format, that you may convert to DAE and reimport in SU ...
-
Not a Solid Works user, but a .exe is typically a program (with data built in), not a pure data file like .skp, dxf, dwg, etc. There may be no translator that will work with that kind of file. Unless you go to the Solid Works user, and ask him for an data export that SketchUp can import, you may be out of luck.
-
As an analogy (although may be a bit of), it is like asking someone to make a dxf export from an animation exported from SU.
Is there any data-like file that client could export from SW?
-
@gaieus said:
As an analogy (although may be a bit of), it is like asking someone to make a dxf export from an animation exported from SU.
Is there any data-like file that client could export from SW?
No, is not like that. Is the actual SW file, but somehow compressed and a viewer added. If you want analogy, think on a SKP file with Sketchup Viewer embedded. You have access to geometry, but can't edit. Just see sections, elements, perspective on/off, rotation, scenes.
-
It's a 'read only' version.
The viewer and data are fused into one exe file.
You're screwed.
IF the client wants you to have the data in a usable format then get it that way initially....
-
@tig said:
It's a 'read only' version.
The viewer and data are fused into one exe file.
You're screwed.That's why I brought that extreme analogy. Both are completely useless - unless you remodel everything eyeballing it.
-
-
A typical Solidworks part should end with the extension;
.SDLPRT
an assembly being
.SDLASM
-
if the file is made with the eDrawings Publisher f. Solidworks you can try to open it w/ the free eDrawings SolidWorks Viewer and save to a vector based format as e.g. STL which then could be converted to something for SU useable as e.g. the Collada DAE format by the free MeshLab.
If the eDrawings Viewer refuses to open the EXEcutable directly you may try if changing the file extension to something supported helps.
btw, AutoCAD is mainly used - at least by professionals - for drafting of 2D (shop) drawings and therefore not really competing w/ a 3D MCAD modeler as e.g. SolidWorks... or Autodesk Inventor.
hth,
Norbert -
@sketch3d.de said:
btw, AutoCAD is mainly used - at least by professionals - for drafting of 2D (shop) drawings and therefore not really competing w/ a 3D MCAD modeler as e.g. SolidWorks... or Autodesk Inventor.
I don't entirely agree. Autodesk and Dassault have been at loggerheads with each other for quite a while now. Neither will open each others files properly- if at all, yet both are quite capable of both 2D and 3D. FWIW, Solidworks does actually produce rather beautiful 2D drawings, and easily too. They each want a piece of the pie- although I don't ever really see Solidworks becoming an application of choice for architects. I think that's where Autodesk have really clinched it.
-
It's a 3D model. I talked to the client and I will have the non-encrypted files.
Thanks for SW/skp plugin link. -
Excellent! That's what we're here for!
Advertisement