ANSYS, Inc.

Known Issues and Limitations

Release 15.0 ANSYS, Inc.
November 2013 Southpointe
275 Technology Drive ANSYS, Inc. is
certified to ISO
9001:2008.
Canonsburg, PA 15317
ansysinfo@ansys.com
http://www.ansys.com
(T) 724-746-3304
(F) 724-514-9494
Copyright and Trademark Information
2013 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 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 subsidi-
aries 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 CONFIDENTIAL 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, com-
pliance 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 li-
cense 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
6. ANSYS Structural Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
6.1. Mechanical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
6.2. Mechanical APDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
6.3. Autodyn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
6.4. Aqwa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
6.5. Beamcheck . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.6. Fatjack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
7. ANSYS Fluids Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
7.1. Fluent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
7.2. CFX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
7.3. TurboGrid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
7.4. BladeModeler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
7.5. CFD-Post . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
7.6. Polyflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
8. ANSYS Electronics Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.1. Icepak . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
9. ANSYS Geometry & Mesh Prep Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
9.1. CAD Connections & Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
9.2. DesignModeler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
9.3. Meshing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
9.4. IC Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
9.5. ICEM CFD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
9.6. Fluent Meshing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
10. ANSYS Simulation Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
10.1. Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
10.2. EKM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
10.3. DesignXplorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
iii
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates. iv
Introduction
The following information is relevant to ANSYS, Inc. Release 15.0. The entries
describe known non-operational behavior, an error, or limitation at the time of
this release. Work-arounds for these items, if available, are included in the respect-
ive descriptions. Inclusion in this document does not imply the issues and limit-
ations are applicable to future releases.
The parenthetical numbers associated with each entry are reference numbers
corresponding to an internal 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 information about service packs and any additional items
not included in this document. First-time users of the customer portal must re-
gister 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.
v
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates. vi
Chapter 1: Installation
No known issues, limitations, or documentation inaccuracies.
1
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates. 2
Chapter 2: Licensing
No known issues, limitations, or documentation inaccuracies.
3
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates. 4
Chapter 3: Platform Support
ANSYS 15.0 will be the last release to support the Windows XP operating system,
Windows 7 (32-bit) operating system, and the Windows 32-bit platform. Sub-
sequent service packs' and verification testing packages' discontinuance of sup-
port of Windows XP will concur with Microsoft's discontinuance of the same,
anticipated to be April 2014. For detailed and current support information, see
the Platform Support section of the ANSYS, Inc. website (www.ansys.com).
5
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates. 6
Chapter 4: Documentation
ANSYS Help Viewer
When using the "Match Case" option of the Help Viewer Search, the results'
highlighting incorrectly highlights all matches to the word, regardless of case.
(61182)
On Windows systems, if you are running from a network installation and the
images do not appear correctly in the Help Viewer, access the shared drive
containing the installation via a mapped drive instead of accessing the share
directly with a UNC path. (70600)
ANSYS Fluent
The following should be included in the list of limitations for the cluster to cluster
basis in Section 13.3.4.1.2.1. of the ANSYS Fluent 15.0 User's Guide:
The cluster-to-cluster basis is not supported for non-conformal interfaces.
(71158)
CAD Integration
The Teamcenter Unified Architecture 9.1 entry in the Geometry Interface Support
table for Windows in the CAD Integration section inadvertently shows support
for the Windows 8 operating system. Teamcenter Unified Architecture 9.1 (2- &
4-tier) with NX 7.5, NX 8.0, and NX 8.5 is not supported on the Windows 8 oper-
ating system. For related issues, see the CAD Connections & Integration section
of this document. (69423)
The JT Reader section of CAD Integration help should include the following
statement in the Caveats and Known Issues section: JT tessellation-only data
files are not supported. JT Reader requires that the JT file contains Boundary
Representation (B-rep) data.
7
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
EKM
In section 5.1.1.2. Supported Operating System Versions of the EKM Installation
Guide, the list should also include Windows Server 2012. (71010)
Section 11.6 Recording Journal Scripts in the EKM Administration Guide contains
a list of actions that can be recorded in a journal. The following items in that list
should not be part of the list:
Analysis project > update analysis
Application > execute
Case model file > create summary report
File > extract metadata
File > synchronize
Lifecycle > edit in Studio
Recycle bin > empty
Report > refine comparison
Script file > execute
Saved query > refine search
Workflow > edit in Studio
(71218)
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates. 8
Documentation
Chapter 5: Advisories
No known issues, limitations, or documentation inaccuracies.
9
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates. 10
Chapter 6: ANSYS Structural Products
6.1. Mechanical
When running a Static or Transient Structural analysis with a Thermal Condition
load, you will need to ensure that all the materials used in the analysis define
the Coefficient of Thermal Expansion property. You cannot proceed to solve your
analysis if this property is not defined, in Engineering Data, for all the materials
used in the analysis. (60429)
When scoping results to elements, Mechanical may display and report results
on some elements that were not scoped. This can happen when an unselected
element has all its nodes in the scoped set. In addition, the reported minimum
and maximum values of the result may be incorrect.
The reported minimum and maximum values are only correct using element
scoping for the following conditions:
Nodal results (like deformations, temperatures, and voltages)
Element Nodal results (like stresses, strains, and fluxes) with the Display Option
property of the Result object set to Unaveraged.
Note: You can determine the data type (Nodal, Element Nodal, or Elemental) of
a result by looking at the Data Type column in the Worksheet of the Solution
object. (66737)
When using parallel part-by-part meshing with extremely large assemblies, you
may see a performance slowdown in remeshing. If you do, a workaround is to
save your project, exit and restart Workbench, reload the project and continue
with your meshing activities. (68906)
Element scoping to Coordinate Systems result types (Element Triads, Elemental
Euler XY, YZ, and XZ Angle), the Strain Energy result type, or the Error result type,
produces invalidate results and may cause Mechanical to crash. These result
types currently do not support element-based scoping. In addition, when scoped
to elements on the model, you cannot use these result types in combination
11
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
with the Promote to Named Selection feature; doing so may also cause Mechan-
ical to crash. (69550)
When using the Distributed ANSYS solver to perform a fracture analysis in
Mechanical, the Stress Intensity Factors (SIFS) and J-Integral (JINT) computations
may yield incorrect results. Mechanical uses the MAPDL CINT,CTNC option with
a node not associated with any of the elements as the crack assist node to specify
the crack extension direction. (70326)
For 2D analyses on the Linux platform, Mechanical does not support the Imported
Initial Stress and Imported Initial Strain loading option. Specifying and executing
these options causes the application to terminate abnormally. (70647)
If you have a Transient Structural analysis and a Modal analysis that share the
same model, and the Transient Structural system includes one or more Initial
Velocity objects in the Initial Conditions group, Mechanical will crash if you make
changes to the "Damped", "Solver Type" or "Store Complex Solution" properties
under Solver Controls of the Modal system. Work-around: The work-around
depends upon what you want to achieve.
If you want to run independent modal and transient structural solves with the
same model setup and Initial Velocity object(s) present, make sure that they
don't share a common model. Use system "Duplicate" and "Replace with" op-
tions from the project schematic to quickly form different analyses with the
same model configuration.
If you wish to form a MSUP Transient system by linking a Modal solution to
an existing Transient analysis, delete any Initial Velocity objects that are present
in the Transient analysis.
(71011)
If you experience a failure while importing an external mesh file into Mechanical
via External Model, you may also encounter large error messages in the Work-
bench application. These messages can cause Workbench to terminate abnormally.
To avoid this error, close the message window in the Workbench application
before importing the data into Mechanical. (71045)
For a Pre-stressed Full Harmonic analysis, the Nodal Pressures boundary condition
does not support the Function and Tabular features for defining the Magnitude
property. If the Magnitude property is set to Function or Tabular, results will
appear with a value of zero. (71084)
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates. 12
ANSYS Structural Products
At Release 15.0 in the Mesh Display section of the Annotation Preferences dialog
box, the "Plot Elements Attached to Named Selections" option is on by default.
This causes all the name selections to try to show the underlying mesh, which
in cases with hundreds of name selections and complicated meshes will require
significant computing effort, compared with the variant showing the underlying
geometry. Work-around: In these cases, switch off the "Plot Elements Attached
to Named Selections" option. (71179)
6.2. Mechanical APDL
For cyclic mode-superposition harmonic analyses, the POST26 RCYC command
does not support equivalent and principal strains and stresses. Work-around:
Use POST1 /CYCEXPAND to obtain these quantities. Additionally, the TIMERANGE
command does not work. Work-around: Use the PLTIME command to limit the
frequency range. (68603)
For cyclic mode-superposition harmonic analyses, using the modal coordinates
output key (MCout on the HROPT command) leads to incorrect solutions. Work-
around: Do not use this option. (68603)
For cyclic mode-superposition harmonic analyses, distributed-memory processing
(-dis on the command line) is not functioning. Work-around: Use share-memory
processing. (63993)
When generating superelements with the BACKSUB expansion pass method
(SEOPT,BACKSUB), the .LN22 file created by the sparse solver cannot be transferred
between 32-bit and 64-bit systems. For example, if a superelement is created on
the Windows 64-bit system, it cannot be expanded on a Windows 32-bit system
(and vice versa). (70199)
In a perturbed harmonic analysis when all the boundary conditions are kept
(PERTURB,HARMONIC,,,ALLKEEP), any locked-in pretension load (SLOAD) from
the preceding prestress step is not ignored and will lead to an oscillating load
in the harmonic analysis. Work-around: Use one of the other LoadControl options
on the PERTURB command which will ignore the locked-in displacement in the
harmonic load. (71123)
6.3. Autodyn
In Euler-Unstructured Langrange coupled models a parallel slave executable may
hang if the decomposition is such that none of the Lagrangian unstructured
elements on that slave participate in the coupling. Work-around: Use the
13
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
Autodyn
manual decomposition option and decompose the coupled Lagrangian unstruc-
tured elements over all the available slaves, such that each slave will participate
in the coupling. (69786)
For a project containing linked Explicit Dynamics and Autodyn systems, closing
Workbench following an update to the Autodyn system may result in a crash.
The termination error can be avoided by closing the Autodyn application before
Workbench or saving the project before closing Workbench. No data loss is as-
sociated with this issue. (70726)
6.4. Aqwa
If you are using Design Points in your Aqwa analysis, you may get incorrect results
if you have duplicate input parameter sets, or if you change or add input para-
meters or Design Points, then update the Design Points again.
After the initial solution, the results displayed in the Table of Design Points on
the Project Schematic are correct. However, if you view the results in the Aqwa
editor, the reported results correctly correspond to the "current" entry in the
Table of Design Points, but the displayed values of input parameters are incorrect,
so are inconsistent. In addition, if you have two Design Points with identical input
parameters, the results displayed in the Table of Design Points for the second
Design Point will be incorrect.
You must start from a known good state if you want to change or add input
parameters or Design Points. In order to create a known good state, after setting
up the initial parameters and Design Points, Archive the project before solving.
This allows you to revert back to the known good state whenever you want to
change or add any parameters or Design Points.
If you have already run an analysis without archiving the known good state and
then want to change parameters or Design Points, it is necessary to reset all the
parameters to their initial values. (This is also true if you resume a project that
you solved previously and want to make any changes to Design Points or para-
meters.)
To reset the parameters, follow these steps:
1. Copy all input parameter values from the Design Point table and paste them
into an external spreadsheet.
2. Open the Aqwa editor.
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates. 14
ANSYS Structural Products
Navigate through the tree to each parameterized input. a.
b. Deselect the "parameter" box next to the parameterized input.
c. Manually reset the input value to the initial one (the value corresponding
to the first Design Point in the Table of Design Points, noted as "Current").
d. Reselect the "parameter" box.
e. Repeat for all input parameters.
3. Optionally close the Aqwa editor
4. Go to the Design Points view in the Workbench Project window.
a. Copy the information that you saved in the spreadsheet back to the
parameters in the Table of Design Points.
b. Alternatively, you can reenter all input parameter values by hand.
c. Be certain that no Design Points are duplicated.
5. At this point you should Archive the project so that you can make changes
in the future from the known good state.
The project is now reverted back to a known good state allowing the user to
safely click on the "Update All Design Points" button.
Remember, once you update the Design Points, the results will be correct in the
Table of Design Points, but in the Aqwa Editor, your displayed results will not
match the input parameter values shown in the editor, and you must revert to
your known good state in order to run a new analysis. (61041)
6.5. Beamcheck
No known issues, limitations, or documentation inaccuracies.
6.6. Fatjack
No known issues, limitations, or documentation inaccuracies.
15
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
Fatjack
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates. 16
Chapter 7: ANSYS Fluids Products
7.1. Fluent
See the Documentation section of this document for items specific to the ANSYS
Fluent User's Guide.
When using poor-mesh-numerics with order 2 on a large number of parallel
cores, Fluent may crash if a partition boundary crosses a large cluster of poor
cells. Work-around: Re-partition with a different method. (61299)
When using the MSMD battery model in distributed parallel, Fluent may crash
if a second data file is read into the same Fluent session. (66689)
The DEM model is incompatible with periodic boundary conditions and should
be avoided. Using this combination may lead to errors or crashes. (69340)
When solving System Coupling problems in Workbench, if a Solution Monitoring
tab is left open for the connected Fluent session the Fluent processes will not
exit when the System Coupling solution is completed. On Windows, this results
in Workbench remaining in an Updating state until these processes are manually
killed. On Linux this may lead to Workbench hanging. (69976)
Specific to Windows platforms, writing a data file from a parallel Fluent session
on multiple nodes with the DO radiation model enabled may lead to a crash.
This problem does not affect Linux platforms or sessions run on a single node.
(70229)
7.2. CFX
The "Static and Total Pressure" option for the supersonic inlet boundary condition
does not work for variable composition mixtures. The solver will stop with an
error message about missing the initial guess for the Newton iteration method.
Please use an alternative option. (69839)
17
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
There may be instances where an abort occurs for single precision calculations
for multiphase flows using multiple frames of reference and the alternate rotation
model. The floating point exception can be avoided by doing the calculation in
double precision. (70066)
Contacts are not read correctly from Meshing when read into CFX-Pre:
On connecting a mesh cell to a CFX setup cell or reading a CMDB file directly,
if contact has been defined in the upstream component, the contact may not
be read correctly into CFX-Pre with the default settings. Remeshing a case
from R14.5 or earlier may result in the definition of automatic domain interfaces
dependent on the contact not being read correctly.
Setting the environment variable CFXACMO_IG-
NORE_NON_ONE_TO_ONE_CONTACTS or that the ANSYS Meshing Contact
Detection preference to Bodies or Self will result all contact being read or de-
tected respectively.
(70524)
7.3. TurboGrid
No known issues, limitations, or documentation inaccuracies.
7.4. BladeModeler
No known issues, limitations, or documentation inaccuracies.
7.5. CFD-Post
No known issues, limitations, or documentation inaccuracies.
7.6. Polyflow
Polydata may crash if you click the Upper level menu button in the Remeshing
technique menu without first fully defining the selected remeshing technique
(that is, defining such settings as the remeshing inlet and outlet for Optimesh,
or the g field for Thompson transformation). (70364)
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates. 18
ANSYS Fluids Products
Chapter 8: ANSYS Electronics Products
8.1. Icepak
Heat flux and heat flow values at boundary faces of 3D source objects placed
inside fluid regions cannot be reported. (36488)
The ray tracing radiation model does not include radiative heat transfer for solid
surfaces touching zero slack assemblies. (70293)
19
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates. 20
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 ANSYS Help.
An update/refresh may result in unexpected loss of mesh on unmodified bodies
when a Workbench database from a previous version is resumed in Workbench
15.0 and Compare Parts on Update feature is set to Associative. Additionally, if
program-controlled inflation is enabled in the meshing settings, it may also
contribute to an unexpected loss of mesh when refreshing geometry. (68858)
ANSYS Workbench may crash when a model imported into Teamcenter Unified
Architecture 9.1 (4-tier) is saved more than once, as observed using the Windows
8 operating system and Teamcenter patch 9.1.2.3. Teamcenter Unified Architecture
9.1 (4-tier) is not supported on the Windows 8 operating system. (69423)
CAD Readers for JT, Creo Parametric, Inventor, NX and SolidWorks may not fully
unconfigure on a client of a network installation, even when this action is attemp-
ted by a client's administrator. An administrative user on the server must execute
an unconfigure action, using CAD Configuration Manager, in order for these in-
terfaces to be fully deactivated on the client. (70719)
The Allow Model Defeaturing option is known to cause problem for some geo-
metries during Mechanical APDL import. Please avoid using the option if you
encounter a problem with it. (70762, 70813, 70818, 70819)
9.2. DesignModeler
No known issues, limitations, or documentation inaccuracies.
9.3. Meshing
Parallel Part Meshing will always generate line elements from line bodies, which
may not be appropriate for an electromagnetic analysis. Work-around: When
21
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
meshing line bodies for an electromagnetic analysis, set the Number of CPUs for
Parallel Part Meshing under Mesh --> Advanced to 1. (70267)
0-thickness walls (baffles) will not display properly when viewing mesh on named
selections. The 0-thickness wall will also not output correctly to Fluent, CFX, or
Polyflow. The 0-thickness wall is captured in the mesh (nodes are on the face),
but the faces are not marked as exterior faces. Work-around: Set the Mesh De-
tails->Advanced->Shape Checking to something other than CFD (for example,
None). (71719)
9.4. IC Engine
On Linux, for the close cycle combustion cases, where you are providing direct
values for IVC and EVO, DesignModeler may hang during the updation of Input
Manager; Work-around: In the ICE Properties View, select "By Lift Curve Profile"
from the "Input option for IVC and EVO" drop-down list and select any profile
file for "Valve Lift Profile And Piston Motion Profile". Then select "Enter Direct
Values" from the "Input option for IVC and EVO" drop-down list and enter the
values for IVC and EVO. (70836)
On Linux, for port flow simulation, design points study may some times fail
during the solution updation. Work-around: In the ICE Solver Setup Properties
View, select any journal file in the Post Iteration Journal field, for example you
can create a text file and add a single line (pp "test post iteration") and use it as
post iteration journal. (71516)
9.5. ICEM CFD
No known issues, limitations, or documentation inaccuracies.
9.6. Fluent Meshing
A limitation in the Prism Split option does not allow the prisms side to match
an existing quad meshed boundary zone forming a conformal mesh, assuming
that the quad boundary has no cell zones attached to it. (69125)
Multi-connected edges will not be fixed in situations where other Face Connectiv-
ity issues exist concurrently. Work-around: Fix other issues in a sequential
manner - fix self-intersections, fix non-manifold, etc., before fixing multi-connected
edges (70050)
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates. 22
ANSYS Geometry & Mesh Prep Products
Where face zones meet at an acute angle, default proximity checking may not
catch the proximal surface. Work-around: Refine the surface mesh at the thin
region and/or increase the Max Angle Change parameter (used during smoothing)
from the default 45 degrees. (70162)
Hotkey ctrl t does not show the trace path correctly if the face entities selected
are in different zones. (70542)
Orientation can only be specified in integers while defining local regions for tet
refinement through TUI. (70790)
Using the High option for Geometry Recovery when Shrink-wrapping an object,
Fluent-Meshing may hang if the geometry has overlapping edges. Work-around:
Use /boundary/feature/intersect-edge-zones command with delete overlapping
option before wrapping. (71421)
23
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
Fluent Meshing
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates. 24
Chapter 10: ANSYS Simulation Products
10.1. Workbench
A Linux desktop may crash when exiting Workbench on a Linux RHEL 5.x Virtual
Machine. Work-around: Set the LD_LIBRARY_PATH environment variable to
/ansys_inc/v150/Framework/bin/Linux64/Mesa before launching Workbench.
(62825)
Creating (e.g. duplicating or importing) a user-defined Custom Unit System may
result in quantities, inputs, and outputs to the solver to be computed incorrectly.
In order to ensure consistent results, make sure the current unit system is explicitly
set after the creation of a Custom Unit System. (63353)
Units may not convert consistently between ANSYS Composite PrepPost setup
cells in a linked system. Work-around: Use the same length unit in the Pre and
Shared cell. (70760)
If you have opted to reserve licenses for design point updates, when the Pre-
RSM Foreground Update property is set to Geometry and the Default Job
Submission property is set to One Job for Each Design Point, the pre-RSM
geometry update is performed without needing to reserve the appropriate license.
(70993)
System Coupling
When part of a transient coupled analysis, the Mechanical APDL solver will pro-
duce incorrect results when receiving Heat Transfer Coefficient and Bulk Temper-
ature values. This error occurs for Transient Thermal systems when the default
setting Program Controlled is used for Nonlinear Controls > Nonlinear Formulation
in the Analysis Settings within the Mechanical applications user interface. Correct
results will be generated by using the Full setting for Nonlinear Formulation.
(70304)
25
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates.
10.2. EKM
See the Documentation section of this document for items specific to the EKM
Administration Guide.
Users without download permissions on a file can access the file content in certain
contexts: such as through the scripting interface, in the process player or when
the file's parent folder is downloaded using FTC or to a location on the server.
To prevent unauthorized users accessing file content, remove the access permis-
sion of such users from those files. (70398)
10.3. DesignXplorer
On a Linux Red Hat 5.9 system, Workbench hangs when you update verification
points with discrete parameters in a DesignXplorer response surface. (71132)
In DesignXplorer, when a project contains input parameters with only negative
Manufacturable Values, the Design of Experiments (DOE) will be impacted. In
some cases, there will not be enough design points in the DOE to update the
Response Surface; in others, the Response Surface can be generated, but will be
most likely be inaccurate because of the incorrect distribution of points across
the parameter space. This may also affect the automatic generation of verification
points in the Response Surface.
Work-around:
1. In the DOE tab, click the Clear Generated Data button in the tool bar.
2. Deselect Use Manufacturable Values for all parameters that have only neg-
ative Manufacturable Values.
3. Preview the DOE.
4. Reselect Use Manufacturable Values for all the parameters that have only
negative Manufacturable Values.
5. Update the DOE.
(71247)
Release 15.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS,
Inc. and its subsidiaries and affiliates. 26
ANSYS Simulation Products