ANSYS, Inc. Known Issues and Limitations PDF

Known Issues and Limitations
ANSYS, Inc. Release 16.0

Southpointe January 2015
2600 ANSYS Drive ANSYS, Inc. is
Canonsburg, PA 15317 certified to ISO
9001:2008.
ansysinfo@ansys.com
http://www.ansys.com
(T) 724-746-3304
(F) 724-514-9494
Copyright and Trademark Information
2014-2015 SAS IP, Inc. All rights reserved. Unauthorized use, distribution or duplication is prohibited.
ANSYS, ANSYS Workbench, Ansoft, AUTODYN, EKM, Engineering Knowledge Manager, CFX, FLUENT, HFSS, AIM
and any and all ANSYS, Inc. brand, product, service and feature names, logos and slogans are registered trademarks
or trademarks of ANSYS, Inc. or its subsidiaries in the United States or other countries. ICEM CFD is a trademark
used by ANSYS, Inc. under license. CFX is a trademark of Sony Corporation in Japan. All other brand, product,
service and feature names or trademarks are the property of their respective owners.
Disclaimer Notice
THIS ANSYS SOFTWARE PRODUCT AND PROGRAM DOCUMENTATION INCLUDE TRADE SECRETS AND ARE CONFID-
ENTIAL AND PROPRIETARY PRODUCTS OF ANSYS, INC., ITS SUBSIDIARIES, OR LICENSORS. The software products
and documentation are furnished by ANSYS, Inc., its subsidiaries, or affiliates under a software license agreement
that contains provisions concerning non-disclosure, copying, length and nature of use, compliance with exporting
laws, warranties, disclaimers, limitations of liability, and remedies, and other provisions. The software products
and documentation may be used, disclosed, transferred, or copied only in accordance with the terms and conditions
of that software license agreement.
ANSYS, Inc. is certified to ISO 9001:2008.
U.S. Government Rights
For U.S. Government users, except as specifically granted by the ANSYS, Inc. software license agreement, the use,
duplication, or disclosure by the United States Government is subject to restrictions stated in the ANSYS, Inc.
software license agreement and FAR 12.212 (for non-DOD licenses).
Third-Party Software
See the legal information in the product help files for the complete Legal Notice for ANSYS proprietary software
and third-party software. If you are unable to access the Legal Notice, please contact ANSYS, Inc.
Published in the U.S.A.

Table of Contents
Introduction ................................................................................................................................................. v
1. Installation .............................................................................................................................................. 1
2. Licensing ................................................................................................................................................. 3
3. Platform Support .................................................................................................................................... 5
4. Documentation ....................................................................................................................................... 7
5. Advisories .............................................................................................................................................. 15
6. ANSYS Structural Products ................................................................................................................... 17
6.1. Mechanical ..................................................................................................................................... 17
6.2. Mechanical APDL ............................................................................................................................ 17
6.3. Autodyn ......................................................................................................................................... 17
6.4. Aqwa .............................................................................................................................................. 17
6.5. Beamcheck ..................................................................................................................................... 18
6.6. Fatjack ............................................................................................................................................ 18
6.7. ANSYS Composite PrepPost (ACP) ................................................................................................... 18
7. ANSYS Fluids Products .......................................................................................................................... 19
7.1. Fluent ............................................................................................................................................. 19
7.2. CFX ................................................................................................................................................ 19
7.3. TurboGrid ....................................................................................................................................... 19
7.4. BladeModeler ................................................................................................................................. 20
7.5. CFD-Post ........................................................................................................................................ 20
7.6. Polyflow ......................................................................................................................................... 20
8. ANSYS Electronics Products .................................................................................................................. 21
8.1. Icepak ............................................................................................................................................ 21
9. ANSYS Geometry & Mesh Prep Products .............................................................................................. 23
9.1. CAD Connections & Integration ....................................................................................................... 23
9.2. DesignModeler ............................................................................................................................... 23
9.3. Meshing ......................................................................................................................................... 23
9.4. IC Engine ........................................................................................................................................ 23
9.5. ICEM CFD ........................................................................................................................................ 23
9.6. Fluent Meshing ............................................................................................................................... 23
10. ANSYS Simulation Products ................................................................................................................ 25
10.1. Workbench ................................................................................................................................... 25
10.2. EKM .............................................................................................................................................. 25
10.3. DesignXplorer ............................................................................................................................... 26
11. ANSYS AIM .......................................................................................................................................... 29
Release 16.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. iii
iv of ANSYS, Inc. and its subsidiaries and affiliates.
Introduction
The following information is relevant to ANSYS, Inc. Release 16.0. The entries describe known non-op-
erational behavior, an error, or limitation at the time of this release. Work-arounds for these items, if
available, are included in the respective descriptions. Inclusion in this document does not imply the issues
and limitations are applicable to future releases.
The parenthetical numbers associated with each entry are reference numbers corresponding to an in-
ternal error tracking system. The numbers are included to help to facilitate ANSYS, Inc. technical support
and help to ensure that the issue described in the entry is resolved.
Service packs may become available for some of the entries. See the ANSYS Customer Portal for inform-
ation about service packs and any additional items not included in this document. First-time users of
the customer portal must register via the ANSYS Web site (www.ansys.com) to create a password.
Additional known issues and limitations may be found in the product Help and/or release notes, both
accessible via the ANSYS Help Viewer within the product.
of ANSYS, Inc. and its subsidiaries and affiliates. v
vi of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 1: Installation
Use of Ultra High Definition (4K) graphics cards cause a number of cosmetic display issues (including
enlarged or reduced text and incorrect positioning of option labels). These issues do not affect the
functionality of the installation program. (96777)
Uninstalling Release 16.0 on the Linux platform may result in the following files remaining installed:
/ansys_inc/root/ansys_inc/v160/aisol/.wbconfig160
/ansys_inc/v160/aisol/ans_admin160
/ansys_inc/v160/aisol/wbhelp160
Work-around: Delete the files manually. (98568)
SpaceClaim Products Installed Prior to Workbench 16.0 Installation

ANSYS SpaceClaim Direct Modeler will not be configured during installation of Workbench if a previous
installed version of SpaceClaim Direct Modeler or SpaceClaim Engineer is detected.
If desired, ANSYS SpaceClaim Direct Modeler can be configured manually, following the removal of
previously installed versions.
To configure manually, execute the AnsConfigSpaceClaim.exe from the following ANSYS installation
location: <INSTALL_PATH>\common files\configs\winx64\config\
SpaceClaim Direct Modeler Configuration

The 16.0 version of SpaceClaim Direct Modeler is not compatible with Workbench versions prior to 15.0.
Use of SpaceClaim Direct Modeler with Workbench versions prior to 15.0 requires SpaceClaim Direct
Modeler 2014 SP2.
Installing SpaceClaim products released prior to Workbench 16.0 is not supported. Doing so will result
in unexpected behaviors. The 16.0 version of SpaceClaim Direct Modeler can be disabled to allow prior
versions of SpaceClaim products to assume the linked connection to Workbench by executing AnsUn-
configSpaceClaim.exe from the following ANSYS installation location: <INSTALL_PATH>\common
files\configs\winx64\unconfig\
Note
Once the 16.0 version of ANSYS SpaceClaim Direct Modeler has been unconfigured, prior
SpaceClaim product versions can be installed/re-installed.
Note
All SpaceClaim Engineering products released with or after Workbench 16.0 have modified
their installations to automatically unconfigure the 16.0 version of ANSYS SpaceClaim Direct
Modeler if it is detected.
of ANSYS, Inc. and its subsidiaries and affiliates. 1
2 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 2: Licensing
No known issues, limitations, or documentation inaccuracies.
Chapter 3: Platform Support
Chapter 4: Documentation
Legal Notice
The following update should appear in the Third-Party Software section:
Perl, http://dev.perl.org/ is licensed under The GNU General Public License (GPL) Version 2
June 1991 Copyright 1989, 1991 Free Software Foundation, Inc. 59 Temple Place, Suite 330,
Boston, MA 02111-1307 USA
ANSYS, Inc. will provide you with a complete machine-readable copy of the source code, valid
for three years. The source code can be obtained by contacting ANSYS, Inc. at
open.source@ansys.com.
Everyone is permitted to copy and distribute verbatim copies of this license document, but
changing it is not allowed. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS
NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT
WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PER-
FORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU
ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
Within the Legal Notices section of the ANSYS Help, see GNU GENERAL PUBLIC LICENSE
(GPL) for a complete listing of the GNU GENERAL PUBLIC LICENSE.
(97306)
CAD Integration
The Geometry Interface Support table for Windows should include an entry for SolidWorks 2015 in the
Plugs-Ins/Pseudo-Reader section showing support on the Windows 7 and Windows 8.1 operating systems.
EKM
In 6.2. Specifying General Server Settings in the EKM Administration Guide, a note for the jobSource-
RootPath, dataManagementJreLocation, and dataManagementJarLocation settings says: It is highly re-
commended that you use a UNC path, not a mapped drive, when specifying this value. This note should
be further clarified as follows:
In Windows, if the folder is on a remote machine, it is highly recommended that you use
a UNC path, not a mapped drive, when specifying this value.
(97872)
In Appendix A. Java Security Manager and EKM Scripting in the EKM Administration Guide, the fol-
lowing note about cluster installs should be added:
Documentation
The default script.policy is intended for use in a non-clustered setup. In a clustered setup, you
will need to update the path to the tmp directory as shown below. Otherwise, executing
macros and performing actions such as Share Query may result in an error.
As an example, if the primary node is named node1:
Instead of granting read/write access to the tmp directory as follows:
permission java.io.FilePermission "${jboss.home.dir}/standalone/tmp/-", "read";
You might update the path as follows:
permission java.io.FilePermission "${jboss.home.dir}/domain/servers/node1/tmp/-", "read";
(98065, 97975)
In the EKM Administration Guide, in sections 5.1.2. Applying the Configuration, 5.1.3. Reverting to a
Previous Configuration and 5.1.4. Accepting the Configuration, the File > Workspace Configuration
menu should be replaced with the Configure menu. (98279)
In the EKM Installation Guide, in sections 10.1.1.1. Configuring Standard LDAP Authentication, 10.1.1.2.
Configuring Proxy-based LDAP Authentication, and 10.1.2. Authenticating EKM Logins to Windows
Active Directory, a step should be added to comment out the existing login module (WindowsLogin-
Module or LinuxLoginModule). Also, the following line should be commented out in the JBoss config-
uration file snippet:
<login-module xmlns="" code="waffle.jaas.WindowsLoginModule"

flag="requisite" />
(98494)
Fluent
At Fluent Release Notes> New Features in ANSYS Fluent 16.0> Models> Combustion and Species
Transport, the following statement:
Fluent now includes the Chemkin reaction library. No separate license is required.
should read like so:
Fluent now includes the CHEMKIN-CFD for Fluent reaction library. No separate license is required.
This also yields improved performance.
Mechanical
The following incorrect statements were made in the section, ANSYS Documentation>Mechanical Ap-
plications>Mechanical Users Guide>Objects Reference>Mesh.
Under Mesh> Object Properties, the following Category was omitted: Patch Independent Options, To-
pology Checking
Under Mesh >Mesh Connection Group:
A Mesh object is not a parent of the Mesh Connection Group object.
Under Mesh >Mesh Connection Group, the following statement is incorrect:
Face Angle Tolerance: for faces that will be excluded from the proximity detection pair, this
property defines the minimum angle between the faces above which the two face pairs will
be ignored from proximity detection. The default value is 70.
The statement should be corrected as follows:
property defines the minimum angle between the master face and slave edge entity above
which the two face pairs will be ignored from proximity detection. The default value is 70.
Under Mesh> Mesh Connection Group, the following statement is incorrect:
Group By: options include None (default) and Faces.

The statement should be corrected as follows:
Group By: options include None and Faces (default).
Under Mesh> Mesh Connection:
A Mesh object is not a parent of the Mesh Connection object.
Meshing
The following incorrect statement appears in the section ANSYS, Inc. Release Notes > IV. ANSYS Geometry
& Mesh Prep Products>4.7 Meshing Mesh Control Enhancements:
The Use Fixed Size Function for Sheets option enables you to use the Fixed Size function while
you are using Proximity Size functions to refine the mesh for the rest of the model.
Use Fixed Size Function for Sheets enables you to refine the mesh for sheet geometries using
the Fixed Size function while you are using Proximity Size functions to refine the mesh for the
rest of the model.
This statement should be corrected as follows:
The Use Fixed Size Function for Sheets option enables you to use the Fixed Size func-
tion while you are using Proximity Size and/or Curvature functions to refine the mesh for
the rest of the model. (97987)
At ANSYS Documentation > Meshing Users Guide > Global Mesh Controls>Sizing Group>Use Advanced
Size Function>Specifying Size Function Options>Use Fixed Size Function for Sheets, the following
paragraph does not mention the body types for which the Use Fixed Function for Sheets option is
available:
Use Fixed Size Function for Sheets enables you to use the Fixed Size function while you are
using other Size functions to refine the mesh for the rest of the model. This setting is available
when the Use Advanced Size Function is set to On: Proximity and Curvature, On: Proximity,
and On: Curvature. The default for this setting is No.
The paragraph should be read as follows:
Use Fixed Size Function for Sheets enables you to use the Fixed Size function while you are
using other Size functions to refine the mesh for the rest of the model. This setting is available
only when the model contains mixed body types (for example, sheet and solid bodies), and
when the Use Advanced Size Function is set to On: Proximity and Curvature, On: Proximity,
and On: Curvature. The default for this setting is No. (97987)
The following incorrect statements appear in the section ANSYS Documentation > Meshing Users Guide
> Miscellaneous Tools > Mesh Editing > Mesh Connections.
Under Scoping, the statement:
Connections are made edge-to-face or face to vertex;

