2 Replies Latest reply on Jun 13, 2014 5:10 PM by John Burrill

    SolidWorks 2013 Serious Issues

    Thomas Huggins

      After much frustration and banging my head on the desk for months, I finally decided to post about the issues with SolidWorks 2013 that we suffer from on a daily basis.  I've been a SolidWorks user since 2004 and have loved it from the beginning..... until now.  All I can say is that I hope these issues were addressed and fixed in the 2014 version or my company will be switching to a reliable 3D platform.  Dassault really needs to issue a final SP for those of us still using 2013.  It's like buyng a car only to find that they forgot to put wheels on it.  It sure is pretty though.  I'm not here to flame the forum, I just want SolidWorks to know that we aren't happy at all.  See below for a list some of the issues that we are experiencing.


      *Converted sketches losing driving sketch relations.

      *EPDM 2013 does not "get latest" when checking out, (that variable is our default).

      *Constant crashes, (I've had as many as 11 in one day).

      *Drawing views linked to BOM continually lose their link.

      *Configurations not staying in their saved state.

      *Revolve feature changes the driving sketch.

      *Crashes in large assy mode.

      *Crashes on closing, even when nothing is open.

      *Random script error messages, even when nothing is open.

      *Random yellow triangle messages that tell nothing.

      *Changes in one sketch causes over constrained errors in other sketches.


      That's what comes to mind at the moment, because these happen every day, but there are more.  Thanks for letting me share and feel free to add issues that you may be having with 2013. -TH

        • Re: SolidWorks 2013 Serious Issues
          Brad Williamson

          Hi Thomas,

          I'm sorry to hear you're experiencing some technical issues that are slowing you down.

          There are a lot of things listed here, but I'd like to get someone to help you get to the bottom of them.


          Please email me privately with your updated contact information, and I'll get the right people in touch with you promptly.



          Brad Williamson

          Territory Technical Manager, South US



          • Re: SolidWorks 2013 Serious Issues
            John Burrill

            Thomas, I partially sympathise because I've been in situations where crashing, fickle behavior and broken relations have slowed me down and stressed me out.

            On the other hand, I know from first hand knowledge that the frequency of these errors derives from three things: machine configuration, file access and inaccurate expectations.

            For the first issue, buy a computer from a quality vendor with a 64bit professional OS, a good ammount of RAM and a certified video card-and then immediately wipe it and reload the OS because those factory images are crud.  Use a virus scanner tested for compatibility and stay away from system ghosting, raid 1, employee monitoring and registry optimizing applications.  Use the certified video card drivers and disable the nvidia and ATI window management tools.

            Second, the safest course of action is to use a PDM system that provides local file access.  If you move files onto the network, then it's on you to make sure there is enough bandwidth for SolidWorks frequent, loading and reloading of data from those files.  One network collision can cause SolidWorks to throw an access control list error and bring about the dreaded 'failed to save' message.

            Finaly, solidworks loses relationships (mates and geometry relations) when model topology changes and when projected and intersection curves change type (ie from circle too ellipse or from 2 point spline to parabola).  On Edge relations are pretty robust as long as the angle between the sketch plane and the object you're converting doesn't change.  Intersection curve relations are very touchy and can't be repaired, once broken.  For that reason, use intersection curves very sparingly and avoid adding sketch relations to their endponits, instead using pierce relations to the edges that bound the intersected surface and don't trim these curves to other sketch geometry if you can avoid it.

            With mates, the main reasons they'll fail on rebuild are flexible subassemblies and limit mates whose degrees of freedom produce unsolveable relations.  In these cases, suppressing and unsuppressing the mates usually puts them to rights.  Sometimes just doing another rebuild fixes these errors-especially when multiple assembly configurations are involved.  In cases where mate references go missing, the cause for this is usually failure to take ownership of a file before editing it and failure to check into the vault a modified referenced document.

            That's not going to eliminate all of the issues, but getting a handle on those factors usually makes them rare occurences.