Known Issues and Limitations

ANSYS, Inc. Release 2020 R1

Southpointe January 2020
2600 ANSYS Drive ANSYS, Inc. and
Canonsburg, PA 15317 ANSYS Europe,
Ltd. are UL
[email protected] registered ISO
http://www.ansys.com 9001: 2015
(T) 724-746-3304 companies.
(F) 724-514-9494
Copyright and Trademark Information

© 2020 ANSYS, Inc. Unauthorized use, distribution or duplication is prohibited.

ANSYS, ANSYS Workbench, AUTODYN, CFX, FLUENT 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 located 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. FLEXlm and FLEXnet are trademarks of Flexera Software LLC.

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. and ANSYS Europe, Ltd. are UL registered ISO 9001: 2015 companies.

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, contact ANSYS, Inc.

Published in the U.S.A.

Table of Contents
Revision History ............................................................................................................................................ v
Introduction ............................................................................................................................................... vii
1. Advisories ............................................................................................................................................... 1
1.1. Mechanical Licensing ........................................................................................................................ 1
2. Installation .............................................................................................................................................. 3
3. Licensing ................................................................................................................................................. 5
4. Documentation ....................................................................................................................................... 7
5. ANSYS Structural Products ..................................................................................................................... 9
5.1. Mechanical ....................................................................................................................................... 9
5.2. Mechanical APDL ............................................................................................................................ 10
5.3. Autodyn ......................................................................................................................................... 10
5.4. Aqwa .............................................................................................................................................. 10
5.5. ANSYS Composite PrepPost (ACP) ................................................................................................... 11
5.6. Material Designer ........................................................................................................................... 11
5.7. Additive Manufacturing .................................................................................................................. 11
6. ANSYS Fluids Products .......................................................................................................................... 13
6.1. Fluent ............................................................................................................................................. 13
6.1.1. General .................................................................................................................................. 13
6.1.2. Meshing Mode ....................................................................................................................... 13
6.1.3. Solution Mode ....................................................................................................................... 13
6.1.4. Client Applications ................................................................................................................. 15
6.2. CFX ................................................................................................................................................ 16
6.3. TurboGrid ....................................................................................................................................... 16
6.4. BladeModeler ................................................................................................................................. 16
6.5. CFD-Post ........................................................................................................................................ 16
6.6. Polyflow ......................................................................................................................................... 16
6.7. Forte .............................................................................................................................................. 16
6.8. Chemkin-Pro .................................................................................................................................. 16
6.9. FENSAP-ICE .................................................................................................................................... 16
6.10. EnSight ......................................................................................................................................... 17
7. ANSYS Electronics Products .................................................................................................................. 19
7.1. Icepak ............................................................................................................................................ 19
8. ANSYS Geometry & Mesh Prep Products .............................................................................................. 21
8.1. CAD Connections & Integration ....................................................................................................... 21
8.2. DesignModeler ............................................................................................................................... 21
8.3. Meshing ......................................................................................................................................... 21
8.4. IC Engine ........................................................................................................................................ 22
8.5. ICEM CFD ........................................................................................................................................ 22
9. ANSYS Simulation Products .................................................................................................................. 23
9.1. Workbench ..................................................................................................................................... 23
9.1.1. TurboSystem .......................................................................................................................... 23
9.2. System Coupling ............................................................................................................................. 23
9.3. ANSYS ACT ..................................................................................................................................... 24
9.4. ANSYS Minerva ............................................................................................................................... 24
9.5. Remote Solve Manager (RSM) ......................................................................................................... 24
9.6. DesignXplorer ................................................................................................................................ 24
10. ANSYS Discovery ................................................................................................................................. 25
10.1. ANSYS Discovery SpaceClaim ........................................................................................................ 25
10.2. ANSYS Discovery Live .................................................................................................................... 25
10.3. ANSYS Discovery AIM .................................................................................................................... 25

Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. iii
 Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
iv of ANSYS, Inc. and its subsidiaries and affiliates.
Revision History
January 2020 Initial release

Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. v
 Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
vi of ANSYS, Inc. and its subsidiaries and affiliates.
Introduction
The following information is relevant to ANSYS, Inc. Release 2020 R1. 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 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.

Additional known issues and limitations may be found in the product Help and/or release notes, both
accessible in the ANSYS Help.

For the most recent version of the current release's Known Issues and Limitations document, see the
ANSYS, Inc. Release Notes section of the ANSYS Help internet documentation website or download it
here.

Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. vii
 Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
viii of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 1: Advisories

1.1. Mechanical Licensing

ANSYS is transitioning its customers to an improved, flexible licensing structure in 2021. In preparation,
beginning January 2020, ANSYS will begin to deliver debundled license files for some Mechanical
products including Mechanical Pro, Mechanical Premium, and Mechanical Enterprise. The current
Mechanical license increments will remain in the license file; as a result, customers may find they are
able to do more than their license normally allows. This additional capacity is temporary and will return
to the expected behavior at 2021 R1 when the new licensing structure is fully in place.

Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 1
 Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
2 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 2: Installation
No known issues, limitations, or documentation inaccuracies.

Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 3
 Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
4 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 3: Licensing
No known issues, limitations, or documentation inaccuracies.

Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 5
 Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
6 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 4: Documentation
No known issues, limitations, or documentation inaccuracies.

Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 7
 Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
8 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 5: ANSYS Structural Products

5.1. Mechanical
When closing Mechanical on the Red Hat 7.7 operating system and using remote viewing software, the
following message is generated: "A fatal error has occurred within AnsyWBU.exe and it must be closed."
Work-around: Set the environment variable ANS_MW_GDI equal to 1. (160372)

The use of the ParamAtPoint method on the IGeoEdge and IBaseGeoFace interfaces could return an
incorrect parameter if the associated edge or face belongs to a Part that has a non-identity transformation
matrix. (178662)

When meshing or solving in Workbench, an unintended "TBB Warning" may appear in the console
output. This warning message has no bearing on any process and can be safely ignored.

• TBB Warning: The number of workers is currently limited to (x). The request for (y) workers is
ignored. Further requests for more workers will be silently ignored until the limit changes.

(194471)

In the context of Level-Set based Topology Optimization, when defining a Compliance Response Con-
straint, you cannot change how the Limit property is defined, that is, either as a Constant or using
Tabular Data. When processing Response Constraints, Mechanical creates a constraint for each load
step in a multi-step analysis. Currently, for the Compliance constraint, the application only creates one
constraint during optimization, regardless of the number of load steps, and for the first load step only.
To duplicate the multiple step scenario, you can create a upstream Static Structural analysis for each
desired step and specify a Compliance constraint for each analysis. (208553)

Specific to the Topology Optimization validation workflow (topo.validation), boundary conditions that
expect to be scoped on cylindrical faces (cylindrical support, Bearing Loads and Bolt Pretension) will
have an invalid scoping and cannot be used in the downstream validation system. (208656)

In previous releases for Acoustics-based analyses, the application prompted you with a dialog box on
the Workbench Project page that pointed out you are creating a system that includes multiple physics.
This prompt no longer displays. (210799)

If multiple Pressure or Force loads that 1) share the same scoping, 2) are defined using the Vector or
Components options, and 3) are applied using the Direct option, then the load's component values
that are written to the input file last, overwrite all the previous component values. And, it is important
to note that when either load is defined using the Vector option and is applied using the Directoption,
the application sends zero values for the unspecified components. This nullifies the component values
of any previously specified load that share the same scoping. (211873)

When launching Mechanical/Meshing you may experience certain cosmetic user interface issues on the
Linux platform. The entries below describe the known issues.

Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 9
ANSYS Structural Products

• Graphics artifacts (such as highlighting and "ghost images") may display in the Outline. These do not
prevent you from selecting items in the tree. Hovering over the artifacts with the cursor typically removes
the artifacts. In addition, using the Maximize option for the inner Mechanical window can cause these
artifacts. This also applies if you open in the application in the maximized state. To correct the display,
select the Restore option of the inner window. If you wish to maximize the interface, use the Maximize
option of the Linux window.

• Editable drop-down controls may not allow selection or may show empty lists. You can work-around
this issue by manually entering the value in the control.

• If you are missing fonts for the docking pane buttons 'Menu', 'Auto Hide', 'Maximize', and 'Close' and
you are displaying remotely, you will need to install the fonts on your XWindows display server. Copy
the font files found under $INSTALL_DIR/aisol/CommonFiles/Fonts/linx64 locally to your XWindows
display server. Use the command "xset fp+ <local-dir>" on your XWindows display server so your
XWindows server can find the font files.

The following features have been disabled on the Linux platform:

• Body Views for Connections

• ViewPorts for graphical display

• Tooltips

(214164)

When you upload a Workbench archive that contains a Mechanical system, and the Model cell has no
data, metadata extraction may fail with the error, "Model is not available to create branches". (214196)

5.2. Mechanical APDL

The viscoelastic stored energy output, accessible as the ELASTIC component of SEND element solution
item, can be incorrect for 3-D 3-Node Elbow element ELBOW290. (153165)

Models using force-distributed constraints defined by contact elements (CONTAnnn) with KEYOPT(2) =
2 and KEYOPT(4) = 1 can produce incorrect results when both of these conditions are true:

• A non-zero rotational boundary condition or moment is applied to the pilot node.

• A predictor is enabled (PRED,ON) or the problem is solved via the quasi-static method (ANTYPE,TRANS
and TINTP,QUASI).

(212160)

5.3. Autodyn
No known issues, limitations, or documentation inaccuracies.

5.4. Aqwa
No known issues, limitations, or documentation inaccuracies.

Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
10 of ANSYS, Inc. and its subsidiaries and affiliates.
 Additive Manufacturing

5.5. ANSYS Composite PrepPost (ACP)

General ACP and release-specific limitations can be found in Known Limitations section of the ACP
User's Guide.

5.6. Material Designer

No known issues, limitations, or documentation inaccuracies.

5.7. Additive Manufacturing

Additive Prep

• No known issues, limitations, or documentation inaccuracies.

ANSYS Additive (Print and Science)

• If you select the Layer by layer stress/distortion output option, your output will be a series of .vtk files that
show the voxelized representation of your part layer-by-layer during the build. You will have as many .vtk
files as voxel layers in your part (as layerwise files are not written for support-only layers). There is a maximum
file size limit of 20 GB for Layerwise .vtk output files. This maximum value is for the sum of all the .vtk
files, not for any one file. The limit was established to prevent a loss of all data if a simulation failure occurs
because of insufficient disk space on your computer. Currently, if you reach this limit, the simulation continues
but the remaining individual .vtk layers are not written out. The final On-plate Stress/Displacement results
are not impacted by this limitation and will be valid. At this time, the limit is not configurable. Furthermore,
the UI tooltip erroneously states the limit to be 5 GB. Workaround: Increase your Voxel Size to reduce the
number of layers in the simulation. (215371)

Workbench Additive

• No known issues, limitations, or documentation inaccuracies.

Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 11
 Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
12 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 6: ANSYS Fluids Products

6.1. Fluent
The following sections list new or recently discovered limitations known to exist in version 2020 R1.

6.1.1. General
For a list of ongoing Fluent limitations listed in previous ANSYS, Inc. Release Notes, refer to Known
Limitations in ANSYS Fluent in the Fluent Getting Started Guide.

6.1.2. Meshing Mode

Meshing

• When starting the Meshing mode from the Fluent Launcher with a legacy case file (*.cas,
*.cas.gz), the Fluent Meshing window will open, but the case file will fail to load completely.
If this happens, use the File>Read>Case menu command to re-read the case file. This applies only
to starting Meshing with case files. Starting Solution mode and starting Meshing using mesh files
(*.msh,*.msh.gz), or case files in the HDF5-based Common Fluids Format (*.cas.h5) are
unaffected. (216631)

Meshing Guided Workflows