Should be corrected as follows:
Documentation
Connections are made edge-to-face or vertex-to-face;
Under Application, the statement:
The automatic mesh connections feature is very helpful, but it can also find and create con-
nections that you may not want. Always review the connections, or at least be aware that if
problems arise, they may be due to automatically generated mesh connections.
The automatic mesh connections feature is very helpful, but it can only detect edge-to-face
connections. If you need to define edge-to-edge connections, you will need to define them
manually. The feature can also find and create connections that you may not want. Always
review the connections, or at least be aware that if problems arise, they may be due to
automatically generated mesh connections.
Under Common Imprints and Mesh Connections, the paragraph:
The tolerance for common imprints comes from the minimum element size in the footprint
mesh, which is the horizontal plate in the example below. Common imprints are made if the
gap between imprints is smaller than or equal to the minimum element size in the connection
region. For this reason, setting the mesh size appropriately is important to control whether
the imprints will be common or not.
The tolerance for common imprints comes from the minimum element size in the footprint
mesh, which is the horizontal plate in the example below. Common imprints are made if the
gap between imprints is smaller than or equal to 5 percent of the element size in the connec-
tion region. For this reason, setting the mesh size appropriately is important to control
whether the imprints will be common or not.
Under Diagnosing Failed Mesh Connections, the process for detecting General Failures should be
described as follows: In the event of a general mesh connection failure, the following approach is re-
commended:
1. Select an ignored or failed mesh connections shown in the tree and look at Control Messages in
the Details View.
2. Note: You can use the Filter to identify Mesh Connection objects that are State>Ignored. Mesh
Connections that are in the Error state can not be filtered and wont be shown.
3. Click Yes, Click to Display to display related error messages.
4. Right-click on the error messages:
a. If a message provides Problematic Geometry information:
i. Select the message, right-click, and select Show Problematic Geometry from the context
menu.
This action highlights the geometry in the Geometry window that is responsible for
the message.
ii. Note: Any error message that is related to a specific mesh connection will be associated with
the slave geometry in the connection.
iii. Select the problematic bodies, right-click, and select Go To > Mesh Connections for Selected
Bodies.
This action highlights all mesh connections attached to the problematic geometry.
iv. Review the tolerances and mesh sizes associated with the highlighted connections.
b. If a message provides Go to Body information:
i. Select the message, right-click, and select Go to Body from the context menu. This action
highlights selects the object in the Details view that is responsible for the message.
ii. Review the tolerances and mesh sizes associated with the highlighted body or bodies.
Under Points to Remember, the following points are no longer applicable:
Toggling suppression of mesh connections or changing their properties causes bodies affected by
those mesh connections to have an unmeshed state. However, when you subsequently select Connect
Mesh, only the connections will be regenerated. Since mesh connections are a post mesh process,
a re-mesh is not necessary and will not occur.
Mesh connections cannot be generated incrementally. Anytime you add or change mesh connections
and select Connect Mesh, processing starts with the mesh in its unconnected (pre-joined) state and
then re-connects the entire assembly. This approach is necessary as mesh connections often have
interdependencies which can have a ripple effect through the assembly of parts. It is often the case
that a connection must be reevaluated across the assembly as a single connection may invalidate
many.
After model assembly, you cannot generate new mesh connections in a mesh that already has mesh
connections. Mesh connections only work with a model assembly if the mesh is unconnected in the
upstream systems. Because the base meshes from the upstream systems are not available to the as-
sembled model, you must regenerate the mesh to use mesh connections.
(97987)
The following statements appear in the section ANSYS Documentation> Meshing Users Guide> Miscel-
laneous Tools> Mesh Editing> Node Merge.
Under Requirements, the paragraph:
For a node merge to be successful, the mesh needs to be of similar size, and the number
of mesh nodes to be merged on both topology entities need to be equal. If they are
not equal, there may be holes in the mesh.
The paragraph should be read as follows:
For a node merge to be successful, the mesh needs to be of similar size, and the number of
mesh nodes to be merged on both topology entities need to be equal. If nodes on the
master and slave don't have a 1-1 correspondence, then the resulting mesh after node merge
can have holes.
Under Application, the paragraph:
Node merge operation supports two methods for connecting the mesh: Automatic and Manual.
They both work similarly, with the exception that in manual node merge the connection
objects are explicitly populated in the tree, but are hidden in automatic mode. Automatic
node merge is very useful when working on very large assemblies, as large number of node
Documentation
merge objects can slow down performance. Manual node merge, however, allows you to
review individual connections in detail.
Should read as follows:
Node merge operation supports two methods for connecting the mesh: Automatic and Manual.
They both work similarly, with the exception that in manual node merge the node merge
objects are explicitly populated in the tree, but are hidden in automatic mode. Automatic
node merge is very useful when working on very large assemblies, as large number of node
merge objects can slow down performance. Manual node merge, however, allows you to
review individual node merge objects in detail.
Step 5 of the instructions to automatically apply node merges begins:
5. Optionally, modify the Tolerance settings in the Details view.

Adjusting the Tolerance settings is a necessary step; it is not optional.
The following default settings were incorrectly listed.
The default setting for the Edge/Edge option is Yes.

The default setting for the Face/Face and Face/Edge options is No.
The following statement is incorrect:
property defines the minimum angle between the faces above which the two face pairs will
be ignored from proximity detection. The default value is 70.
property defines the minimum angle between the master face and slave edge entity above
which the two face pairs will be ignored from proximity detection. The default value is 70.
The description of the Group By control omits the Faces option:
An additional control, Group By is exposed in the Details view. Options for Group By in-
clude None, Bodies, Parts, and Faces. This property allows you to group the automatically
generated connections objects. Setting Group By to Bodies (default) or to Parts means that
connection faces and edges that lie on the same bodies or same parts will be included into
a single connection object.
An additional control, Group By is exposed in the Details view. Options for Group By in-
clude None, Bodies, Parts, and Faces. This property allows you to group the automatically
generated connections objects. Setting Group By to Bodies (default) or to Parts means that
connection faces and edges that lie on the same bodies or same parts will be included into
a single connection object. The Faces option is only available if the Face/Face or Face/Edge
controls are set to Yes.
(97987)
Workbench
The Workbench documentation on design points does not specify that Workbench design points go
out of date when postprocessed in CFD-Post. Work-around: Retain the design points prior to updating
and export them to separate Workbench projects once they are up to date. (98141)
Chapter 5: Advisories
Chapter 6: ANSYS Structural Products
6.1. Mechanical
See the Documentation section of this document for items specific to the Mechanical Users Guide in
the ANSYS Help.
In Harmonic Response, Phase Response results are incorrect when complex Force and Pressure loads
are defined by Components. (92294)
If you execute a solve and there are failures during mesh generation, empty/suppressed Named Selections
are created in the tree. The empty/suppressed Named Selections can be ignored. (97148)
In a MSUP harmonic analysis with Cluster Results set to Yes, Force and Moment Reactions give zero
results when other regular results are not requested. Work-around: Add any other regular results like
Deformation/Stress/Strain along with the Force and Moment Reactions. (97619)
The location of a Rotating Force load is not updated correctly when the Define By property of the
Location group is set to Geometry Selection and the scoping is a body or multiple edges/faces/bodies.
(98322)
6.2. Mechanical APDL

