Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations GregLocock on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

Error using MultiBody part

Status
Not open for further replies.

EUANS

Mechanical
Nov 8, 2002
17
I have a complex assembly which I want to save in a simplified format. I have tried saving the assembly as a multibody soildworks part (all components option). I can successfully save the part and as expected the file size is a fraction of the original assembly. However when I subsequently open the multibody part SolidWorks crashes with the message "Solidworks has terminated due to an unhandled error". This is also reproducable with the external components and external faces options. I am running SWX 2003 sp 3.0.
Has anyone else experienced the same problem? Is there an alternative way to save a simplified version of the assembly?
 
Replies continue below

Recommended for you

Some questions you may have already asked yourself...

Are there any complex parts or surfaces that may be gumming up the works?

Does it work fine when you remove certain components?

Can you make a multibody part of a simpler assembly?

How about simplifying the assembly, first? Perhaps dissolve all subassemblies before saving as multibody part.

[bat]Good and evil: wrap them up and disguise it as people.[bat]
 
Have you tried opening this on someone elses computer to see if it crashes? This will tell you if it's the part or the computer.

If it's the part I would try some of Tick's Suggestions.

If it's the computer then I would start by restarting my computer.

Maybe the latest SP 4.0 might fix it. Call your VAR and send the file to them and let them test it, if you don't want to upgrade.

Maybe - faq559-507

Hopefully it won't come to this, but - faq559-488

Unhandled errors are random and it some times it takes time to figure out what the problem is. It might be as simple as a corrupt file to a DLL corruptting itself. No one knows but testing it with some of the above methods help determine the cause or at least where it is located - File or Computer.

Regards,

Scott Baugh, CSWP[wiggle][alien]
3DVision Technologies
faq731-376
When in doubt, always check the help
 
I hate to sound like a broken record...

What OS are you running?

How much memory do you have?

What graphics card and drivers are you using?

I am in contact with our customers on a weekly basis. I take 500-800 part assemblies and Save As a SLDPRT, with exterior faces only. I then Save As to whatever file format works for them, be it STEP, SAT or Parasolid. I've never had an issue.

MadMango
"Probable impossibilities are to be preferred to improbable possibilities."
Have you read faq731-376 to make the best use of Eng-Tips Forums?
 
The Tick
-no surfaces, only solids but some are complex
-removal of these makes no difference
-yes, managed ok on a really simple one level assembly

SBaugh
-haven't tried on another PC yet
-have notified VAR of problem

MadMango
-Windows 2000
-1.5GB RAM
-nVidia QuadroFX 1000 (128MB)
 
Hmm... maybe it's time to install a newer SP. I am on SW03 SP3.1.

MadMango
"Probable impossibilities are to be preferred to improbable possibilities."
Have you read faq731-376 to make the best use of Eng-Tips Forums?
 
nVidia card, eh?

Maybe you already know this....

When using nVidia graphics card, DO NOT LET WINDOWS INSTALL A WINDOWS DRIVER. Windows has default drivers for nVidia cards, but they are bad for SW.

Go to the nVidia website and download and install the latest driver from there.

[bat]Good and evil: wrap them up and disguise it as people.[bat]
 
I would always use the OEM drivers, instead of the default Windows ones.

But i *did* notice one instance, when using a no-name vid card, and on WinXP sp1, where the Windows drivers were more stable (for SW) than the OEMs!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor