Known Issues and Limitations

ANSYS, Inc. Release 2021 R1

Southpointe January 2021
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

© 2021 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
2. Installation .............................................................................................................................................. 3
3. Licensing ................................................................................................................................................. 5
4. Documentation ....................................................................................................................................... 7
5. ANSYS Structural Products ..................................................................................................................... 9
5.1. Mechanical ....................................................................................................................................... 9
5.2. Mechanical APDL .............................................................................................................................. 9
5.3. Autodyn ........................................................................................................................................... 9
5.4. Aqwa ................................................................................................................................................ 9
5.5. ANSYS Composite PrepPost (ACP) ..................................................................................................... 9
5.6. Material Designer ............................................................................................................................. 9
5.7. Additive Manufacturing .................................................................................................................. 10
5.8. Sherlock ......................................................................................................................................... 10
6. ANSYS Fluids Products .......................................................................................................................... 11
6.1. Fluent ............................................................................................................................................. 11
6.1.1. Meshing Mode ....................................................................................................................... 11
6.1.2. Solution Mode ....................................................................................................................... 11
6.1.3. Client Applications ................................................................................................................. 13
6.2. CFX ................................................................................................................................................ 13
6.3. TurboSystem and TurboGrid ............................................................................................................ 13
6.4. BladeModeler ................................................................................................................................. 14
6.5. CFD-Post ........................................................................................................................................ 14
6.6. Polyflow ......................................................................................................................................... 14
6.7. Forte .............................................................................................................................................. 14
6.8. Chemkin-Pro .................................................................................................................................. 14
6.9. FENSAP-ICE .................................................................................................................................... 14
6.10. EnSight ......................................................................................................................................... 14
7. ANSYS Electronics Products .................................................................................................................. 17
7.1. Icepak ............................................................................................................................................ 17
8. ANSYS Optical Products ........................................................................................................................ 19
8.1. ANSYS SPEOS .................................................................................................................................. 19
8.2. SPEOS for NX .................................................................................................................................. 19
8.3. SPEOS for Creo Parametric .............................................................................................................. 20
9. ANSYS Systems Products ...................................................................................................................... 21
9.1. VRXPERIENCE Sound ....................................................................................................................... 21
10. ANSYS Geometry & Mesh Prep Products ............................................................................................ 23
10.1. CAD Connections & Integration ..................................................................................................... 23
10.2. DesignModeler ............................................................................................................................. 23
10.3. Meshing ....................................................................................................................................... 23
10.4. IC Engine ...................................................................................................................................... 23
10.5. ICEM CFD ...................................................................................................................................... 23
11. ANSYS Simulation Products ................................................................................................................ 25
11.1. ANSYS ACT ................................................................................................................................... 25
11.2. Distributed Compute Services (DCS) .............................................................................................. 25
11.3. DesignXplorer ............................................................................................................................... 25
11.4. optiSLang ..................................................................................................................................... 25
11.5. Remote Solve Manager (RSM) ........................................................................................................ 25

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. iii
Known Issues and Limitations *

11.6. System Coupling ........................................................................................................................... 25

11.7. Workbench ................................................................................................................................... 26
12. 3d Design Products ............................................................................................................................. 27
12.1. ANSYS SpaceClaim ........................................................................................................................ 27
12.2. ANSYS Discovery ........................................................................................................................... 27

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

Initial release

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. v
 Release 2021 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 2021 R1. The entries describe known non-
operational behavior, an error, or limitation at the time of this release. Workarounds 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 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. vii
 Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
viii of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 1: Advisories
No known issues, limitations, or documentation inaccuracies.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 1
 Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
2 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 2: Installation
• The Chemkin option is included in the Ansys Workbench "Toolbox" even when the Chemkin product
is not installed, causing an error when Ansys Workbench tries to communicate with the application.
(364306)

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 3
 Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
4 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 3: Licensing
• During up-front HPC parametric sharing, when non-solver features are requested, the applications
might check out more parallel licenses than required. (345957)

• When running the Gather Diagnostics option in the Client Settings Utility the file containing the
Windows system information (ansyssys.nfo) is missing. (360803)

• Canceling an action the FlexNet Publisher page of the Client Settings Utility does not let user enter
new text. (363290)

• You are unable to set the client licensing server in the Client Settings Utility if hostname contains a
hyphen. (365837)

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 5
 Release 2021 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 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 7
 Release 2021 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
