yang686526

assembly rebuild times
hello again, boys and girls. i was just wondering if there is a way to check the rebuild times on an assembly. in a part you can check the feature statistics, but there isn't an option for assemblies. assemblyexpert just tells you the number and type of parts. maybe someone has a macro?
dan
don't you have a stopwatch?
jeff mirisola, cswp, certified driveworks ae
my guess is that rebuild times for an assembly would be sort of difficult to calculate. solving mates, with their potential for circular tanglements, probably means that the rebuild time depends on what you changed. also, it depends on how many components/subassemblies have to be rebuilt for the assembly to rebuild.
just shooting from the hip, though.
-handleman, cswp (the new, easy test)
right, but the same can be said for parts. i mean, if you hit the "recalculate" button on feature statistics you'll get a different rebuild time even if you don't change anything. just looking for something similar in assys.
dan
i got pointed to a macro on fcsuper's site that will work.
a macro listing the individual rebuild times of components in an assy has been requested several times before. it would be a very useful tool when trying to discover which component in an assy is causing a long save-time.

so... which do you want, individual component save times or rebuild times? when you have an assembly open, sw keeps track of which components of the assembly have been modified. if a component doesn't get modified, it doesn't get re-saved when you save the assembly. the same logic is applied for rebuilds - when you rebuild the top level assembly (even ctrl-q) it only rebuilds components that sw determines require rebuilding. there is a sort of "super ctrl-q" available in the api that force-rebuilds all the referenced documents as well.
-handleman, cswp (the new, easy test)
this macro will force-rebuild each referenced configuration of each part file in the active assembly. suppressed and lightweight components are ignored. it starts at the deepest level of the assembly and force-rebuilds all referenced configs of all documents at that level. it then goes up one level at a time and force rebuilds again. each subassembly at this level should contain fully rebuilt components, so only the current level is force-rebuilt. there is an option to force-rebuild twice in a row if desired.
i never use the "in use" configuration setting for any assembly components, but if you do i think this macro will likely change that.
the macro keeps track of which configs of which parts have already been rebuilt, so no config gets rebuilt twice, even if it's on a different level.
there is also an option to save the components (after rebuild) and report the save time.
the results of the rebuild/save are presented in excel format.
-handleman, cswp (the new, easy test)
not sure if anyone's tried this one yet, but i thought it might be handy to go ahead and report the file size of each component as well.
i also turned screen updating back on in excel. turning it off doesn't make it run a whole lot faster, and with it off it sort of looks like it's not doing anything.

-handleman, cswp (the new, easy test)
handleman,
i hadn't got around to testing the first one, but that last one is excellent. it will really help (and already has) when trying to find out why an assy is taking so long to save.
thank you.

handleman
very nice - as usual .
thanks
tobin sparks