When modeling contact surface wear at an interface having symmetric contact pairs, wear results may
be incorrect if you define wear (TB,WEAR) on only one of the contact surfaces in the symmetric
pair. Work-around: For the case of symmetric contact pairs, you must define wear (TB,WEAR) for both
contact pairs. If wear is desired on only one surface of the symmetric contact pair, set the wear coefficient
(C1 on the TBDATA command) to zero for the surface where wear should not occur. (97605)
XFEM-based fracture analysis supports only analyses where large deflection is not present (NLGEOM,OFF).
The CINT command always evaluates circumferential stress (PSMAX) and maximum circumferential stress
(STTMAX) in the initial configuration. Geometry changes are ignored. A mismatch exists between what
XFEM requires when large deflection is active (NLGEOM,ON) and the PSMAX and STTMAX values that
the CINT command provides, leading to errors in XFEM-based crack propagation. The error is minor
when the displacement vector at the crack tip node is small. (98377)
6.3. Autodyn
6.4. Aqwa
When defining stiffness and damping for a ball and socket in Aqwa Workbench that uses an Alignment
Method for the Joint Axes other than the Global Axes, the interface displays the definition in the joint
local axis system but the core solver treats the definition as being in the global axis system. To avoid
this only use the Global Axes for the Alignment Method. (97902)
ANSYS Structural Products
When a geometry value is parameterized in DesignModeler such that the position of a program-controlled
mass changes in Aqwa the mass may not be in the correct position. (98155)
6.5. Beamcheck
6.6. Fatjack
6.7. ANSYS Composite PrepPost (ACP)

Performing node merge operation within a part (as opposed to node merge across different parts) im-
ported from ACP renumbers the element Ids. This corrupts the composite definition on the part and
the results obtained will be incorrect. (98602)
Chapter 7: ANSYS Fluids Products
7.1. Fluent
In simulations that use the discrete phase model, particle mass may be lost when simulation of transient
particles released with constant parcel size is combined with auto-save of case files. (84288)
Use of the Lagrangian wall-film model in combination with hanging-node adaption in a parallel Fluent
session may cause the Fluent session to fail. (97573)
User-defined wall functions are not compatible with the Eulerian multiphase formulation and cannot
be used. (97810)
In some situations when a mesh is replaced, data may not get interpolated to the new mesh. (97848)
7.2. CFX
If the window for CFD-Post, the ANSYS CFX Launcher, Solver Manager, or Turbogrid is closed on a
second monitor, then the second monitor is removed, the window will be outside the visible area when
next started. Work-around: If you switch on the second monitor, you can again see the window. If the
second monitor is no longer available, you can change the initial screen position of a window by editing
the corresponding "WindowX" and "WindowY" settings in CFXPreferences.ccl, for example by setting
both to 0 (zero). (75285)
In a multiple frame of reference calculation, if there is a Stage interface between rotating and stationary
domains, then the hybrid values of temperature-related variables such as temperature, total temperature,
and total temperature in the stationary frame may be in error. The same is true for the hybrid values
of enthalpy-related variables. To avoid these errors, plot only conservative values. (95946)
On Linux machines with an NVIDIA graphics card, processes related to CFX-Pre (in particular,
PreGui_ogl.exe) are not always cleaned up properly when CFX-Pre is closed. These processes have to
be stopped manually. (96655, 98074)
If a solution of a particle transport case is interpolated, for example to restart on a different grid, particle
mass flow information including time integrated information may not be read correctly and be set to
zero. This information will then be wrong throughout subsequent time of a transient simulation. (97114)
If a multiple frames of reference simulation with transient rotor-stator interfaces is solved in parallel
with multipass partitioning, then it is possible for the solution process to hang because the partition
smoothing algorithm has created partitions without any vertices. Work-around: Switch off the partition
smoothing algorithm. (97256)
The relative motion between Coord0 reference frame and local frames applied on boundaries may not
work as expected. The behavior is unchanged if no relative motion is set. (97843)
7.3. TurboGrid
ANSYS Fluids Products
7.4. BladeModeler
7.5. CFD-Post
If the Results component has output parameters in a project originating from Release 12.1 or earlier,
then a Refresh of the Results component will invalidate other design points. To fix: Edit the Results
component, then deselect the expression as an output parameter and then reselect it. (This also inval-
idates other design points.) Work-around: Avoid using the Refresh operation, and use the Update op-
eration instead. (97172)
7.6. Polyflow
When using ANSYS Meshing as part of a Polyflow simulation, note that the definition of the Export
Unit for Polyflow (available in the Options dialog box when Export is selected under Meshing in the
left pane) is not saved in the Workbench project file. As a result, the Export Unit defined in one Work-
bench session may impact the next session. Work-around: You should always inspect the final units
read by Polydata. The Export Unit feature should not be used for Workbench-driven parametric runs nor
when using the Remote Solver Manager, because the consistent updating of the export units is not
guaranteed. This feature should only be used for manually run single design points. (96475)
Chapter 8: ANSYS Electronics Products
8.1. Icepak
When solving cases with parameters, fast trials option cannot be used. Current and previously solved
cases consisting of fast trials cannot be post processed. (98642)
Chapter 9: ANSYS Geometry & Mesh Prep Products
9.1. CAD Connections & Integration
See the Documentation section of this document for items specific to the CAD Integration section of
the ANSYS Help.
9.2. DesignModeler
9.3. Meshing
See the Documentation section of this document for items specific to the Meshing section of the ANSYS
Help.
SUSE Linux systems may run out of memory during mesh processing, causing the mesher to fail. Work-
around: Split the model into separate pieces or increasing the mesh size to reduce the overall cell
count. (85341)
The new Tools->Options->Meshing->Export->Polyflow->Export Unit options have some limitations and