If you see the following messages when you launch Mechanical or DesignModeler or Meshing Editor,
set the environment variable TERM=xterm and make sure your version of krb5-libs is not newer than
krb5-libs-1.17-9.

• MwSetTmpFilesDir failed to retrieve data for user id 1783. errno = 2

• MwSetTmpFilesDir failed to retrieve data for user id 1783. errno = 2

• MwSetTmpFilesDir failed to retrieve data for user id 1783. errno = 25 (342299)

For metal fraction calculation when Icepak is run remotely via remote access software, GPU-based
metal fraction calculation may not work correctly. It's recommended that you disable GPU-based metal
fraction calculation in the Icepak preferences dialog or define an environment variable ICEPAK_USE_GRID-
CUT_LEGACY and set its value to 1. (348795)

5.2. Mechanical APDL

No known issues, limitations, or documentation inaccuracies.

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

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

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.

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

5.7. Additive Manufacturing

Additive Prep

• The Slice Viewer may not show all the layers in a Renishaw build file if certain unrepresented scan
vector types are encountered. This limitation is geometry-dependent, possibly for complex models
with uncommon scan vector types. The slice slider shows a limited number of layers and the slice
numerical input field is limited to 100. All layers are written in the build file, however, so you can
view the build file with other software for visual confirmation. (369258)

ANSYS Additive (Print and Science)

• No known issues, limitations, or documentation inaccuracies.

Workbench Additive

• No known issues, limitations, or documentation inaccuracies.

5.8. Sherlock
No known issues, limitations, or documentation inaccuracies.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
10 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 2021 R1.

6.1.1. Meshing Mode

No new issues, limitations, or documentation inaccuracies.

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

6.1.2. Solution Mode

Licensing

• (Operating under the Pro license) While the user-defined specification method is available for
some fields, such as material properties, you cannot load user-defined functions, as they are not
supported at the Pro capability level. (321331)

Graphics Display

• Dragging the ANSYS Fluent application between 4K and non-4K displays may result in the application
not scaling correctly. As a workaround, restart ANSYS Fluent after relocating it to a new screen to
make it appear as expected. (345352)

• (Linux only) ANSYS Fluent does not support AMD Radeon Pro graphics cards and the Fluent session
may close unexpectedly. (348500)

Embedded Graphics

• Images of embedded graphics windows captured using the Save Picture dialog box are saved
without borders on the embedded windows, regardless of the setting specified in Preferences.
(336851)

Graphics, Reports, and Postprocessing

• For pictures saved at higher resolutions (4K or higher) with -driver null, the title lines may
not appear as thick as desired. (154730)

• (Linux only) Contour lines are not displayed when dynamic shadows are enabled. To make the
contour lines display, you can disabled dynamic shadows either in the graphics window toolbar or
in Preferences. (343770)

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

System Coupling

• When the Fluent solver is called by System Coupling for a transient simulation, and transient results
are requested through the System Coupling Output Control functionality, those files are not
written to the Fluent common file format project file. To workaround this issue, please set the
Fluent autosave frequency to be consistent with the System Coupling Output Control details.
(286923)

Solver Meshing

• (Fluent in Workbench only) One-to-one mesh interface creation is not the default method, because
it is not recorded correctly for future updates. If you enable one-to-one mesh interface creation,
the automatic update of the Setup and Solution cells will not proceed appropriately. As a work-
around, create mesh interfaces manually. (313084)

Expressions

• Expressions computing forces or moments will not display the value in the same units as a force
or moment report definition for the same quantity. For example, an expression for a moment will
be printed in units of [(kg m^2)/s^2] whereas a moment report definition will display the
value in units of [N m]; these are equivalent units, which you can confirm by converting to base
units. Similarly, an expression computing force, will display the value in [kg m s^-2], while a
force report definition will display the value in [N]. (302469)

Solver

• If you have enabled the application of poor mesh numerics using criteria based on the cell gradient
quality, the number of cells to which it is applied may vary when performing single-precision cal-
culations with different numbers of processes. Workaround: Use the double-precision solver.
(362753)

Fluent in Workbench

• (Linux only) You may observe some error messages printed to the console regarding HDF5 when
you update your Solution cell. These error messages are harmless and can be safely ignored.
(354856)

• (Windows only) For the Fluent (with Fluent Meshing) component system, design point studies
using the Remote Solve Manager with Microsoft HPC, may not completely update all design
points. Should this happen, you can rerun the affected design points and they will update as ex-
pected. (350696)