• Using journal (*.jou) or workflow (*.wft) files from previous releases may slow or even halt the volume
mesh generation process. Workaround: For journal files, make sure that you add version-specific inform-
ation to the beginning of your journal files (for example: /file/set-tui-version "19.5"). For
workflow files, make sure that you have the Quality Warning Limit property in the Create Volume Mesh
task set to a value closer to 0 (such as 0.05) instead of a value near 1. (163320)

Files

• It is not possible to import CAD files when running the meshing mode of Fluent on a Cray machine.
Workaround: Contact your technical support engineer and request a patch that can be used to update
the installation. (212131)

For a list of ongoing Fluent limitations, refer to Known Limitations in ANSYS Fluent in the Fluent
Getting Started Guide.

6.1.3. Solution Mode

Remote Display

• With enhanced graphics (enabled by default) the graphics window may become slow or hang
momentarily. If you experience either of these issues, disable the Ground plane grid option in the
Graphics branch of Preferences. (190056)

Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 13
ANSYS Fluids Products

Data Import and Export

• Writing animation files to MPEG format may result in unexpected errors if the animation image
files are saved at a size larger than 1360x768 pixels, with the exception of 1600x1200 and 1920x1200.
(194546)

Heat Transfer

• A WAVE coupling run may fail if the following environment variables are set:

– For Windows, set PYTHONHOME to NULL.

– For Linux, set PYTHONHOME to the python executable for Python version 2.7.15.
(212390)

• When writing S2S files, they will always have the .gz extension. Due to this, you need to set File
Type to All when reading S2S files to see the s2s.gz files in the working directory. (212969)

Solver