awkward behavior users should know about. For example: any changes made to the export units are
not currently saved in the Workbench project. Export units defined in one Workbench session may impact
the next session. You should always inspect the final units read by Polydata. This feature should not be
used for Workbench driven parametric runs since the consistent update of the export units is not
guaranteed. This feature should be used for manually run single design points. (96475)
If you have a mixed configuration of Mesh Connections and Node Merge controls, changing the Node
Merges causes the mesher to revert to the base (last saved) mesh, which might invalidate existing mesh
connections. To correct this, update the project and the mesh connections will be restored. (97377)
9.4. IC Engine
9.5. ICEM CFD

9.6. Fluent Meshing

While wrapping large, complex geometries with small mesh sizes, the mesh memory limit may be ex-
ceeded. An error message will be displayed recommending a coarser size field be used. (78466)
Wrapping a multi-face zone model using the Low Geometry Recovery option may be slower than in
previous releases due to more rigorous adaptation of mesh size to size field. (96244)
ANSYS Geometry & Mesh Prep Products
When using a proximity size function in certain geometries (angle > 30 degrees or extended region of
non-intersecting faces), the proximal face zones may not be detected. (96617)
Proximity size function computations for large complicated geometries may result in a warning message.
Should the warning message appear, split the proximity size function into multiple scoped size functions.
(96617)
When growing prisms into both solid and fluid regions from a solid-fluid interface, unexpected stair-
stepping may occur on the fluid side where stair-stepping occurs on the solid side. Work-around:increase
the boundary mesh density in the solid region to allow at least two tetrahedrons or reduce the gap
factor to avoid any stair-stepping. (97692)
When using Auto Mesh after recovering periodicity, an error may be reported if the shadow zone is
named "original_periodic_zone:#", where # is an incorrect shadow zone ID. Work-around: Rename the
shadow zone to "shadow:#", where # is the correct shadow zone ID and proceed with Auto Mesh. (97930)
The Delete Fringes operation for fixing multi-connected faces runs slower than previous releases. (97967)
Using Fluent meshing with a model having a long file name (>90 characters) may result in instability.
Work-around: Reduce the file name length to fewer than 90 characters. If a crash is experienced after
reading a file having a long file name, then delete the file $HOME/.flrecent so that artifacts of this
problem do no affect future sessions of Fluent Meshing. (97978)
In the case of distributed prism meshing, if any pre-ignore happens across a partition interface, the
non-conformal creation can make the partition interface zone inconsistent across the compute nodes.
This can make the mesh unusable. In the case of distributed meshing, if /mesh/modify/auto-node-move
is used to move nodes along a partition interface zone, it can make the partition interface zone incon-
sistent across the compute nodes. The mesh may still be usable after agglomeration or switching to
solution mode. However, the quality of some cells may change after these operations. (98259)
Shrinkwrap operations at Release 16.0 might demand more peek memory on Linux platform, compared
to Windows or compared to Release 15 on Linux. (98343)
Chapter 10: ANSYS Simulation Products
10.1. Workbench
See the Documentation section of this document for items specific to the Workbench section of the
ANSYS Help.
On some AMD cards, 2D and 3D vector symbols may not render correctly. To display the vector symbols
correctly, choose the 1D Arrow vector symbol. (86507)
Beam stress results and beam strain results (available by setting "Calculate Beam Section Results" option
to Yes) will not be displayed correctly in a Harmonic analysis although values in Details View are correct.
(97348)
Export of regular Principal Vector stress/strain results contains incorrect header information (the header
for user defined Principal Vector results is correct):
1. If user picks Show Tensor Components=No, the correct data appears (principal axes and
Euler angles) but the header is for raw components.
1. If user picks Show Tensor Components=Yes, the correct data appears (raw components)
but the header is for principal axes and Euler angles.
(97365)
If ICEM exposes any output parameters, update the project using the Update option in Workbench.
Updating from inside the application will invalidate the design point states for non current design
points. (97418)
System Coupling
10.2. EKM
See the Documentation section of this document for items specific to the EKM Installation Guide and
EKM Administration Guide.
If you pause or interrupt the solution during a Fluent server-mode job and enter a Fluent command in
the command window which requires an argument to be wrapped in quotation marks, the command
will be executed, but when you resume the solution, the job may go directly to the Executed stage. To
avoid this issue you should re-execute the job instead of resuming the solution. Re-executing the job
will resume the solution from the point at which it was paused or interrupted. (97832)
In the Open Process Template dialog box in EKM Studio, attempting to open a repository file from
My Applications or Shared Applications will fail unless a path of some kind is displayed in the Repos-
itory Folder edit box. (97986)
After upgrading from EKM 15.0 to EKM 16.0, non-administrator users will not be able to use Starred
Data or Recent Data in the Data section. (See 8.1.3. Starred Data and 8.1.4. Recent Data in the Users
ANSYS Simulation Products
Guide.) To enable these pages, an administrator can run the following Python script in the Scripting
Command Window:
cmd = ekm.getCommandObject("changePermissions")
cmd.addModel(ekm.getObjectByPath("/My Home/Starred"))
data = {}
data["recursive"] = True
data["permissions"] = {"all":["access"]}
cmd.execute(data)
cmd = ekm.getCommandObject("changePermissions")
cmd.addModel(ekm.getObjectByPath("/My Home/Recent"))
data = {}
data["recursive"] = True
data["permissions"] = {"all":["access"]}
cmd.execute(data)
For information about running scripts, see 12.9. Running Python and BeanShell Scripts from a Command
Window in the EKM Administration Guide. (98272)
Following an upgrade from EKM 15.0 to EKM 16.0, navigating to the AdministrationUsers page, selecting
a User object created with EKM 15.0, and selecting MoreDisplayList will cause an error. To prevent this
problem, an administrator can run the following Python script in the Scripting Command Window:
usersFolder = ekm.getObjectByPath("/Administration/Users")
for name in usersFolder.getChildNames():
ekm.startTransaction()
print ">>> Making /Administration/Users/" + name + "/usageStats internal."
ekm.getObjectByPath("/Administration/Users/" + name +
"/usageStats").getModel().setInternal(True)
print ">>> Making /Administration/Users/" + name + "/tempFolder internal."
ekm.getObjectByPath("/Administration/Users/" + name +
"/tempFolder").getModel().setInternal(True)
ekm.commitTransaction()
(98028)
If for some reason a newly created workspace fails to initialize, no EKM user can sign in to EKM. For
example, a workspace may fail to initialize if you chose to import an exported workspace during work-
space creation, but did not specify the path to the exported workspace correctly. Work-around:
1. Shut down and restart the EKM server.
2. Sign in to EKM Administrator as superuser.
3. Delete the new workspace.
(98148)
If an administrator creates a new workspace by importing a previously exported workspace, non-admin

