Crashing - too much to handle?

[tikka308]

I have a fixture plate design which has more complexity than anything else I've done in Sprut in the past year (complexity = # faces). After I import the various IGS files (parts, fixtures, etc), I cannot move ("transform") them without Sprut hanging indefinitely. Granted, moving just, say, the fixture clamps is 2300 faces. I am also on a slightly older computer (P4, 2.5GHz, 2 gb ram) but I've never had Sprut come close to being this dysfunctional before.

Using V7, Build 1.6 Rev 47237 - was upgraded last week per Tormach's guidance. FWIW, my prior build did not try to render the transform. If that is the problem, is there a way to disable that feature?

[dbrija]

Originally Posted by tikka308 I have a fixture plate design which has more complexity than anything else I've done in Sprut in the past year (complexity = # faces). After I import the various IGS files (parts, fixtures, etc), I cannot move ("transform") them without Sprut crashing. Granted, moving just, say, the fixture clamps is 2300 faces. I am also on a slightly older computer (P4, 2.5GHz, 2 gb ram) but I've never had Sprut come close to being this dysfunctional before. Using V7, Build 1.6 Rev 47237 - was upgraded last week per Tormach's guidance. FWIW, my prior build did not try to render the transform. If that is the problem, is there a way to disable that feature?

Latest on Sprut's download link is 47351. Might be worth a shot.

Is this something you could post so others can try on different hardware?

[tikka308]

That'd be wonderful if someone else could try on their hardware. File is 25mb - so too large to attach. Hence I'm sharing via sugarsync. It's an IGS file.

https://www.sugarsync.com/pf/D76564_6530813_476994

[Scott_M]

I was able to move it. I clicked on transform/locate zero and it kinda hung with the cursor spinning ( which means it is thinking ) It took about 2 minutes for the data in the boxes to fill in. Middle middle max were selected and I clicked apply and it took a few more minutes for it to move. I then clicked close and nothing happened so I clicked it again and got the greyed out screen and a "not responding" message I waited a few minutes and it came back and closed . everything worked it just took a long time. So I would guess it is the size of the file.

Is it crashing for you or hanging? If it is hanging wait for it . It could take several minutes
I saved it as an stc file and it is now 41 mb.

Scott

[tikka308]

Yikes - 41mb! It did not crash on me, but I waited for over an hour - so it's not practical even if it is hanging. Scott - mind sharing your computer specs?

Here's the other question: I don't need all this darn detail - I'm only importing these clamps so Sprut incorporates them as fixtures and detects crashes, avoids hitting them while waterlining, etc. Is there a way in Alibre to simplify these so they are not 2300 faces? I know I could just create a box that's the same size as a proxy for the clamp, but it'd be nice to know how to handle this going forward

Scott - thanks for taking the time to help!

[Gerry Sweetland]

Originally Posted by tikka308 That'd be wonderful if someone else could try on their hardware. File is 25mb - so too large to attach. Hence I'm sharing via sugarsync. It's an IGS file. https://www.sugarsync.com/pf/D76564_6530813_476994

Hi Tikka,
I tried your iges file on my system, it's a Gateway DX4850 w/ an Intel Core I7-2600 CPU @ 3.40GHz and 8 Gigs of RAM. The video card is a low end Nvidia GT420, 1 Gig RAM. Windows 7 64bit. SprutCam is Ver 7 build 1.5 Rev. 45786

I was hoping it would do better than it did! It took SC about a minute to sew and about a minute to scale from metric to imperial. Device manager showed that SC was running during these two operations. I then tried to locate 0 in model mode and it caused SC to stop responding. I just let it grind away and it finally woke up to let me fill in the data boxes to re-locate X-min, Y-max, Z-max. This "X-form" did not take long to complete, almost instantaneously. I could pan, rotate and zoom the geometry OK, maybe a little bit jerky but not too bad.

My video card is pretty low end, I'm waiting for the warranty to end on this computer so I can purchase a higher watt PSU and a Nvidia Quadro 600. I don't know if this would help to work with this file or not? In other words it seems like my ECU and RAM should be good but the only lacking thing is the graphics card?

I attached a couple of screen caps of the system grinding away on the transformation and after it started responding again. It took probably 3 or 4 minutes to chew on it but it did come back with out having to restart SC.
Sorry I can't be more help,
Gerry

[tikka308]

Gerry - Thanks for giving it a go. Man, if its pokey on your computer, then I am hopeless on mine.

Since I don't really need all the detail in these parts - they are clamps which serve as fixtures and are being imported into Sprut only for collision purposes - I'll have to figure out how to reduce the number of faces. I guess the simplest way might be to recreate them as solid blocks (devoid of internal faces, chamfers, etc) - which is fine except it's an extra few steps...

[dbrija]

Originally Posted by tikka308 Gerry - Thanks for giving it a go. Man, if its pokey on your computer, then I am hopeless on mine. Since I don't really need all the detail in these parts - they are clamps which serve as fixtures and are being imported into Sprut only for collision purposes - I'll have to figure out how to reduce the number of faces. I guess the simplest way might be to recreate them as solid blocks (devoid of internal faces, chamfers, etc) - which is fine except it's an extra few steps...

I would eliminate the screws/threads. They are driving the face count. It crashes for me after I import it and started the transform dialog. Not sure why. That is on an i5 Core2 (8 cores), Radeon 6770 HD graphics, 8G Ram). Imported and scaled in 1 minute< for each operation. Trying on 1.6 build 47351

I tried it again on 47354 and it worked fine. Like others reported, it took a few minutes....

[Scott_M]

IF they are just for collision purpose then they are way too detailed as you concluded. I would sugggest opening your assembly and go to the sketch environment and just sketch the outline of each one, save the sketch and start a new part using that sketch and extrude the sketches. It should result in a pretty small file size. You don't need screws or chamfers or holes. Just properly positioned boundries.

I tried it on my gaming rig.
Win 7 Ultimate
Q6600 quad core @ 3.4 ghz with 4 gigs of ram
ATI HD 6950 with 2gb ram

Scott

[Scott_M]

something like this

attached, rename from .txt to .igs

Scott