【转帖】stability of v2008 vs v2009

yang686526

stability of v2008 vs v2009?
this might appear as a rant, but it's really a bit of research.  i've recently endured a change from v2007 to v2008 for a hand tool design--lots of surface work with fills, sweeps, lofts, etc.  i had some rather predictable bugs pop up when my assembly was in v2007.  my client had someone else working on a different model of hand tool, but he did it in v2008.  so i had to move to v2008, get up to speed instantly with the interface updates, and get cracking.  i have a way of modeling things that makes editing later a piece of cake--usually involving a master part with bodies split and then saved as separate parts at the end of the tree for detailing as separate parts later.  after seeing this other colleague's assembly for this tool (not that it was bad--just more difficult to edit/tweak forms later on), i decided to remodel the whole assembly, figuring it would be quicker.  (if using v2007, i'd have been correct--lots of later tweaks to handle curves and other geometry.)
i was instantly faced with a barrage of bugs.  my v2007 hand tool had a couple of consistent bugs in the feature tree (things like forgetting what surfaces were included in a trim), but these were always consistent, and i simply labeled which features would fail and fixed them as the edited part was rebuilt (roll back, fix along the way).  annoying, but no big deal.  my rebuilt v2008 hand tool has had many more critical failures, but this time they switch, depending on the edits i make upstream--no more predictability.  my problem with this is that the failures aren't the typical geometry corrections that are needed, but software bugs that have features that once worked fine failing flagrantly.  i cannot merely delete and redo the feature, since up to ten hours of downstream features would be lost if i did so.  so the feature problems must be (somehow) solved by keeping the same features.  this involves lots of surfaces, so most of the time i add in lots of patches/hacks/fixes rolled back before the failed feature to solve things.
here's the big question i've got:
for those who do modeling of this sort, are you seeing fewer bugs in v2009 than in v2008?  this is wasting huge amounts of my time and i've got to solve this issue--i have other projects that need my attention, and this current hand tool design is stuck in v2008 (i could have done it much better with v2007 and saved all this hassle--it simply handled surfaces much better with fewer bugs).  please let me know your experiences with the two versions and i'll push my client to allow an upgrade to v2009 if that's yielded better results.
  
jeff mowry
if you were re-doing the model anyway, why did you not do it in sw07 and just open it in sw08 when finished?

jeff,
this is a tough question. i saw problems with surfaces and composite curves when jumping from 07 to 09. i found going to 08, then 09 solved the problem in some respects, but didn't solve everything. i still have has some buggy issues, weird relationships, in context sketch stuff, and feature failures. i feel your pain.
my 2 cents in terms of 08 v 09 is that you should go to 09. it is 08 sp6 and more. sp2 on 09 is rocking. i've got my s key and rmb rocking, and am now moving faster than ever, when at times i was so reluctant to abandon my precious 07 and my fine tuned workflow. old habits are hard to break though. i've seen some major complaints about 09 on the sw forums though. speed was the complaint, when 09 was supposed to be so much faster, it was slower. and then everyone blames hardware. i haven't found this. i've crashed a few times hard on 09 with weird things like doing selections and clicking on the decal property manager.
also, do a test using the converision wizard of 08. bring the 07 into the conversion wizard without opening. then try and open the converted files in 08. is it the same results as opening the 07 files in 08 and then saving to update, and having the rebuild failures and feature issues?
my position is go to 09. then if on 09, do one more step and use the new convert files in the task scheduler to bring up these 08 ones, and test against just opening the 08 ones, rebuilding, and then saving. the one thing about the 09 conversion is that i couldn't keep it out of the toolbox, updating toolbox ref'd parts from previous versions, and also it was finding in context refs that i swear i broke.
hope you find a solution.
rfus
because i didn't know about these bugs at the time--i'd never used v2008 until then.  i was called on-site to this client's office, and v2008 is what they had installed.  i didn't originally anticipate remodeling the entire assembly either.  the original plan was to tweak the existing model, which, after reviewing the existing work, seemed more tenuous than simply remodeling everything for ease of editing quickly.
  
jeff mowry
thanks, rfus, i'll check this out.  (my previous reply was to corblimeylimey--i must be typing slowly today.)
i've never used the conversion wizard--i guess i have no faith in "wizards" anymore, and would rather have a hands-on approach to my model rebuilds in new versions.  your experience is that the conversion wizard does a good job with the updates?
  
jeff mowry
yes, it solved some issues in the way it is rewriting the files. use the file explorer to dump this design for test and all its refs to a place where you can test this, but i don't really need to tell you that. check the backup option too just in case, because this saved my 07 toolbox. i was able to grab all the backup toolbox parts and put them back in.
i will be eager to see if it does make any difference.
rfus
i've had very few parts fail the conversion wizard (less than a dozen) over 8 years and 1000's of files. however none of my files have the fancy swoopy-curves and surfaces that yours would have.
with your type of work i guess you rarely have to reuse files. i am often re-using old bits in new products so have little choice in converting.
if you ever have to go back and convert say a sw01 file to sw09, you would probably have far more problems.

so i can segregate which files the conversion wizard updates vs. not updates?  i won't use it without the ability to segregate my files exactly as i specify.  in this instance i would copy these files to a new directory and run the wizard only on the contents of that directory for testing.
during installation, did you specify software versions in the directories (such as "solidworks2008" instead of the stupid and destructive default of "solidworks")?  if so, you're still seeing the toolbox interference?  that's nuts.
  
jeff mowry
i had a major issue with the 09 conversion tool in the task scheduler (not previously there in 08). i said, update this assembly, where in the directory with the assembly it showed maybe 50 parts and subassems. but the creatinon of this was with hundereds of parts, sub assembs, blocks, in context refs, where at some times there were things like inserted parts, and then all kinds of toolbox parts. i put just the assembly into the conversion wizzard of 09, and hit go and sent it to a directory figuring it would update these 50 files and my 09 toolbox would be used when i opened the assem, but all of a sudden it says, converting 323 files. it even found refs that i had hidden, such as when you open an assembly and it cant find a ref, and then ask would you like to find yourself. i had no need to rebuild against it, so i consider it an unbroken/broken ref. how did it find these? i was like, if sw doesn't know where they were in the file refs, then how the heck did the task scheduler find them. i'd selected the backup option but spent half a day replacing this stuff i wasn't ready to bring up to 09 because it was used in other places in other designs that were in 07.
i figured out my best workflow for the migration. have the backup, and am now a happy camper on 09.
rfus
one more note.
i have 06, 07, 08, and 09 on here. all have their own toolbox, not default.
another thing i'm seeing is that my v2008 edrawings refuses to properly save my configurations.  i have certain parts hidden or shown per configuration, but edrawings will not save multiple configurations into an edrawing file properly--ever.  anyone else seeing this nonsense?
  
jeff mowry