• In a Workbench project, if your Fluent case and data files are in the default common fluids format
(CFF) and you also export a .cdat file, you may get an error message if you attempt to postprocess
the results using CFD-Post. This is because when a .cdat file is exported, a legacy case file (.cas)
is also written as the latest case, and so paired with the CFF data file (.dat.h5), and it is not
possible to use a combination of legacy and CFF files in CFD-Post. Workaround: Manually write a
new .cas.h5 and .dat.h5 file after the .cdat file is exported. (310992)

Job Schedulers

• (Windows only) If you use the Microsoft Job Scheduler with Windows Server 2016 to start Fluent
across multiple machines (with the host on one machine and compute nodes on others) and then

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
12 of ANSYS, Inc. and its subsidiaries and affiliates.
 TurboSystem and TurboGrid

write case / data files through the text user interface, the I/O mode will be incorrectly changed
from HOST mode to NODE0 mode, and the files will be written to the current working directory
on the machine where the compute-node-0 is. For example, if you close a Fluent session in
Workbench, the case and data files will automatically be written to the compute-node-0 working
directory rather than the usual default directory (such as Workbench_file-
name_files\dp0\FLU\Fluent). Workaround: Use Windows Server 2019. (360850)

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

6.1.3. Client Applications

Fluent Icing

• If a Fluent case file contains mapped interfaces (such as in a Conjugate Heat Transfer scenario, in
which a single subdomain is selected for icing simulations), the Fluent solver might reorder the
nodes when the CPU count is changed, and the case is saved. Node reordering will invalidate any
prior nodal solutions written by the icing solvers. To avoid node reordering by the Fluent solver,
the suggested practice is to always use the same number of CPUs in Fluent Icing than the number
used to save the case file that was imported to Fluent Icing. (372217)

• The EID solver step cannot be interrupted, the interrupt command will be effective only at the end
of the EID computation. (372220)

• Selecting a post-processing option from the Quick-view ribbon automatically creates a Quick-view
entry in the Outline View. Deleting this Quick-view entry will prevent later Quick-view options
from the ribbon to work. (372221)

• Path with spaces either in the project path or in the case file name are not currently supported
with the post-processing tools (CFD-Post, EnSight), and should be avoided. (372223)

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

6.2. CFX
The timing diagnostics reported in the solver output file under the heading 'CPU Time Requirements
of Solver' are missing for subsystem groups (e.g. 'Mass and Momentum'). The total reported for 'Miscel-
laneous' includes the discretization and solution time for all subsystem groups and is correspondingly
higher. By using the expert parameter setting 'timing output level = 2', the missing information can be
found as part of a more detailed timing diagnostic. (370799)

6.3. TurboSystem and TurboGrid

If Vista TF does not run after setting the license server using the client licensing utility then, as a work-
around, you can manually add the following line to ansyslmd.ini:

ANSYSLI_SERVERS=2325@<license_server>

(368904)

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

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

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

6.6. Polyflow
No known issues, limitations, or documentation inaccuracies.

6.7. Forte
Due to an incompatibility issue with OpenGL, some AMD Radeon graphics cards (such as AMD Radeon
Pro WX5100) may cause application crashes or display issues when running under Linux operating
systems. (348489)

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

6.9. FENSAP-ICE
• Ice Cover in CFD-Post and Ice Numbered Solutions

A sequence of numbered output solution files of ICE3D is not currently supported by the Ice Cover
macro of CFD-Post. Only individual solutions can be used with this macro. (372252)

• Remeshing Scripts and Fluent Meshing Script Cross-Platform Compatibility

In ICE3D, the remeshing scripts set-up for the grid displacement mode Remeshing - Fluent Meshing
are not portable across platforms. The custom_remeshing.sh file needs to be converted to the
suitable platform text file format. Alternatively, the remeshing template files can simply be reloaded
using the Template - Reload template located in the ICE3D grid displacement menu. (372256)

6.10. EnSight
• When reading Overset solutions from a Fluent Restart file (.cas.h5/.dat.h5), the variable value
for Overset_Cell_Type for boundaries (2D parts in 3D volume, or 1D parts in 2D simulation) is
not returned correct through the CFF API. This will cause boundary parts to incorrectly disappear
when applying the Overset_Cell_Type filtering (typically used to correctly visualize surfaces in
the overset domain). You are suggested to utilize the Common Fluids Post file format (CFF Post;
.cas.post/.dat.post) for handling the post processing of Overset Domains. (323381)

• There has been a recent change in the convention used to denote the direction of the wall shear
force from Fluent. EnSight has not yet adjusted to this change in convention, and therefore may show

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

