I like restarting work as much as the next guy but eventually I need to finish things. Has anyone used other CAD software that was actually tested and works as advertised?
Assuming that your question or statement means that you don't like SW or you have issues with SW...
All software works as advertised, it's when we do things just a little different and combine those actions with another different method, that is when things start to go wacky..
Most of the (not all), but I'll repeat, most of all issues are user or equipment related. Most of the user issues are lack of training on what we want to do, or lack of design intent, how to proper use the software etc....
So fill in the blanks so we can help, till then there are ????'s
Perhaps share your hardware details (at least for entertainment value).
I like this answer. It's pretty much the correct one for the thread.
I just wanted opinions of people that have used other CAD software with better results.
I realize SW has its disciples monitoring the forums.
My HW specs:
250 GB SSD RAID 1
It's not nearly as amusing as the AutoDesk Cult, nor the Apple cult.
I'm afraid the days of getting stable and vetted releases of ANY software are long over. From Solidworks to any Office program, to even the underlying Operating Systems, we are now forever locked in a BETA version hell. As users there is little we can do about it, except perhaps not jumping to upgrade quite as often once you find a version combination that works well about 90% of the time. Unless you are willing to fork over $20K or more for Catia or Pro-E (or whatever they are calling it now), you aren't likely to get much better results - and even then, places like Boeing stay locked on old versions for the reasons I mentioned above. Good luck. Keep your drivers updated to the latest, don't willy-nilly allow Windows to do unnecessary updates, and pray.
The problem too is that there are nearly an infinite number of hardware variations so not all can be tested or vetted to work well. This makes it extremely aggravating when you encounter bugs that are not repeatable on the VAR's computers. Oh well. Like the Chinese curse says, "May you live in interesting times..."
At my last job, I worked side-by-side with another engineer who had identical hardware (purchased on same day from same vendor). He was plagued by hangs and crashes; I was not. We got new computers, and within a month of breaking-in it was the same story, my setup was markedly more stable.
I never figured out what the difference was.
OR it could be that he is using SW 2015! ..c'mon folks it's a terrible release...at least that's what the other thread says!
Yes. If so, he needs to get on SP 4.0 ASAP. We have noticed a few flaky things even with it. (Views on thumbnail going transparent, and it taking a long time to switch drawing sheets in an already created drawing). I'm sure there are others. Even our VAR can't figure out the slowness we encounter, so we get caught between the VAR suspecting the IT guys and the IT guys blaming the software, all while we twiddle our thumbs changing among drawing sheets....Oh well...
That's just it. What is his level of experience and how long has he been using Solidworks? Is he encountering things he didn't before when doing certain things (real bugs), or is he not using the software correctly for what he is trying to do (user error)? Has he looked through the forums to take note of certain Windows Updates causing issues (and how to fix that)? Has he contacted his VAR? Has he tried Solidworks Rx? And while he says he had to start over, he never really describes what issue it was that caused him to have to do that. So as one of the previous responders said, all we have are questions.
Define better results..... Define what you do and what you are having problems with....
All CAD software has it's problems.
Pick your poison. The grass is not always greener.
I had the same experience, only I was the one having the problems, colleagues did not experience any problems, or not that much.
Some of us are cursed. Using SW (whatever version), i experience crashes without any warning (just pop-ed away).
I can compare to NX and Creo, which crashes once every month or so, compared that to at least once a day with SW.
Working with 3DCAD for over 20 years, i think i know what i am talking about.
Those who preach for their own church, just dont know there is more on the other side, or just lucky.
I must say, I'm still using SW for quick and easy projects, but when going complex, SW is NOT the way to go.
By complex I mean (big assy's of freeform shapes).
Although SW15 sp05 seems much more stable, SW16 is NOT, just installed the SP01 we'll see.
I think SW is very dependent on hardware and drivers (also form third party), in combination with big assy's it is definitely UNSTABLE.
I think it's like driving, or even walking around traffic. After a years of doing it, you subconsciously develop the instincts to stay out of trouble. You stop thinking about it. On the other hand, children, or new drivers, are constantly making mistakes and getting into danger despite good faith efforts to follow all of the instructions they've been taught.
Rarely do I see SolidWorks crashes, whereas I saw them daily or better in the first five years of this century. Put it down to whatever you want.
Been a SW user for more than 15 years... the stability is getting worse. Open and shut case. Same high end hardware in use over a number of years.
It has gone from the odd crash to some times two or three a day since 2013. Sorry but my confidence in SW is declining rapidly
The most stable CAD package I've used has to be Siemens NX, but by God is it awful to use, the draughting side is laughable & feels like it belongs in the early 90s.
Autodesk Inventor is very comparable with SW, however they do seem keen to make as stable releases as possible & crashes are more dependent on hardware issues rather than software.
SW needs to concentrate on stability to win back customer trust, after the shambolic & shocking stability of 2015 they need to sort thing out.
Well stated Anna
There are a few Microsoft Windows updates that cause crashing issues, with some simple remedies to correct them. we're running several seats of SW2015 sp5 with very few issues.
I've used Pro/e and Creo, NX, Solid Edge and SolidWorks (refuse to capitalize the name) have to agree NX has been the most stable software I've used hands down. I've also supported NX, Solid Edge and SolidWorks for small, medium, large and global organizations and can say those NX and SE times were the best of times. NX Drafting is very powerful but the latest releases that required the UI to be updated (sound familiar) was not being accepted. This went so far that Product Manager held a special webinar to address all the complaints on the forum. In the end, the UI was functional and the users were not taking advantage/understanding how the old process in the old UI worked with the new. It was a relearning issue. Once that session was held, most of the users saw the power and accepted the changes. Chris, what version where you using?
SolidWorks has been my bane for some time now. The software this is the most finicky (based on drivers and mouse clicking) and the SW/DS doesn't appear to want to tackle some of the core bugs in the software that we all have to work around. Just saying that reminds me of most of the response from my VAR. "The work around is...."
@ Ryan -
I used NX7.5 & 8. I honestly found NX so hard to work with & difficult to achieve results; I'm not saying NX isnt powerful & can do great things, I'm saying its one of the least friendly CAD packages to use. One of my biggest bug bears is layers - you don't need layers in modern CAD packages, they are a throwback to the 90s when they had a purpose due to software limitations; but what makes things 100 time worse is the fact the layers of a part can be different for an assembly which in turn can be different in a drawing. (eg. Part1 can be on Layer10 in the part, Layer20 in the assembly & Layer30 in the drawing) which makes it almost impossible to work with someone else's assemblies/data if a lot of layers have been used.
Time for some new high end hardware?
Nope not at all in the cards. Box runs everything else flawlessly. 16 gig of DDR3-1866 ram, i7 3770K CPU @ 4.2 Ghz, SSD, Win7x64 pro OS, 2 gig Nvidia GPU.
I spoke a long time certified MS developer who suggested that it is time for DSS to stop using kids for program development who use non standard APIs and other programming short cuts to create "neat" code and adhere to "standards". That way we need not fear security updates or are we to forego such trivia as security for the benefit of DSS programmers.
Even running SW in administrator mode so it has elevated rights does not stop it from crapping out randomly on the simplest operations at times.
Easy for DSS to blame hardware and Microsoft updates. Sorry I don't buy that Kool-aide once a release has gone past SP-2 updates especially when my E-Cad, graphics and video editing programs run without randomly crashing. These programs are every bit as demanding as SW so by elimination the ball rests primarily with DSS programmers.
Don't get me wrong, I love the program and use it daily having moved up from Pro-E many years ago when Pro-E ran in a non Windows shell.
Wow, yes I would 100% agree that working on assy and part that use lots of layers is very 90's and would make working with NX very difficult! My question would be "Why would you or others use layers in NX that way?" That's a HUGE mistake. The software takes care of the visibility of objects types for you! The only place that users might still be using layers is in Drafting to separate titleblocks, from notes, from change revision symbols.
If you were attempting to use layers in assemblies to control visibility then someone is using the system incorrectly. Assemblies use "reference sets" and groups in conjunction with blank/unblank (hide/show) to control visibility. If you aren't using reference sets then you aren't using assemblies correctly- at all! When you work in-context (true in-context not like the SW in-context) you work directly on features and the entities you need either pop up show when you work on them- select a feature and choose between the parameters or sketch. If you choose the sketch then the sketch displays and then shuts off when you exit the sketcher. Now, if someone is way old-schooling and putting each sketch on a separate layer in the piece part instead of letting the software control the display then yes you will have visibility issues at the assembly level using in-context editing in the assy. Hence you use reference sets! That's is why they are critical to successful use of assemblies- not mention they control the amount of data (partial loading) that is opened when opening an assembly. You also need to understand the difference between hide/show and layers visible/invisible.
Anyway, all this is my helpdesk instincts kicking in!
Not so sure. Hardware development has seemed to slow the last few years. I mean we are still running i7 or Xeon processors and while graphics cards have gotten better with more bang for the buck, I don't see much difference between most 3 year old systems and the latest ones. Unless you are talking about using multiple processors to power through rendering and such, I don't think there is much of a speed increase in newer hardware. I hope Intel can prove me wrong - and soon. Most development lately has been to decrease power consumption and heat (not bad things), but those have nothing to do with raw speed. Then you have the issue of having rushed to market drivers on newer hardware that can cause instability issues and crashes, so to me it isn't worth living on the bleeding edge. Give me 2 year old hardware and a stable, predictable release on an operating system that doesn't get in the way. Is that too much to ask?
Been an Admin for 8 years... all I can say is 90% of issues with SW are GPU Driver related.... and 90% of users don't know what a GPU Driver is (or atleast care to updated)...
I'm using Solidworks since release 2010 and each release is getting worst year after year ... no matter which computer or windows version used, this is the crappiest software I've ever used "for work" but I'm still using it because our licence is still valid but I'm searching for alternatives too because I'm loosing arround 2-4 hours each week just in redoing stuff because of bugs or using workarrounds to avoid known bugs. Some of them are there since release 2012. And this is without mentionning all the RX that I've done that takes time too and seem to give nothing because the bugs are still there 4 years later.
Just this week I've spent arround 15 hours of my work time just to try to get the SP 0.1 to 2016 and even with the help of my VAR I've been unable to install it on any machine at work or on my portable computer ... and they keep telling me that my computers or windows are problematics ... so all my computers are craps ??? funny !!!! Before we bought Solidworks we've asked our VAR "what computer should we buy" and we do exactly what they want us to do and installed the windows they want us to install ... and they keep telling me "the problem is your computer or your windows" ... I'm trying all my best not to call them (VAR) when I have problems; It's just a waste of time because the problem is 90% of the time comming from SW so they don't have any power over it and they are opening a case ... this i can do alone, no need to pay for a subscription for that kind of help.
So here's my advices for the sales department of Solidworks if they want to stay on the grid:
1) Stop releasing new feature, I won't try them anyway the basics are already buggy so what will be the new stuff ... imagine!
2) Stop changing the colors, it's anoying
3) Stop changing the icons, it's useless
4) Fix what is actually in place and call it "SOLIDWORKS - Working edition"
What do I care about :
1) not loosing time at work to fix your software
2) working instead of debuggin your products ... we are not BETA tester
3) working with a software that IS "Professionnal Software"
With so much bug as 2015 has, this should be released as a Freeware because if I do the calculation of the money we throw in the trash to make it work and in debugging time with my VAR, this is more than the price of our licences; so in fact, they should had paid us to use it.
The only thing that keeps me from jumping to another software is my subscription that is ending in june so WAKE UP.
Retrieving data ...