-
Website
http://www.solidsmack.com/ -
Original page
http://www.solidsmack.com/upgrading-to-solidworks-2009-love-hate/2008-12-03/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
Charles Culp
34 comments · 2 points
-
Brian
51 comments · 9 points
-
MatthewWest
32 comments · 2 points
-
Bruce Buck
72 comments · 6 points
-
Dave Moore
49 comments · 1 points
-
-
Popular Threads
-
Friday Smackdown: Mechtronic Melee
1 day ago · 2 comments
-
Ask The Reader: Are You Upgrading to Windows 7? {Poll}
1 week ago · 21 comments
-
The Rockin’est LED PocketWatch Mod EVER, Designed With a lil’ SolidWorks
3 days ago · 4 comments
-
FreshFiber’s 3D Printed iPhone Case Puts the Fancy in Your Pants
2 days ago · 2 comments
-
Get Into SolidWorks World 2010 for Free. No Beet Throwing Required. #SWW10
5 days ago · 5 comments
-
Friday Smackdown: Mechtronic Melee
When you do upgrade, I'd test first. Install one license and go at it.
1. A lot of tools have regressed from not only 2008 to 2009, but from 2009sp0 to 2009sp1.
2. Roughly 200 to 300 drawings are now corrupt due to the upgrade. We are working with SolidWorks engineers to fix our drawings so that production can continue.
We have been informed that SP2 will fix all the issues we're having - but that's not for a couple of weeks away.
WAIT TIL SP2 IN DEC.
I want to design parts and assemblies. I don't want to test software nor discover and report bugs. I don't want to apply 5 (or more) Service Packs every year. I don't want a new version every 12 months.
Devon T. Sowell
http://www.3-ddesignsolutions.com
1) All our video cards are now obsolete
1a) Our budget doesn't leave me much room to fly low and replace them with decent cards.
$700 cards now being replaced by $200 cards, but at least they work
2) Immediately on installation, I am notified of a service pack, a rather large collection of patches. This
inspired my IT manager to offer to beat me about the head and shoulders if I asked again. Led me to
download them at home, which included both 32 and 64 bit patches.
What cards did you use before the upgrade?
/Dennis Hvam.
1. Right-click on desktop and Nviddia Control Panel
2. In 3D Setting, make sure 'let the 3D application decide'
3. RESTART your computer.
Changing it to this will allow SolidWorks to use DirectX instead of OpenGL. good luck.
From a budgetary standpoint, I've recommended consolidating hardware and software upgrades together and to set that as a cycle within the company. for video cards I recommend nVidia's FX line - 1700's are great, but you may seem some regression if put into an older system. All 10 of our engineers are running FX cards, and even the older 1400s have held up pretty well.
Does any of you use PDMWorks, if so have you experienced any problems or other upgrade related issues when using SolidWorks 2009 and PDMWorks?
/Dennis Hvam.
Utilized an admin image + network license and experienced little (if any) problems.
The biggest hassle was converting (library) files up to 2009 using the Task Scheduler.
After 10 years of SolidWorks upgrades, this one went smoother than expected. Not perfect, but better than expected.
The customer uses FX1300 video cards. They work decent but are looking to upgrade later this year.
Overall, the client is happy with 2009 so far. It's probably a combination of the new (2008) interface plus the new stuff in 2009. PhotoView 360 is a big hit. New enhancements in SolidWorks Enterprise PDM are well liked.
1. SolidWorks is fully capable of Nanotech.
2. SolidWorks is fully capable of Nanotech.
3. The IT department dislikes Dust.
4. prophet?
Now if I were a Solidworks Admin, I'd have them install it on my computer (if I couldn't do it myself). I'd gather results from testing and share that data with them, telling them we need to upgrade or wait until, such and such happens.
Except that when the new software is unusable, the engineering department is now telling IT to 'fix' it. Right now.
But we can't fix it right now, because the other 5 departments we support are all upgrading to the latest and greatest (read: beta, buggy) versions of their respective software packages.
The end result is a productivity loss across the board, which could've been avoided by doing a proper upgrade assessment before jumping in head first.
After our upgrade to SW 2009, which the Engineers requested, they are complaining that the network must have slowed down because the new Solid Works is SOOOO SLOW! Of course - it's the network.