the vector direction for wall shear opposite to that reported by Fluent. EnSight will update to the
current convention for 2021R2. (352286)

Workaround: You can multiply the shear force vector by -1 to align with the convention used by
Fluent.

• Handling of Overset_Cell_Type values for 2D Parts needs to return proper value (not undefined or
incorrectly zero). Today, all values are returned as zero. (323381)

• On some Linux systems and in certain remote desktop configurations, the EnSight, EnVe, EnVision
and Nexus tools may not be able to find the desired typefaces for use in graphical user interfaces. In
these cases, the graphical user interface may come up, but user interface text is displayed in a
monospaced or serifed typeface. The most common situation is when a server focused Linux install
(without a complete set of desktop packages) is used to host an application session over a remote
rendering solution like vncserver or DCV. There are a couple of ways to work around this issue. First,
one may install a set of desktop packages (for example, Gnome or KDE) on the system which will
usually fix the issue. Second, there is a command line flag ‘-distfonts’ that can be included on the
EnSight (or other tool) command line. This flag causes the graphical user interface tools to ignore
the fonts installed in the operating system, using instead the base fonts included in the EnSight
package. A third option would be to modify the system’s fontconfig configuration files to provide
an alias for the typeface ‘sans serif’, such as:
<match target="pattern">
<test qual="any" name="family">
<string>sans serif</string>
</test>
<edit name="family" mode="assign" binding="same">
<string>Arial</string>
</edit>
</match>

(316429)

• When attempting to export deep pixel images, in batch, on Linux, to a nexus report, EnSight may
stop working. Changing any one of those aspects (not deep pixel, not batch, not Linux) will allow
successful operation. (362022)

• When using a remote desktop protocol (for example, RDP/VDI/DCV), in combination of sending 3D
scenes to a Nexus report, the Report Tab in EnSight is unable to display the 3D scene correctly. This
appears to be further isolated to allocations which do not support GPU of WebGL rendering. The report
itself is correct, and the issue is isolated to viewing of the report only. Users will need to view that
report on a system which supports GPU rendering and WebGL. (291848)

• When using the ANSYS CFF Post reader, in the context of a currently running transient solution, the
option in EnSight for Monitor New Timesteps does not properly load the variables from the new
timesteps correctly. You will need to turn off the Monitor New Timesteps control to properly read
the files. (291365)

• When parts had been selected, then de-selected by a left mouse click in the viewport, the part list
will be de-selected (correctly). However, the Part Object List may still show parts being selected (when
they are not). The workaround is to ensure part selection prior to operations, or invoke a ‘en-
sight.refresh()’ in the python terminal window to force an update to the Part Object List
display. (364438)

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

• In the Contour Feature Detail Editor, when selecting the variable to use for creation of the Contour,
the Variable Selection dialog can get hung up on a single variable, not allowing you to change the
selection. This only occurs in the Create mode of the dialog. If this does happen, there is a workaround
to Create the Contour with the frozen variable. Once created, (you are now in the Edit mode of the
dialog), you can correctly change/update the variable selection to the correct variable. (365993)

• Plotter names can incorrectly end up as duplicates of other plotters which will cause the incorrect
restore of states. You can manually rename the plotters to separate names and re-save the state.
Restoring the states will then occur properly. (365859)

• There is a missing Create Annotation option when right-clicking a constant in the variable object
list. You can simply left-click and drag the constant onto the viewport to create the annotation, or
use the Annotation Creation operation and insert the constant variable into the annotation creation.
(366449)

• When using datasets with mid side nodes (for example, higher ordered elements), along with the
new Filter Part capability in 2021 R1, EnSight does not handle the combination of mid side node and
Filter Part correctly, causing it to exit. The previous Element Filtering capability for model parts can
be correctly utilized still, and this may provide a suitable workaround for most situations where element
filtered is required. (368407)

• Using the existing LS-Dyna legacy reader, the values reported on Beam elements for RS Shear stress,
TR Shear stress and Axial Stress have been interchanged, and thus are being read in the wrong order.
You can re-interpret them in the correct order, but must do so manually. (368715)

• When using the Sweep Source control within nexus integration within EnSight, the interactive control
is correct. However, the recording of this sweep control to the command file is missing, and therefore
playback of the command file will not correctly re-create the sweep source. The workaround for this
issue is to ensure that the Beta Flag is set (set the environment flag to ENSIGHT_ANSYS_BETA_FLAG
= 1). (368905)