users may encounter errors when signing in, or when attempting to access their Dashboard, Recycle
Bin, and other user-specific folders. Work-around: Stop and restart the server after the new workspace
is created. (98207)
10.3. DesignXplorer
Optimization objectives defined on input parameters are not handled as expected in charts. If the study
contains only objectives defined on input parameters, the Samples and Trade-off charts cannot be
generated. If the study combines objectives and constraints on input and output parameters, the
input parameter is not taken into account when calculating the Pareto fronts. Work-around: Create a
DesignXplorer
derived output parameter equal to the input parameter, and optimize the derived output instead of
the input parameter. (96695)
Chapter 11: ANSYS AIM
See the Installation section of this document for items specific to the installation of SpaceClaim Products
installed prior to Workbench 16.0 and the configuration of SpaceClaim Direct Modeler during the install-
ation of ANSYS AIM.
When using user-defined expressions, if a result depends on the output of another result, the evaluation
may fail because the order of evaluation is not taking into account the expression dependencies. You
can solve the problem by manually evaluating each result in the correct order (note this does not apply
to updating multiple design points). For example, you cannot optimize the output of a Calculated Value
object if it depends on the output of another Calculated Value object. (75135)
When saving a project, if your project name contains non-ASCII characters, the project may fail to save,
and if it fails, may corrupt the data. Work-around: Only use ASCII characters for project names. (75693)
Memory usage may be escalated when evaluating streamlines, especially when using Volumetric Grid
Sampling. Memory use can be reduced by reducing the number of sample points and/or the maximum
number of steps. (96055, 98054)
When using the French or German locale, the Location Criteria Functions do not accept comma
decimals when a comma is selected in the Decimal symbol field of the Numbers tab in the Customize
Format dialog box. Work-around: The arguments to criteria functions are enclosed in double quotes,
and any value inside the double quotes must use the dot rather than the comma. (97091)
When you duplicate a Physics task with an undefined parameterized value, you will see an error message
for the duplicate Physics task. You can avoid this by making sure that all the parameterized values are
defined in the original Physics task before you duplicate it. (97435)
If an input parameter and a named value are defined for the same input property, and another input
property is defined by an expression referencing this named value, then up-to-date design points are
invalidated each time a design point update occurs. (97507)
When working with multiple simulation processes, the current simulation process may give blank or
invalid results if it references an object containing a topology selection from a different simulation
process. For example, the topology selections (selection sets, location-aware objects, or expressions)
may have invalid or unexpected values when creating a current simulation process with duplicated
tasks from another simulation process. Work-around: After duplication of results objects verify location
assignments are correct for current simulation process. (97553)
When using a Named Value to define a property, it may be possible to update a task even though the
Named Value is empty, leading to erroneous output. Care should be taken to ensure all Named Values
are properly defined before updating a task. (97661)
After solving with fluid flow and thermal physics, with the physics options set to laminar flow, turning
off thermal physics and setting the flow to turbulent will result in an incorrect error on physics. Setup
a new physics task to resolve this issue. (97806)
ANSYS AIM
You will see an error message when you create a contour of Turbulence Kinetic Energy or another user-
defined variable on a streamline. You can avoid this by creating a dimensionless variable before evalu-
ating the contour. For example, if you want to create a contour of Turbulence Kinetic Energy, you can
enter "TurbulenceKineticEnergy/1[m^2 s^-2]" in the variable field for the contour result. (97821)
If a wrap is meshed with a very coarse size, the point inside the flow region may be outside the mesh
even if it was within the geometry. If this happens, no error will be issued. In this case, you should move
the point to be within the mesh, or mesh with a finer size. (97859, 98181)
If named expressions that refer to solver variables are combined, then this can lead to an incorrect
evaluation. For example:
expr1 = Position.x + 0.1 [m]

