Eltron
Mechanical
- Mar 3, 2005
- 2,459
OK. I have an annoying issue that has burned me on two occasions now, and I wanted to share my workaround. I have a client that wants pretty pictures of their pilot plant model. It has hundreds of pipe runs, reactors, vessels, etc. They use some "other" software to generate the model, so they send me .stp files (well over 100 Mb). It takes some time to open them, but they eventually open up. After it opens I have an assembly complete with parts and subassemblies. I save it, make changes, save it, make changes, save it, take a nap, make changes, etc. At the end of the day I close everything down like a normal person. Next day I open the assembly, and SW forgets its brains. It can't find any of the parts or subassemblies even if I point it to them and they are all in the same folder. All of the previous day's work is flushed down the SW dunny.
Turns out this is a known issue and has been for a while...surprise, surprise (SPR 537279). Since SW knows about it I figure it should get fixed right around the time the Cubs win the world series. I'm not holding my breath. Anyway, my workaround is to save the assembly as a multibody part immediately after extracting the .stp file. I lose assembly functionality, but at least I can make a pretty picture...and keep from punching a hole through my monitor and polluting the innocence of my office mates with offensive language.
Dan
Dan's Blog
Turns out this is a known issue and has been for a while...surprise, surprise (SPR 537279). Since SW knows about it I figure it should get fixed right around the time the Cubs win the world series. I'm not holding my breath. Anyway, my workaround is to save the assembly as a multibody part immediately after extracting the .stp file. I lose assembly functionality, but at least I can make a pretty picture...and keep from punching a hole through my monitor and polluting the innocence of my office mates with offensive language.
Dan
Dan's Blog