Re: quantity of parts and features

Scott- feature statistics gives the number of features - its in the second line of text, right under the part name. 939 features in my current part. It also gives the total rebuild time, so I know how long I should take to go to the fridge and back (193 seconds)

Hmm,... I wonder,.. if you move the fridge closer, do the rebuild times increase??

(btw, my current master part: has ~500 features (6 solids now but will have 12 parts later, using insert part in parts, not split parts), ~60 seconds to rebuild)

.. ;^)

All be damn, I missed that.

Thanks Ed, Scott

Don't you mean decrease? I'm thinking about filling a bucket with ice that I can use to keep refreshing beverages at my feet so I can work really fast (or not care so much when things slow down)

Yeah, my part was pretty spry a couple of weeks ago. Don't get me wrong, Its not a dog at all - I'll be happy to take 3 minutes for a complete regen on this, especially since I always work with 'verficiation on rebuild' active (the model will speed up quite nicely if I don't have that on, but I have vowed never to take it in the ass on bad data again). BTW - This model has multi bodies, surfaces, lot of replace face and delete face (how did we ever work without those two?), in-context, configurations - you know, all the stuff that should cause tons of problems. And guess what - I get MAYBE one crash every 25-40 hours! SW2003, SP3.1 has been phenonenol for me! Its brought me back to the days of SW99, when you could really count on the software and it would deliver (with the exception below)

About the split parts - good move to avoid them. I'm currently taking notes and I'm hoping to post something authoritative when i get the chance, but in the short term it looks like there is no end to the number of ways you can mess the things up. Using the split feature to chop a model up WITHOUT exporting the bodies might be handy, but saving off the parts with the split command is looking to be scarier and scarier the more I explore it. On the other hand, inserted parts with the first feature dedicated to 'deleting bodies' has been bomb proof (when I get errors, they are instantly fixed and all of my data is intact). Thats been reassuring because I had to take my

900+ feature part, create four parts off of it and add a couple hundred features (plus in-context refs and configurations) to each of those.

Cheers (the rebuild is done)

-Ed

Paul, have you tried the 'RedLight' add-in for rebuilds?

Hey Ed,

Yep, decrease. (I'm using mailgate.org (on location contract) and I don't proof much using it.)

I know you wrote about the split part issue and I took note of it but when I've used it, it's pretty good. Although, I still lean towards insert part because of past methods and it still makes sense to me it should be this way (if they add sketches, better positioning, coordinated systems,..it will kickass).

And, I agree, the stability of sp3.1 has been impressive!

Otherwise, I have not had many problems except for the typical workarounds due to surface issues (problems with edges, extending edges, trimming in different orders (mutual trim limitations), copy-extend-offsets, edge degeneration (there seems to be tolerance issues again),.... it's driving me knuts)

The wierdiest thing that has happened recently is with insert part. This error showed up when the surface option was checked...

"Some resulting bodies cannot be identified from the saved information."

It went away after I did more work on the model (added features) it refered too but there is no way to track down what is was because I have to move forward, (I have no time to send the data so I sent the error message image and explained). There was nothing wrong with the model (no errors, ctrl-q'd) and in fact it's been stable since last year when I created the skins for the early layout, it's very clean.

..

Actually, I did and I'm sorry to say (sorry Philippe), for the way I work, that program created some odd hangs with my files and it slowed me down quite a bit.

The whole point of design driven software is for the model to update and I have to rebuild my models constaintly so the children have to update.

And, it crashed SW, so I removed it.

The program I thought was kind of kewl was "Spliner" but it also crashes my SW install (sorry again Philippe).

..

No problem Paul, but I can only correct bugs that are reported, so please tell me what went wrong and how. Nobody else reported SW crashes or hands with RedLight, I really want to know what happened! This is a real problem for me, and I guess for other SW partners : we do our best to make useful software, release it as shareware or even for free, but it is simply impossible to test it in production conditions, we need your help and feedback...

BTW, it was the old version, it was dated July 3rd. So, since it was the old version, I'm sure this whole issue is mute?