expr2 = Position.y + 0.2 [m]
expr1 * expr2
would evaluate to Position.x + 0.1 [m] * Position.y + 0.2 [m] instead of (Position.x + 0.1 [m]) * (Position.y
+ 0.2 [m]). Work-around: Manually insert extra brackets around each named expression (expr1) * (expr2).
(97998, 98297)
If a named expression is used in a fluids solver/post-processing expression 'unmodified' then subsequent

changes to the named expression definition will not be correctly updated. To work around this, either
modify the expression that refers to the named expression to include some dummy modifier, create a
new named expression, or use an 'inline' expression instead. In the following example, changing the
named expression will not update the use of that expression in the 'Normal Speed' property.
myNamedExpression = 1[m/s]
Boundary Condition > Normal Speed = myNamedExpression
Work-around: Boundary Condition > Normal Speed = 1*myNamedExpression (98046)
A task update will fail and the project will be corrupted if the task contains a selection set created by
capping surfaces and that selection set is referenced by some other object in the task. Work-around:
Manually create a selection set, and apply it to the same reference that the capping surface selection
set references, and then reference this manually created selection set instead of the one created by the
capping surface. (98088)
The document How to Interrupt a Physics Update in ANSYS AIM (Beta) can be found at Knowledge Re-
sources> Online Documentation > Documentation Information (http://support.ansys.com/docinfo) on
the ANSYS Customer Portal. (98150)

ANSYS, Inc. Known Issues and Limitations PDF

Cargado por

Información del documento

Título original

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

ANSYS, Inc. Known Issues and Limitations PDF

Cargado por

Copyright:

Formatos disponibles

Known Issues and Limitations

ANSYS, Inc. Release 16.0

ANSYS, Inc. is certified to ISO 9001:2008.

U.S. Government Rights

Published in the U.S.A.

SpaceClaim Products Installed Prior to Workbench 16.0 Installation

SpaceClaim Direct Modeler Configuration

<login-module xmlns="" code="waffle.jaas.WindowsLoginModule"

Under Mesh >Mesh Connection Group:

A Mesh object is not a parent of the Mesh Connection Group object.

Under Mesh >Mesh Connection Group, the following statement is incorrect:

Under Mesh> Mesh Connection Group, the following statement is incorrect:

Group By: options include None (default) and Faces.

Group By: options include None and Faces (default).

Under Mesh> Mesh Connection:

A Mesh object is not a parent of the Mesh Connection object.

Under Scoping, the statement:

Connections are made edge-to-face or face to vertex;

Connections are made edge-to-face or vertex-to-face;

Under Application, the statement:

Under Common Imprints and Mesh Connections, the paragraph:

3. Click Yes, Click to Display to display related error messages.

4. Right-click on the error messages:

a. If a message provides Problematic Geometry information:

b. If a message provides Go to Body information:

Under Points to Remember, the following points are no longer applicable:

Under Requirements, the paragraph:

Under Application, the paragraph:

Step 5 of the instructions to automatically apply node merges begins:

5. Optionally, modify the Tolerance settings in the Details view.

The following default settings were incorrectly listed.

The default setting for the Edge/Edge option is Yes.

The following statement is incorrect:

The description of the Group By control omits the Faces option:

6.2. Mechanical APDL

6.7. ANSYS Composite PrepPost (ACP)

The new Tools->Options->Meshing->Export->Polyflow->Export Unit options have some limitations and

9.5. ICEM CFD

9.6. Fluent Meshing

1. Shut down and restart the EKM server.

2. Sign in to EKM Administrator as superuser.

3. Delete the new workspace.

If an administrator creates a new workspace by importing a previously exported workspace, non-admin

expr1 = Position.x + 0.1 [m]

If a named expression is used in a fluids solver/post-processing expression 'unmodified' then subsequent

También podría gustarte