• When attempting to save/read context files with multiple cases, there are various instabilities with
the handling of parts. This can affect both the save of the context file, as well as the read.

As a potential workaround, if you are experiencing problems reading in context files with multiple
cases, you may be able to bypass the issue of part handling by first loading the multiple cases, and
then restoring the context file (as opposed to loading the cases as a result of restoring the context
from scratch). (363417)

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
16 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
While running Icepak using Remote Solve Manager on Workbench, Icepak does not support running in
the background. (311506)

For metal fraction calculation when Icepak is run remotely via remote access software, GPU-based
metal fraction calculation may not work correctly. It's recommended that you disable GPU-based metal
fraction calculation in the Icepak preferences dialog or define an environment variable ICEPAK_USE_GRID-
CUT_LEGACY and set its value to 1. (348795)

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 17
 Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
18 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 8: ANSYS Optical Products
8.1. ANSYS SPEOS
Groups are not compatible with components but with geometries only. (339069)

Materials fail to be taken into account by the simulation when they contain geometry groups. (339263)

A manual update of SPEOS elements may be required after having exploded an associated group.
(349931)

When a geometry presents construction issues, the tessellation might fail and prevent the simulation
from being computed. (361835)

Point selections are not persistent when using the Geometry update feature. When editing the origin
point of a SPEOS element and performing a Geometry Update, the element might fail to be placed
on the updated origin point location. (202601)

In some cases, ambient sources are not correctly oriented in the simulation result. (363205)

When visualizing camera sensor results, the spectral irradiance map may show some circular artefacts.
(334136)

Simulation results fail to be generated when a LiDAR sensor is placed in a sub component that is itself
nested in a sub component. The LiDAR must be placed on the assembly or sub component level only.
(370392)

The 3D view visualization may not be functional for the camera sensor, the interactive source, the
thermic source and 3D texture elements. (336422)

Modifying OPD features that are based on the automatic update mechanism (i.e.Parabolic Surface, TIR
Lens, Projection Lens) used as input geometries of SPEOS objects disables the automatic refresh of
SPEOS tree. Workaround: Refresh the tree manually after each SPEOS operation or restart ANSYS SPEOS
to restore the automatic refresh of SPEOS tree. (368779)

Volume Optical Properties are silently ignored for simulation when applied on surface geometries. As
a result, they are noted as unused in the simulation report. (372852)

8.2. SPEOS for NX

When visualizing camera sensor results, the spectral irradiance map may show some circular artefacts.
(334136)

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 19
ANSYS Optical Products

On NX version 12, a looping error prevents from launching SPEOS if the license server has been turned
Off from the ANSYS License Manager. Workaround: Close SPEOS for NX, turn the license server On and
reopen the application. (349374)

8.3. SPEOS for Creo Parametric

When visualizing camera sensor results, the spectral irradiance map may show some circular artefacts.
(334136)

In some cases, sources or sensors might not be visible in the 3D view when opening the project.
Workaround: Edit the SPEOS item or regenerate it to trigger the 3D view visualization. (362909)

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
20 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 9: ANSYS Systems Products
9.1. VRXPERIENCE Sound
ASDforEV does not close properly. Workaround: From Windows Task Manager, end the process ASD-
forEV.exe. (354155)

ASDforEV CAN reader does not close properly. Workaround: From Windows Task Manager, end the
process ASDforEVCANreader.exe.(353457)

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 21
 Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
22 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 10: ANSYS Geometry & Mesh Prep Products
10.1. CAD Connections & Integration
No known issues, limitations, or documentation inaccuracies.

10.2. DesignModeler
If you see the following messages when you launch Mechanical or DesignModeler or Meshing Editor,
set the environment variable TERM=xterm and make sure your version of krb5-libs is not newer than
krb5-libs-1.17-9.

• MwSetTmpFilesDir failed to retrieve data for user id 1783. errno = 2

• MwSetTmpFilesDir failed to retrieve data for user id 1783. errno = 2

• MwSetTmpFilesDir failed to retrieve data for user id 1783. errno = 25 (342299)

10.3. Meshing
When multiple bodies are meshed using selective meshing in the Geometry tree, mesh is generated
only for one body and skips the rest. You must select the bodies in the Geometry window and generate
mesh for the selected bodies. (358470)

When you apply Inflation controls in the Model tree or enable Inflation group in the Mesh Details view
after applying Mesh Refinement controls, the mesh refinement is not suppressed automatically and
generates invalid mesh. You have to suppress the Mesh Refinement control manually to avoid mesh
failure. (364668)

