{"id":1988,"date":"2014-06-03T08:59:30","date_gmt":"2014-06-03T07:59:30","guid":{"rendered":"http:\/\/www.solidapps.co.uk\/blog\/?p=1988"},"modified":"2015-11-04T11:03:28","modified_gmt":"2015-11-04T11:03:28","slug":"solidworks-support-monthly-news-june-2014","status":"publish","type":"post","link":"https:\/\/www.solidapps.co.uk\/blog\/2014\/06\/solidworks-support-monthly-news-june-2014\/","title":{"rendered":"SOLIDWORKS Support Monthly News \u2013 June 2014"},"content":{"rendered":"<p>Welcome to this new edition of the SOLIDWORKS Support Monthly News, coauthored by members of the SOLIDWORKS Technical Support teams worldwide.<\/p>\n<h2>SOLIDWORKS 2015 Beta \u2013 looking back 10 years ago<\/h2>\n<p>We\u2019re still all anxiously waiting for the beginning of this year\u2019s Beta program (around the end of June) to discover and test all the new features in version 2015. Note that you can already <a href=\"http:\/\/www.solidworks.com\/beta\/beta-join.htm\" target=\"_blank\">sign up <\/a>to be able to test all the SOLIDWORKS 2015 products participating in the Beta Program.<\/p>\n<p>Meanwhile, let\u2019s continue our journey and look back again at what made the news ten years ago in the What\u2019s New pages of the documentation! After version 2004 (last month), here are excerpts from version 2005:<\/p>\n<p><strong>SOLIDWORKS<\/strong><\/p>\n<ul>\n<li>Icons on toolbar buttons and in the FeatureManager design tree now follow the Windows XP style:<img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3077 colorbox-3075\" src=\"http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Screen-capture22.png\" alt=\"Screen capture\" width=\"82\" height=\"79\" \/><\/li>\n<li>Cross select: when you box select from left to right, only items completely within the box are selected. Now you can cross select from right to left to select items crossing the box boundaries in addition yo items within the box.<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3078 colorbox-3075\" src=\"http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Screen-capture23.png\" alt=\"Screen capture\" width=\"553\" height=\"134\" \/><\/li>\n<li>Copy Settings wizard to distribute settings to other computers or save and restore them.<\/li>\n<li>Splines<\/li>\n<li>Many features moving from dialog boxes to PropertyManagers (Trim, Miror, Explode, etc.)<\/li>\n<li>Extrusion starting away from the sketch plane (from a surface, face, plane, vertex or offset)<\/li>\n<li>Assigned Mass Properties<\/li>\n<li>New SOLIDWORKS DWGEditor<\/li>\n<li>SOLIDWORKs animator now uses the Timeline interface<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"colorbox-3075\" src=\"http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Screen-capture24.png\" alt=\"Screen capture\" width=\"585\" height=\"179\" \/><\/li>\n<\/ul>\n<p><strong>\u00a0COSMOSWorks (the original name of SOLIDWORKS Simulation)<\/strong><\/p>\n<ul>\n<li>Studies are now associated with a configuration \u2013 So you now get an independent Mesh for Each Study. In earlier releases, studies shared one mesh represented by the Mesh icon in the tree<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-3081 colorbox-3075\" src=\"http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Screen-capture25.png\" alt=\"Screen capture\" width=\"432\" height=\"119\" \/><\/li>\n<li>New study types: Nonlinear, Drop-Test, Fatigue<\/li>\n<li>Multiprocessor Support for FFEPlus Solver<\/li>\n<\/ul>\n<h2>Spotlight on features \u2014 Sheet metal\u2013 Understanding the option: \u201cCreate multiple flat patterns whenever a feature creates multiple shm bodies\u201d<\/h2>\n<p>Under <strong>Tool<\/strong>, <strong>Options<\/strong>, <strong>Document Properties<\/strong>, <strong>Sheet Metal<\/strong>, there is the option\u00a0<strong>Create multiple flat patterns whenever a feature creates multiple shm bodies.<\/strong> This is one of those options that is a bit misunderstood. So lets clarify when it is supposed to work.<\/p>\n<p>&nbsp;<\/p>\n<table>\n<tbody>\n<tr valign=\"top\">\n<td>This option was implemented for those who work with multibody sheet metal and create certain specific operations. The user creates a sheet metal body with SOLIDWORKS 2011 or 2012, the feature tree will display one flat pattern feature<\/td>\n<td><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-2830 colorbox-3075\" src=\"http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Fig10.png\" alt=\"Fig10\" width=\"307\" height=\"291\" \/><\/td>\n<\/tr>\n<tr valign=\"top\">\n<td>The user cuts the single body in half, producing 2 bodies. Notice the feature tree still displays 1 flat pattern feature.<\/td>\n<td><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-2831 colorbox-3075\" src=\"http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Fig11.png\" alt=\"Fig11\" width=\"320\" height=\"322\" \/><\/td>\n<\/tr>\n<tr valign=\"top\">\n<td>The user checks this option. Now the feature tree displays 2 flat pattern features.<\/td>\n<td><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-2832 colorbox-3075\" src=\"http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Fig12.png\" alt=\"Fig12\" width=\"309\" height=\"350\" \/><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The other circumstance where this option works is when doing a body pattern. The user has the ability to display a single flat pattern (default) or multiple flat patterns.<\/p>\n<p>Be aware that this option will work only with parts created with SOLIDWORKS 2011 or 2012. Parts created after SOLIDWORKS 2012 will automatically display multiple flat pattern features.<\/p>\n<h2>Service Pack News<\/h2>\n<p>Service Pack 4.0 of version 2014 is planned for release this later month, with the Evaluation Version only a few days away.<\/p>\n<h2>Noteworthy Solutions from the SOLIDWORKS Knowledge Base<\/h2>\n<p><strong><b><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-408 colorbox-3075\" src=\"http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Screen-capture3.png\" alt=\"icon - SW\" width=\"16\" height=\"16\" \/><\/b> The assembly file is empty. When opening it in large design review mode, I can see the components but after resolving, it has lost all the parts and mates. How is that possible?<\/strong><br \/>\nThis result can be due to a user action rather than a software issue.<br \/>\nIn SolidWorks 2012 and previous releases, when selecting one or more components within a subassemblies and pressing delete, the result was that the subassembly was deleted from the top assembly.<br \/>\nRefer to the image below.<br \/>\n<a class=\"zoomLink cboxElement\" style=\"float: none;\" href=\"http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Screen-capture26.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-3174 colorbox-3075\" style=\"opacity: 1;\" src=\"http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Screen-capture26.png\" alt=\"Screen capture\" width=\"454\" height=\"284\" \/><\/a><br \/>\nSaving the top assembly did not produce any change on the subassembly file itself.<br \/>\nFrom SolidWorks 2013, when selecting one or more components within a subassemblies and pressing delete, the result is that the components are deleted from the subassembly.<br \/>\nRefer to the image below.<br \/>\n<a class=\"zoomLink cboxElement\" style=\"float: none;\" href=\"http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Screen-capture27.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-3175 colorbox-3075\" style=\"opacity: 1;\" src=\"http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Screen-capture27.png\" alt=\"Screen capture\" width=\"456\" height=\"286\" \/><\/a><br \/>\nSaving the top assembly, the subassembly is also saved without the deleted parts.<br \/>\nSee the final result below.<br \/>\n<a class=\"zoomLink cboxElement\" style=\"float: none;\" href=\"http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Screen-capture28.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-3176 colorbox-3075\" style=\"opacity: 1;\" src=\"http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Screen-capture28.png\" alt=\"Screen capture\" width=\"459\" height=\"288\" \/><\/a><br \/>\nPlease be aware of this changed behaviour to avoid unexpected results.<br \/>\nFrom Solution ID: <a href=\"https:\/\/customerportal.solidworks.com\/eservice_enu\/start.swe?SWECmd=GotoView&amp;SWEView=SW+KBase+Solution+View+(eService)&amp;SWERF=1&amp;SWEBU=1&amp;SWEApplet0=SW+KBase+Solution+Form+Applet+(eService)&amp;SWERowId0=1-2LEDW0U\" target=\"_blank\">S-066007<\/a><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-410 colorbox-3075\" src=\"http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Screen-capture4.png\" alt=\"icon - Simulation\" width=\"16\" height=\"16\" \/> <strong>Is there a hotfix available for SPR 781081 (crash in SOLIDWORKS 2014 SP3 when changing units in the SOLIDWORKS Simulation Force dialog)?<\/strong><br \/>\nYes, the SOLIDWORKS Simulation 2014 SP3 hotfix for this SPR is provided in the form of a single .exe file in the Attachments section of this Solution. This hotfix will address the issue mentioned in SPR 781081.<br \/>\nPlease refer to Solution ID: <a href=\"https:\/\/customerportal.solidworks.com\/eservice_enu\/start.swe?SWECmd=GotoView&amp;SWEView=SW+KBase+Solution+View+(eService)&amp;SWERF=1&amp;SWEBU=1&amp;SWEApplet0=SW+KBase+Solution+Form+Applet+(eService)&amp;SWERowId0=1-2LIEMNX\" target=\"_blank\">S-066018<\/a>.<\/p>\n<p><strong><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-405 colorbox-3075\" src=\"http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Screen-capture1.png\" alt=\"Icon - EPDM\" width=\"16\" height=\"16\" \/> What are the recommended changes to the Enterprise PDM 2012, 2013 and 2014 convert task script under advanced scripting options in order to avoid empty drawing model views in the converted output file (PDF, eDrawings\u00ae etc.)?<\/strong><br \/>\nIf the SolidWorks drawing that is being processed by the Enterprise PDM convert task contains multiple inactive sheets that require updating and the convert task executes when the SolidWorks session is minimized or runs in the background on the task host, it is possible that views in the inactive sheets could end up missing geometry and content in the converted output file.<br \/>\nPlease refer to Solution ID: <a href=\"https:\/\/customerportal.solidworks.com\/eservice_enu\/start.swe?SWECmd=GotoView&amp;SWEView=SW+KBase+Solution+View+(eService)&amp;SWERF=1&amp;SWEBU=1&amp;SWEApplet0=SW+KBase+Solution+Form+Applet+(eService)&amp;SWERowId0=1-2J8H28R\" target=\"_blank\">S-065824<\/a> for more information about how to avoid and solve this problem.<\/p>\n<p style=\"text-align: center;\">&#8211; \u2013 &#8211; = = = o o O o o = = = \u2013 &#8211; &#8211;<\/p>\n<p>That\u2019s it for this month. Thanks for reading this edition of SOLIDWORKS Support News.<\/p>\n<p>Originally posted by Julien Boissat in the <a href=\"http:\/\/blogs.solidworks.com\/tech\/2014\/06\/solidworks-support-monthly-news-june-2014.html\" target=\"_blank\">SOLIDWORKS Tech Blog<\/a><\/p>\n<p><a href=\"http:\/\/mkt.solidworks.com\/emarketing_enu\/start.swe?SWECmd=InvokeMethod&amp;SWEMethod=StartSS&amp;SWEView=URLRouter&amp;SWEApplet=SSRoute&amp;SWENargs=SSId=1-2LPZ7NU,SSName=REP+ENG-INTL+SW+Inspection+First+Look,SSLC=,SSCC=,CID=1-2MR2O6Z,OID=1-2LPWVYS,COID=1-2MR2O70,PRO=1-NKZ7N\" target=\"_blank\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-1962\" src=\"http:\/\/www.solidapps.co.uk\/blog\/wp-content\/uploads\/REP_SW_Inspection-First-Look_600x90.jpg\" alt=\"REP_SW_Inspection-First-Look_600x90\" width=\"600\" height=\"90\" srcset=\"https:\/\/www.solidapps.co.uk\/blog\/wp-content\/uploads\/REP_SW_Inspection-First-Look_600x90.jpg 600w, https:\/\/www.solidapps.co.uk\/blog\/wp-content\/uploads\/REP_SW_Inspection-First-Look_600x90-300x45.jpg 300w\" sizes=\"auto, (max-width: 600px) 100vw, 600px\" \/><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Welcome to this new edition of the SOLIDWORKS Support Monthly News, coauthored by members of the SOLIDWORKS Technical Support teams worldwide. SOLIDWORKS 2015 Beta \u2013 looking back 10 years ago&hellip; <\/p>\n","protected":false},"author":1,"featured_media":798,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[25,26],"class_list":["post-1988","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-solidworks","tag-solidworks-2","tag-support"],"post_mailing_queue_ids":[],"_links":{"self":[{"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/posts\/1988","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/comments?post=1988"}],"version-history":[{"count":3,"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/posts\/1988\/revisions"}],"predecessor-version":[{"id":3781,"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/posts\/1988\/revisions\/3781"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/media\/798"}],"wp:attachment":[{"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/media?parent=1988"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/categories?post=1988"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/tags?post=1988"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}