• The use of the Fractional Step pressure-velocity coupling scheme with dynamic mesh layering is not
supported. To run this combination, enter the following Scheme command before running the calculation:
(rpsetvar 'dynamesh/layering/layering-before-move? #t). (125886)

Graphical User Interface

• Automatic scaling of the ANSYS Fluent application window and graphics window interactivity are
not compatible when viewed on a 4K monitor. If the application is scaled properly, interactions in
the graphics window may not behave as expected. Set the QT_AUTO_SCREEN_SCALE_FACTOR
environment variable equal to 0 to have the graphics window work as expected. Set
QT_AUTO_SCREEN_SCALE_FACTOR equal to 1 to have the application scale properly. (143229)

Cell Registers

• Residual registers are only available for cases that are run using the pressure-based numerical
solver (PBNS). (165220)

Graphics, Reports, and Postprocessing

• Setting a selected surface to a specific color using the right-click Color by option in the graphics
window may change the color of other surfaces if the mesh is displayed using the global Mesh
Display dialog box (Domain > Mesh > Display in the ribbon). As a workaround, display the mesh
using the savable Mesh Display object (Results > Graphics > Mesh > New... in the ribbon).
(207794)

• Coloring surfaces using the Color by right-click option in the graphics window will display mesh
edges along with the color change, even if they are not enabled in the Mesh Display dialog box.
The first color change you make on the selected surfaces will not experience this behavior-only subsequent
color changes. (208149)

• User-defined surfaces (iso-surfaces, planes, points, and so on) cannot be selected or filtered using
the selection filter drop-down in the graphics window toolbar when the filter is set to any of the
user-defined surface types. (192978)

Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
14 of ANSYS, Inc. and its subsidiaries and affiliates.
 Fluent

• (Cell zones with porous media) Volume and mass integral reports do not account for porosity effects
in the porous media. (195382)

• Graphics effects are not included when saving pictures in AVZ format. (211327)

• To ensure enabled graphics effects have good performance, you must have a good graphics card
and your graphics driver must be set to either OpenGL2 (Linux) or DX11/OpenGL2 (Windows).
(171492)

• You may experience animation saving and playback issues if the Storage Directory specified in
the Animation Definition dialog box uses a relative path and it differs from the absolute path of
the working directory specified at launch or by reading a case file. As a workaround, provide an
absolute path in the Storage Directory field in the Animation Definition dialog box and ensure
that the folder exists. (197054)

Fluent in Workbench

• (HSF File, PPM Image, TIFF Image only) Solution animations created after loading a case or mesh
file will be saved in the same directory as the loaded case/mesh file, which results in the animation
no longer working after the Workbench project is saved and re-loaded. As a workaround, you can
either put the desired case/mesh file into the dp0/FLU/Fluent Workbench directory prior to
importing it or move the animation files to this directory before saving the Workbench project.
(197054)

• (PNG Image, JPEG Image only) Solution animations created after loading a case or mesh file will
be saved in the same directory as the loaded case/mesh file, which results in the animation no
longer working after the Workbench project is saved and re-loaded. As a workaround, you must
put the animation files into the dp0/FLU/Fluent Workbench directory before saving the Work-
bench project. If your case/mesh file is located in the dp0/FLU/Fluent directory prior to loading,
the animation files will be saved in the progress_files/dp0/FLU/Fluent directory, and will
have to be moved to dp0/FLU/Fluent prior to saving and closing the project. (212074)

Remote Solve Manager (RSM) and Design Point Service (DPS)

• If Fluent is set to run in parallel (more than 1 processor specified under Parallel Run Settings in the Setup
cell properties), then design point updates will run in parallel, even if the Component Execution Mode
is set to serial for the Parameter Set properties. Contact support for a workaround If this scenario negatively
affects your work flow. (192255)

For a list of ongoing Fluent limitations, refer to Known Limitations in ANSYS Fluent in the Fluent
Getting Started Guide.

6.1.4. Client Applications

Fluent Icing

• On Windows, in some situations, during a calculation, the synchronization of convergence graphs between
the Fluent Solver and Fluent Icing may cause Fluent Icing to suddenly disconnect from the Fluent Solver.
If this happens, Fluent Icing must be closed and reopened to continue properly. This issue may be avoided
by setting Solve → Global settings → Plot update interval to 0. (209823)

• On Windows, the Fluent Icing calculation time can slow unexpectedly if a previous Fluent Solver connection
had an unexpected error during the calculation, connection or disconnection process. Restarting Fluent
Icing and killing all background processes can return your simulation speed to normal. (209824)

Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 15
ANSYS Fluids Products

For a list of ongoing Fluent limitations, refer to Known Limitations in ANSYS Fluent in the Fluent
Getting Started Guide.

6.2. CFX
No known issues, limitations, or documentation inaccuracies.

6.3. TurboGrid
No known issues, limitations, or documentation inaccuracies.

6.4. BladeModeler
No known issues, limitations, or documentation inaccuracies.

6.5. CFD-Post
No known issues, limitations, or documentation inaccuracies.

6.6. Polyflow
When FIPS (Federal Information Processing Standards) is enabled, any Workbench project containing
Polyflow system(s) will be unable to update the status of the cells of the Polyflow system(s). This is due
to MD5 signatures being used to keep track of the changes of the different files of the Polyflow systems.
Since MD5 is not FIPS-compliant, MD5 signatures cannot be calculated when FIPS is activated, and so
the state of Polyflow systems cannot be updated. Workaround: Do not activate FIPS. MD5 signatures
will soon be replaced by FIPS-compliant ones in a future release, when you will have to update your
Workbench projects to that release before activating FIPS. (142282)

6.7. Forte
When using Ensight's SOS option (Server of Servers) to exploit parallel loading of Forte results, only
temporal parallelism should be used, otherwise results may contain visual artifacts. (144875)

6.8. Chemkin-Pro
No known issues, limitations, or documentation inaccuracies.

6.9. FENSAP-ICE
• In Multishot simulations with automatic remeshing using Fluent Meshing, there could be situations where
periodic or symmetry BC zones intersecting with the displaced ice surface produce errors in facet assignment.
After a large number of shots, it is possible that a few wall facets join to the symmetry or periodic BC zones.
This in turn jeopardizes prism block growth or tetra mesh initialization. The workaround is to load the
lastwrap.msh file in Fluent Meshing and to manually reassign these facets to their proper zones. Use
this repaired file to complete the rest of the remeshing and interpolation steps. (215361)

Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
16 of ANSYS, Inc. and its subsidiaries and affiliates.
 EnSight

• When Multishot with remeshing and screen model is enabled, the built-in custom remeshing script is not
copying the wire diameter to the roughness file that will be used by FENSAP for the next shot. To correct
this, change the roughness interpolation section in custom_remeshing.sh file in the multishot run
directory to the following:
if test -f roughness.dat.ice.$shot1

then

"$NTI_PATH/rough2rough" $GP roughness.dat.ice.$shot1

$GM roughness.dat.map.wall -bc=2 -field=20

"$NTI_PATH/rough2rough" $GI roughness.dat.map.wall

$GO roughness.dat.ice.$shot1.disp.wall -flat -bc=2 -field=20

"$NTI_PATH/rough2rough"

$GO roughness.dat.ice.$shot1.disp.screen -bc=6 -field=60

"$NTI_PATH/mergebcs" roughness.dat.ice.$shot1.disp.wall

roughness.dat.ice.$shot1.disp.screen roughness.dat.ice.$shot1.disp

rm -f roughness.dat.map.wall roughness.dat.ice.$shot1.disp.wall

roughness.dat.ice.$shot1.disp.screen

fi

(215362)

6.10. EnSight
• There may be a difference between the numbers of variables and their names as read into EnSight from
Fluent .cas/.dat files and from cas.h5/dat.h5 files because variables in the .dat file are all read and
named directly, while the dat.h5 is read through an ANSYS internal API which names the variables and
limits the variables that are exposed. (179522)

Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 17
 Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
18 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 7: ANSYS Electronics Products
For more entries specific to the Electronics Products, see the Known Issues and Limitations section of
the What's New in Electronics PDF distributed with the Electronics products.

7.1. Icepak
When creating non-uniform polygons, you must use SI units for top vertex coordinates. (195816)

Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 19
 Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
20 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 8: ANSYS Geometry & Mesh Prep Products

8.1. CAD Connections & Integration

There is a known problem importing sub-assemblies containing solid weld features through the Creo
Parametric Associative interface. In such cases weld bodies will not transferred and parts belonging to
the sub-assembly are incorrectly assigned the weld feature's name. The part names can be corrected
by suppressing the sub-assembly features prior to import. There is a work-around for missing weld
bodies available in DesignModeler. Multiple attaches can be performed, one for each sub-assembly
containing a solid weld feature. (166047)

8.2. DesignModeler
No known issues, limitations, or documentation inaccuracies.

8.3. Meshing
Weld controls do not allow to stop mesh during the meshing process. (209312)

All Weld controls may not create weld bodies when you generate mesh with large number of weld
controls. This could slow down the performance. (210164)

When you select Use Local Geometry Scoping in Repair Topology, you may encounter the following:

• Annotations may not work or can provide wrong information at times.

– Sharp Angle and Pinch Faces scoping have the same color annotation as Merge Faces scoping.

– When you select Geometry scoping in the Details view, only Merge Faces scoping is highlighted

• Incorrect scoping at times.

– The underlying geometry scoping may not update correctly with the Geometry CAD update.

• Scope changes are not handled well.

– When you use local scoping for Remove Thin Faces, Remove Sharp Angle and Pinch Faces options,
Scoping annotations appear even after turning off the local scoping for the same.

• When you use Named Selection for scoping in Repair Thin Faces, Repair Sharp Angle, Repair Pinch Faces
options, the scoping may error out.

(212946)

Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 21
ANSYS Geometry & Mesh Prep Products

8.4. IC Engine
No known issues, limitations, or documentation inaccuracies.

8.5. ICEM CFD

No known issues, limitations, or documentation inaccuracies.

Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
22 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 9: ANSYS Simulation Products

9.1. Workbench
No known issues, limitations, or documentation inaccuracies.

9.1.1. TurboSystem
ANSYS Workbench may encounter an error when you attempt to drag a Response Surface onto the
Project Schematic if the project contains either Vista AFD or Vista CCD (with CCM) systems. A potential
work-around is to remove the following DLLs from the ANSYS installation:

• ANSYS Inc\v201\Addins\TurboSystem\bin\Win64\libifcoremd.dll

• ANSYS Inc\v201\Addins\TurboSystem\bin\Win64\libifportmd.dll

• ANSYS Inc\v201\Addins\TurboSystem\bin\Win64\libmmd.dll

(199091)

9.2. System Coupling

• System Coupling does not support either the suppression of data transfer objects or the deletion of data
transfer objects for restarted coupled analyses. If performed, these operations cause the coupled analysis
to hang indefinitely.

Note that these operations are accessed in the different System Coupling contexts, as follows:

Suppress operation:

– System Coupling in Workbench: the Suppress context option

Delete operation:

– System Coupling in Workbench: the Delete context option

– System Coupling GUI: the Remove context option

– System Coupling CLI: the DeleteObject() command

Workaround: When running a restarted coupled analysis, avoid using these operations. (193036)

• If System Coupling is run on a cluster and the machine list is provided but the number of cores to be used
by System Coupling is not specified, then System Coupling does not use the default number of cores (two).
Instead, it runs on the all the cores reserved by the queuing system (i.e., those cores that are defined in the
machine list).

Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 23
ANSYS Simulation Products

Workaround: When running a coupled analysis on a cluster, ensure that System Coupling is started
using either the -s or the --sycnprocs command-line argument to specify the number of cores.
(212830)

• When a thermal-structural co-simulation that was solved using System Coupling in Workbench is restarted
from the final result, inconsistencies between Fluent and System Coupling setups regarding the use of
nodal vs. face/element data will cause the Fluent participant crash.

Workaround: When running a case of this description, review the Fluent and System Coupling setups
and ensure that both are using data from the same location — i.e., either both are using nodes, or
both are using faces/elements. Perform the appropriate migration steps, as described in Migrating
to Use Fluent Face/Cell Transfer Data in the System Coupling User's Guide, as needed. (216744)

9.3. ANSYS ACT

See the ACT Known Issues and Limitations documents on the App Developer Resources page of the
ANSYS Store.

9.4. ANSYS Minerva

When using the File Transfer Client to upload files, attempting to specify a destination folder from the
Search tab results in an error. If you are uploading to the Data section, use the Browse tab instead. If
you are uploading to a Work Request or Task, use the Upload function in the ANSYS Minerva application
instead of using the File Transfer Client. (211127)

9.5. Remote Solve Manager (RSM)

No known issues, limitations, or documentation inaccuracies.

9.6. DesignXplorer
ANSYS Workbench may encounter an error when you attempt to drag a Response Surface onto the
Project Schematic if the project contains either Vista AFD or Vista CCD (with CCM) systems. A potential
work-around is to remove the following DLLs from the ANSYS installation:

• ANSYS Inc\v201\Addins\TurboSystem\bin\Win64\libifcoremd.dll

• ANSYS Inc\v201\Addins\TurboSystem\bin\Win64\libifportmd.dll

• ANSYS Inc\v201\Addins\TurboSystem\bin\Win64\libmmd.dll

(199091)

Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
24 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 10: ANSYS Discovery

10.1. ANSYS Discovery SpaceClaim

When setting edge sizes for Bias method Height and ratio, the visual clues L and H can be a bit mislead-
ing. The L can be thought of as 1 to indicate the Height 1 and Ratio 1. The H can be thought of as 2 to
indicate the Height 2 and Ratio 2. (182678)

10.2. ANSYS Discovery Live

The steady state solver only supports turbulent problems. (217178)

10.3. ANSYS Discovery AIM

To ensure a consistent normal direction, AIM automatically corrects the contact normal directions for
shell-to-shell and shell-to-solid contacts. However, for manually created contacts with non-contiguous
surface selections, the automatic correction may not achieve a consistent normal direction for the
contact surfaces. Use Modeling to ensure a consistent normal direction for manually created contacts
with non-contiguous face selections. (153273)

Selection of Enable constraint based sketching when Super Sketch is active may result in a system failure.
Work-around: Clear the application data to disable Super Sketch. (193068)

Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 25
 Release 2020 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
26 of ANSYS, Inc. and its subsidiaries and affiliates.