In the worksheet for weld creation, you can turn off the Number of Layers by providing the value zero.
When you save and resume the project, the Number of Layers defaults to one. You must manually enter
the Number of Layers as zero every time you resume the project. (367441)

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

10.5. ICEM CFD

No known issues, limitations, or documentation inaccuracies.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 23
 Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
24 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 11: ANSYS Simulation Products
11.1. ANSYS ACT
See the ACT Known Issues and Limitations documents on the App Developer Resources page of the
ANSYS Store.

11.2. Distributed Compute Services (DCS)

Failed evaluations of Workbench process steps in DCS design points can be wrongly marked with a
"successful" evaluation status. If this occurs, output parameter values shown in DCS will then not be
updated correctly, showing initial values stored in the Workbench project from before the update instead.
(368508)

11.3. DesignXplorer
No known issues, limitations, or documentation inaccuracies.

11.4. optiSLang
If both parametric and non-parametric optiSLang systems are used in a Workbench project, there are
also two separate optiSLang projects for this workflow. Each of these optiSLang projects requires its
own license. This leads to license errors if you only have access to a single license. (317394)

11.5. Remote Solve Manager (RSM)

Updating a Workbench project with Mechanical design points through Remote Solve Manager (RSM)
can cause the following error in the RSM log:

[ERROR] OpenClientAndConnect failed because portToListen is invalid: 0

This error is thrown by mistake and can be ignored. (367276)

11.6. System Coupling

System Coupling's "Export Setup from Workbench" operation is not supported for System Coupling
v1.0. If you attempt to export a coupling setup from a coupled analysis created using System Coupling
v1.0, the export will fail, and no content will be exported.

To address this issue, use the following workaround:

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

1. Update engine settings for each System Coupling system on the Project Schematic:

a. Double-click the system's Setup cell to open its System Coupling tab.

b. In the Outline, click Execution Control.

c. In the Properties pane, set Coupling Engine to 2.0.

2. Regenerate the System Coupling Input file by selecting Select File > Export SCI File.

3. Perform the export operation.

(368452)

11.7. Workbench
Updating a Workbench project with Mechanical design points through Remote Solve Manager (RSM)
can cause the following error in the RSM log:

[ERROR] OpenClientAndConnect failed because portToListen is invalid: 0

This error is thrown by mistake and can be ignored. (367276)

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
26 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 12: 3d Design Products
12.1. ANSYS SpaceClaim
No known issues, limitations, or documentation inaccuracies.

12.2. ANSYS Discovery

When running Discovery on a Dell 7550 laptop with NVIDIA Quadro graphic cards RTX4000, T1000 or
M3000M, the graphics driver may crash preventing Discovery from rendering a model (3D scene).
Workaround: Disable integrated graphics in BIOS. (336591)

When running a fluid-solid heat transfer simulation with a heat source or sources on solid thermal
bodies, the heat flow value includes the source(s) in W. The monitor chart generated for heat flow,
however, is correct. (363831)

When viewing mesh in Refine, as the mesh gets fine on a specific body you may not be able to view
the volume elements. (362105)

Certain graphics cards give an illegal memory access error when some fluid cases are set at a high fidelity.
(365071)

If you duplicate a Topology Optimization simulation, even if you modify the conditions on the simulation,
the original solution is solved rather than the duplicate, and no results display in monitors at end of
solve. In addition, if the duplicate Topology Optimization simulation contains a Mass monitor, an excep-
tion error is thrown at each iteration of the solve. Workaround: Disable and re-enable Topology Optim-
ization in the duplicate simulation. (365930)

When the default mesh size is computed during the Refine stage, all bodies in the model are included,
including bodies that are suppressed. This may lead to an inappropriate default mesh size. Workaround:
Delete the suppressed bodies or make local fidelity adjustments. (369524)

In the Refine stage, mechanical solutions fail if spaces appear in the path to the Windows %temp%
folder. No results are returned, and no error is issued in the user interface. For example, the following
configuration will cause the solution to fail:

C:\Users\Visitor Test>set TEMP

TEMP=C:\Users\Visitor Test\AppData\Local\Temp

Workaround: Remove the spaces from the %temp% path and solve again. For example, if the username
contains spaces as shown above, remove the spaces from the username by creating a new user account
on the machine. (370377)

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 27
 Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
28 of ANSYS, Inc. and its subsidiaries and affiliates.