Ansys Inc. Known Issues and Limitations

Known Issues and Limitations
ANSYS, Inc. Release 2022 R1

Southpointe January 2022
2600 Ansys Drive ANSYS, Inc. and
Canonsburg, PA 15317 ANSYS Europe,
Ltd. are UL
ansysinfo@ansys.com registered ISO
http://www.ansys.com 9001: 2015
(T) 724-746-3304 companies.
(F) 724-514-9494
Copyright and Trademark Information
© 2022 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 ......................................................................................................................................... 10
5.4. Aqwa .............................................................................................................................................. 10
5.5. Ansys Composite PrepPost (ACP) ..................................................................................................... 10
5.6. Material Designer ........................................................................................................................... 10
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 ................................................................................................................. 12
6.2. CFX ................................................................................................................................................ 13
6.3. TurboSystem and TurboGrid ............................................................................................................ 13
6.4. BladeModeler ................................................................................................................................. 13
6.5. CFD-Post ........................................................................................................................................ 13
6.6. Polyflow ......................................................................................................................................... 13
6.7. Forte .............................................................................................................................................. 13
6.8. Chemkin-Pro .................................................................................................................................. 13
6.9. FENSAP-ICE .................................................................................................................................... 13
6.10. EnSight ......................................................................................................................................... 14
7. Ansys Electronics Products ................................................................................................................... 17
7.1. Icepak ............................................................................................................................................ 17
8. Embedded Software ............................................................................................................................. 19
8.1. Scade ............................................................................................................................................. 19
9. Ansys Optical Products ......................................................................................................................... 21
9.1. Ansys Speos .................................................................................................................................... 21
9.2. Ansys Speos for NX ......................................................................................................................... 21
9.3. Ansys Speos for Creo Parametric ..................................................................................................... 21
9.4. Ansys Speos Labs ............................................................................................................................ 22
9.5. Ansys Speos HPC ............................................................................................................................ 22
10. Ansys Acoustics Products .................................................................................................................... 23
11. Ansys Systems Products ...................................................................................................................... 25
11.1. AVxcelerate Data Preparation and VRXPERIENCE VR ....................................................................... 25
11.2. AVxcelerate Sensors Simulator ....................................................................................................... 25
12. Ansys Geometry and Mesh Prep Products .......................................................................................... 27
12.1. CAD Connections & Integration ..................................................................................................... 27
12.2. DesignModeler ............................................................................................................................. 27
12.3. Meshing ....................................................................................................................................... 27
12.4. ICEM CFD ...................................................................................................................................... 27
13. Safety Analysis .................................................................................................................................... 29
Release 2022 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. iii
Known Issues and Limitations *
13.1. Medini .......................................................................................................................................... 29

14. Ansys Simulation Products ................................................................................................................. 31
14.1. Ansys ACT ..................................................................................................................................... 31
14.2. Distributed Compute Services (DCS) .............................................................................................. 31
14.3. DesignXplorer ............................................................................................................................... 31
14.4. optiSLang ..................................................................................................................................... 31
14.5. Remote Solve Manager (RSM) ........................................................................................................ 32
14.6. System Coupling ........................................................................................................................... 32
14.7. Workbench ................................................................................................................................... 32
15. 3d Design Products ............................................................................................................................. 35
15.1. Ansys SpaceClaim ......................................................................................................................... 35
15.2. Ansys Discovery ............................................................................................................................ 35
iv of ANSYS, Inc. and its subsidiaries and affiliates.
Revision History
January 2022
Initial release
of ANSYS, Inc. and its subsidiaries and affiliates. v
vi of ANSYS, Inc. and its subsidiaries and affiliates.
Introduction
The following information is relevant to ANSYS, Inc. Release 2022 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.
of ANSYS, Inc. and its subsidiaries and affiliates. vii
viii of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 1: Advisories
No known issues, limitations, or documentation inaccuracies.
of ANSYS, Inc. and its subsidiaries and affiliates. 1
2 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 2: Installation
Chapter 3: Licensing
Chapter 4: Documentation
Ansys Help, on Linux in a DCV environment, cannot be launched from Firefox for the products CFX,
EnSight, and Polyflow. (459559)
Chapter 5: Ansys Structural Products
Select from the following products to review known issues and limitations. Problem scenarios are de-
scribed and when possible, a solution to the issue is provided.
5.1. Mechanical
5.2. Mechanical APDL
5.3. Autodyn
5.4. Aqwa
5.5. Ansys Composite PrepPost (ACP)
5.6. Material Designer
5.7. Additive Manufacturing
5.8. Sherlock
5.1. Mechanical
When you complete a solution using Distributed Compute Services (DCS) and then you change an object
that requires you to re-solve the analysis, the context (right-click) menu option Get Results may not
operate correctly. Workaround: To make sure the Get Results option executes correctly, you can perform
one of three options:
• Select the Solution object (instead of a result object) and perform the Get Results operation.
• First use the context (right-click) menu option Clear Generated Data for the selected result
object and then select Get Results.
• Clean and re-solve the analysis.
(553666)
5.2. Mechanical APDL

• When relinking a custom Mechanical APDL executable using ans_admin221, be aware that the
ANSCUSTOM script included in the Ansys installation for release 2022 R1 incorrectly names the
download file for the GCC compiler as linux-toolchain-8.2.0-01.zip. The correct name of this
download file at release 2022 R1 is GCCCOMPILER_820_LINX64.tgz. For detailed instructions, see
1.9.4. Downloading and Installing the GCC Compiler in the 2022 R1 version of the Mechanical APDL
Programmer’s Reference. (550220)
• The auto-hybrid heuristics, designed to automatically enable hybrid parallel to improve performance,
may result instead in degraded performance in some cases. This is more likely to occur for simulations
that involve the sparse direct solver and require more memory to run in the in-core memory mode
than is physically available in the machine. Additionally, simulations containing a majority of beam
Ansys Structural Products
and/or shell elements in the model may be impacted by this issue. Workaround: Disable auto-hybrid
and run with distributed-memory parallel processing by forcing one thread per process (-nt 1 on the
command line). (554557)
5.3. Autodyn
5.4. Aqwa
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

General Material Designer and release-specific limitations can be found in Known Limitations section
of the Material Designer User's Guide.
5.7. Additive Manufacturing

Additive Prep
• No known issues, limitations, or documentation inaccuracies.
Ansys Additive (Print and Science)
Workbench Additive
5.8. Sherlock
When exporting a CCA to Electronics Desktop, the specific heat property will not be set for composite
materials. (538707)
Chapter 6: Ansys Fluids Products
6.1. Fluent
The following sections list new or recently discovered limitations known to exist in version 2022 R1.
6.1.1. Meshing Mode

Mesh Generation
• With the Rapid Octree mesher, the use of the default distributed geometry handling with high core
counts (usually > 300) may cause Fluent to terminate abnormally. Workaround: either reduce the
number of cores or, if there is sufficient memory on the compute nodes, disable the distributed
geometry handling using the following text command: /mesh/rapid-octree/distribute-
geometry? no. (548350)
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

Graphics Display
• (Linux only) Ansys Fluent does not support AMD Radeon Pro graphics cards and the Fluent session
may close unexpectedly. (348500)
Graphics, Reports, and Postprocessing
• If Enhanced Plots are enabled in Preferences (under Charts in the Appearance branch) and you
create a solution animation for the charts using In Memory for the Storage Type, then writing
out Animation Frames, Picture Files, or a Video File during animation playback will fail with an
error. As a workaround, you can use one of the image options for Storage Type in the Animation
Definition dialog box. (542241)
• Reported wall statistics specified in the Sampling Options dialog box use data interpolated from
cell centers to the wall, rather than face values, which may result in values that are incorrect. As a
workaround, use the statistics setup in the Zone-Specific Sampling Options dialog box, which
correctly uses face values, where appropriate. (520182)
Discrete Phase Model
• Automatic export of particle data to the EnSight Case Gold format during transient time stepping
works only when the Separate Files for Each Time Step option is enabled in the Automatic
Particle History Data Export dialog box when creating an automatic export definition for particle
history data. Otherwise, the exported files will not be valid for the EnSight Case Gold reader. (548227)
Ansys Fluids Products
Solver Meshing
• When using the gap model with a flow-blocking gap region or when using contact detection in a
dynamic mesh with the contact marks method selected for flow control, you must ensure that none
of the cells that are marked as part of the blocked region are adjacent to a periodic boundary zone,
as this will result in Fluent reporting an error during initialization or the calculation. (498569)
• When slitting a coupled wall, Fluent will terminate abnormally if the coupled wall includes a node
that is also shared by two or more periodic boundary zone pairs. Note that a slitting operation is
performed not only when you use the mesh/modify-zones/slit-face-zone text command,
but also when you specify a time-averaged explicit thermal coupling (for example, by using the
define/models/cht/explicit-time-averaged-coupling/conformal-coupled-
walls text command). Workaround: decouple all of the periodic pairs that share the node (for
example, by using the define/boundary-conditions/modify-zones/slit-periodic
text command) before you slit the coupled wall. (528636)
Fluent in Workbench
• Fluent design point studies using the Remote Solve Manager may not completely update due to
errors. Should this happen, you can rerun the affected design points and they will update as expected
(you may have to rerun failed design points multiple times). (350696, 385734)
• Workbench may close unexpectedly if you are running on a Windows Server 2016 machine. If you
experience this behavior, define the following environment variable to avoid the issue:
HDF5_USE_FILE_LOCKING=FALSE. Refer to https://support.hdfgroup.org/ftp/HDF5/releases/
ReleaseFiles/hdf5-1.10.1-RELEASE.txt for additional background information. (542550)
ACT
• In some cases, you may see a warning when accessing Preferences after loading ACT at startup.
As a workaround to open Preferences, close Fluent, disable Load ACT in the Fluent Launcher and
start Fluent. Once Fluent is running you can modify Preferences and click OK to save your changes.
(462205)
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 Aero
• When a new aero workflow is created using a .msh or .msh.h5 file, Fluent Aero will import, convert,
and save this file to a .cas.h5 file inside the simulation folder. In some instances, during the import
process, the file save operation can fail even if the case file is properly loaded into Fluent Aero. If
this occurs, the .cas.h5 file can be saved to the Simulation folder by Calculating a design point or
by using the Save Case command. (557317)
Fluent Icing
• When setting pressure-inlet boundary conditions using Edit mode, the field names Temperature
[K] and Gauge Pressure [Pa] are misleading as they indicate that static conditions are required.
Instead, these entries set total conditions at the pressure-inlet, in other words theTotal Temperature
in K and the Gauge Total Pressure [Pa] in Pa. (557415)
FENSAP-ICE
6.2. CFX
6.3. TurboSystem and TurboGrid

6.4. BladeModeler
6.5. CFD-Post
6.6. Polyflow
6.7. Forte
All replay files must be used with projects produced in the same release of Forte. If the replay file and
project are from different releases, the settings in the replay file will be implemented in an unpredictable
manner. (554625)
6.8. Chemkin-Pro
The data files (sample) associated with the tutorial, "Chemkin-Pro as a Workbench Component: Optim-
ization of IC Engine Performance and Emissions" are incorrectly flagged as Beta version in the Chemkin-
Pro install and cannot be used. Workaround: Use the downloadable version. Access the download from
the Chemkin-Pro 2022 R1 page at the Ansys Help website or from the section, "Data Provided," in the
chapter "Chemkin-Pro as a Workbench Component: Optimization of IC Engine Performance and Emissions"
in the Chemkin-Pro Chemkin-Pro Tutorials. (554714)
6.9. FENSAP-ICE
In the 1st Ice Prediction workshop, Wright's SLD rebound model implemented in FENSAP-ICE is reported
to produce very different results when compared to LEWICE3D on the horizontal tail case. The LEWICE3D
solution is in good agreement with the experimental data for this case. The issue is being investigated.
(558864)
Ansys Fluids Products
6.10. EnSight
• When working with Interactive Probes and States in EnSight, there is not per-state attribute that is
captured for the Probe attributes. This means that for the States in EnSight, the probes act independ-
ently. This can result in undesirable visibility in certain states. Workaround: Turn off Probes in the
graphical user interface or to accept Probes in all captured assets. (546607)
• When working for Element Filtering and Coordinate variables, the application of States can reset that
Element Filter based on Coordinates back to a null filter. Only filter operations involving Coordinate
variables are affected, all other Variable Filtering application is correctly maintained when applying
States. Workaround: Re-apply the element filter rules involving Coordinate variables after restoring
the state. (546925)
• Nexus does not yet support usernames or passwords which utilize i18n characters. (546521)
• Double clicking in the middle of a text field incorrectly selects the text within the text field. This is a
known bug with the underlying Qt graphics library. (414225)
• Clicking the Mac trackpad with two fingers to display the right-mouse-button context pop-up menu
in the EnSight graphics window may pause animation due to a problem with the underlying Qt
graphics library. To make animation continue, single click in the graphics window. (459535)
• When two or more surfaces overlap/very close (e.g. Use of Shadow Parts), EnSight can use a per-part
attribute called 'Facing Front/Facing Back' to correctly show the parts in the right order to the viewer
(i.e. which of those overlapping parts do you see). The OSPRay Ray Tracing capability does not have
this capability, therefore when using the Facing Front/Facing Back capability in EnSight, the OSPRay
rendering will not necessarily respect that display order; potentially resulting in the other surface or
a mixture of the surfaces being rendered. (530505)
• When two or more surfaces overlap/very close (e.g. Use of Shadow Parts), EnSight can use a capability
called Group Transform Polygon Offset to correctly show the parts in the right order to the viewer
(i.e. which of those overlapping parts you see). The OSPRay Ray Tracing capability does not have this
capability, and therefore when using the Polygon Offset, the OSPRay rendering will not respect that
display order, resulting a mixture of surfaces being rendered when the surfaces overlap. (530525)
• Context restore which utilizes Element Filtered does not correctly restore. The Filter is set correctly,
but not applied. (548531)
• When using Structured Datasets, with Unstructured Boundary File (in EnSight format), and in the
context of Server Of Server usage, the nodal variable values are incorrectly applied. (440558)
• When restoring a command file (generated in EnSight 2022 R1) which contains nexus dbase operations
on Windows, the command file may contain just a backslash as a path separator. This restore operation
may fail due to the single backslash usage. (548944)
• When using the ray trace options in combination with illustrating surfaces which have undefined
variable values, the ray trace routine will display the surface as 'zero' value instead of the specifications
in the color palette (e.g. display as constant color, or invisible). (553190)
• The handling of the RBM mesh motion from CFX, through the CFF data format, with Immersed Solids,
is not producing the correct motion of the body. (510659)
EnSight
• For Immersed solid zones, from CFX, via the CFF format, variables are not explicitly available on the
IMS Walls from their neighboring cell nodes. (509370)
• Deactivation of the fx_vortcore_streng variable after creating the vortex core in EnSight will cause
EnSight to stop. (553287)
• The LSTC LSDYNA reader does not handle datasets with Rigid Body Motion defined within in. The
API used does not correctly inform the reader of this situation, and can cause incorrectly shaped
elements to be passed through. (558890)
• When using the Fluent HDF5 Restart reader, with domains which utilize Element Filtering (e.g. overset),
the saving and restoring of subsequent context files may not work correctly. The settings for the
element filtering are not transferred correctly through, which appears as an issue in the restoring of
the context file. (559189)
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
Chapter 8: Embedded Software
8.1. Scade
Chapter 9: Ansys Optical Products
9.1. Ansys Speos
Local Meshing (552272 551166 551355)
• Known Issue: The Meshing can be wrong when the Step Value applied is smaller than the face size.
• Workaround: Check the meshing quality using Preview Meshing and adjust if needed.
Speos Light Box (539554)
• Known Issue: When you partially simulate a Speos Lightbox containing inputs generated before
version 2021 R2, Speos may stop working.
• Workaround: Make sure to use the complete Speos Lightbox in the simulation.
Material Files (560769)
• Known Issue: The properties displayed may not reflect the Material file definition when opening it
with a double-click from Windows Explorer.
• Workaround: Open the User Material Editor from the Speos interface, then open the Material file
from the User Material Editor.
9.2. Ansys Speos for NX

• Workaround: Open the User Material Editor from the Speos for NX interface, then open the Material
file from the User Material Editor.
9.3. Ansys Speos for Creo Parametric

• Workaround: Open the User Material Editor from the Speos for Creo Parametric interface, then open
the Material file from the User Material Editor.
Ansys Optical Products
Eulumdat File (546984)
• Known Issue: Uploading an Eulumdat file in a Luminaire source does not work if the extension is
*.LDT instead of *.ldt.
• Workaround: Replace the uppercase extension *.LDT by the lowercase extension *.ldt and upload
the Eulumdat file again.
Irradiance Sensor (549785)
• Known Issue: During an Irradiance sensor creation, when applying the Properties, the face selection
does not work for the Data Separated By Face Filter.
• Workaround: After the sensor creation, right-click the Irradiance sensor from the tree, and select
Properties.
9.4. Ansys Speos Labs

• Workaround: Open the User Material Editor from the Speos, Speos for NX, or Speos for Creo Para-
metric interface, then open the Material file from the User Material Editor.
9.5. Ansys Speos HPC

Chapter 10: Ansys Acoustics Products
Chapter 11: Ansys Systems Products
11.1. AVxcelerate Data Preparation and VRXPERIENCE VR
• Creating a new deploy platform in CAD with Antialiasing activated in the Deploy General Settings
makes the software unstable. (551591)
• There is a software stability issue when setting an invalid URL in the HTML Path property of a Surface
Source. (551580)
• Trying to generate tangents on a non-visible mesh results in software instability. (549635)
• Instantiating a geometry imported with the Import patches option activated may takes a long time.
Workaround: Deactivate the Import patches option before importing the geometry, the instantiation
takes less than 5 sec. (451383)
• Switch to Speos Live Preview is not possible when a material with a normal map is applied more than
1 time.
Workaround: If you want to apply a material with a normal map to more than one material part,
copy the material to create one file per material part (552448).
11.2. AVxcelerate Sensors Simulator

• The diffraction spike effect, and the appearance of this effect, due to headlamp lights is saturated on
the first frame in the camera output and in the display window. (552476)
• In AVxcelerate Sensor Labs, you can import a rotating lidar created in 2021 R2 version with an Hori-
zontal Divergence parameter value is out of the allowed range. (552146)
Chapter 12: Ansys Geometry and Mesh Prep Products
12.1. CAD Connections & Integration
12.2. DesignModeler
12.3. Meshing
Moments of inertia and principal axes calculations may be incorrect for Pull features and multi-body
part profiles. You may need to calculate the moments of inertia and principal axes manually for Pull
features. (468737)
When a generated Pull in a system is transferred to another system and both the systems are updated
then if you suppress the first system and update both the systems, the updated Pull in the first system
is not transferred to the Pull in the second system. (528768)
When you export a .CSV file from Weld Worksheet, the names on the header of the exported file may
not reflect the new names of the fields in the worksheet. The field names on the weld worksheet (listed
on the left below) and their respective names on the exported file (listed on the right below) are as
follows:
• Weld Worksheet = Exported .CSV File
• Create HAZ Layer = Create Offset Layer
• Number Of HAZ = Number Of Layer
• HAZ Growth Rate = Offset Layer Growth Rate
• HAZ Distance = Offset Layer Height
• Weld Width (Leg01) = Weld Width
• Weld Height (Leg02) = Weld Height
(548751)
12.4. ICEM CFD

Chapter 13: Safety Analysis
13.1. Medini
When importing requirements from external RM systems into medini for the first time, it is not possible
to map more than one relation to the medini Trace relation. The operation is aborted until the mapping
file is adjusted. On subsequent updates the mapping is possible thought. Workaround: Initially import
without relationships and update with relationships afterwards. (368230)
Chapter 14: Ansys Simulation Products
14.1. Ansys ACT
See the ACT Known Issues and Limitations documents on the App Developer Resources page of the Ansys
Store.
14.2. Distributed Compute Services (DCS)

14.3. DesignXplorer
14.4. optiSLang
Exporting an optiSLang project as an Ansys ModelCenter scriptWrapper does not work correctly for
discrete and dependent parameters.
For discrete parameters, boundaries are exported into the ModelCenter scriptWrapper which cannot
be handled by ModelCenter. An error is displayed in ModelCenter and responses are not updated.
• Workaround: Manually delete boundaries for discrete values in the scriptWrapper file, located
in the export directory.
• Example (in myProject.scriptWrapper): variable: Parameter_bool bool input default=0 enumVal-

ues=0,1
For dependent parameters, the scriptWrapper Python script attempts to read values from these para-
meters, even though they are not supported or exported. A Python error is reported in the log file and
responses are not updated.
• Workaround: Manually add the parameter to the scriptWrapper file, located in the export direct-
ory. You can also specify the parameter as dependent in ModelCenter to ensure a value is not
set for this variable. This is just a placeholder for the dependent variable and the value is not
updated in ModelCenter.
• Example (in myProject.scriptWrapper): variable: Parameter_dependent long input default=0
(552810)
Ansys Simulation Products
When you have a workflow with multiple MOP nodes that are manually connected to the Sensitivity
system, and the MOP nodes are configured to use external (Python based) model types like DFFN, SVR
or GARS, running the entire workflow (all nodes in parallel) results in external model build failures.
Workaround: Manually run each node individually, one after the other. Add conditional execution to
force the workflow to run the MOP nodes in sequence. To do this, connect the oSuccess and en-
abled_storts slots according to the targeted order. (558435)
When using a signal type response, running Probabilistic Inference for Bayesian Optimization (PI-BO)
fails with the following error message: TypeError: Argument ‘outputs’ has incorrect
type (expected list, got numpy.ndarray)(from RPC dispatch side) Workaround:
Remove signal responses from the response list. If signals are required for the criteria definition, use
signals as internal variables at the respective nodes and calculate the required scalar metrices, for ex-
ample, a metric to define the difference to a reference signal. Register the scalar value as response to
use it for the criteria definition on the system level. (559052)
After project execution has finished, the following menu entries are deactivated:
• Generate optiSLang App
• Generate Ansys ModelCenter Wrapper
Workaround: Close and reopen the project. (560056)
The Register project to Web Service functionality with the latest Web Service (22R1) as a target produces
the following error: Error loading custom Monitoring: TypeError: Cannot use ‘in’
operator to search for ‘Monitoring’ in undefinedThe same error is produced when
a project is registered using the /register_project end point. Workaround: In the request body object
set the "wizard" property to an already existing wizard that does not provide a custom Monitoring.
(557822)
14.5. Remote Solve Manager (RSM)

14.6. System Coupling

14.7. Workbench
Currently, the localization of material properties and models in Engineering Data is not occurring. If you
are comfortable editing an installation file, you can correct the issue as follows:
• Open the file Ans.EngineeringData.ts from the following folder: v221\Addins\Engineering-

Data\Language\{language}
• Find this line: <multiname>Ans.EngineeringData.Utilities</multiname>
• Add the following entry immediately after the above line: <multiname>Ans.Engineering-
Data.UtilsHelper</multiname>
Workbench
• Save the file and restart the application.
(557674)
Chapter 15: 3d Design Products
15.1. Ansys SpaceClaim
15.2. Ansys Discovery

• The presence of monitors on points, planes, lines and surfaces may cause a design variant solution
to fail. (560005)
• In the Explore stage, when solving for results that exhibit highly localized extrema, monitors on
points, planes, lines and surfaces may deviate from the underlying solution.
Workaround: The legend and corresponding min/max monitors in the volume would yield the most
accurate information on the global extrema. (554884)
• When using the opacity slider in Display tab > Color, the assigned body or face color may be substi-
tuted with black.
Workaround: To change the opacity of a body or a face, define an override color first then adjust
the opacity as needed. (552013)
• After solving in Refine, projects exported to Mechanical may not contain tabular data.
Workaround: Export to Mechanical before solving. (552234)
• When working with physics parameters in test cases and then navigating to another simulation, the
test cases may no longer be visible.
Workaround: Un-parameterize your physics parameter and then re-parameterize it (using undo).
(552575)
• If a simulation containing a porous condition is duplicated, thermal properties for the porous mater-
ial are not retained when the project is saved.
Workaround: Replace the porous condition in the duplicate simulation after opening the saved
project. (552181)

Ansys Inc. Known Issues and Limitations

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ansys Inc. Known Issues and Limitations

Uploaded by

Copyright:

Available Formats

Known Issues and Limitations

ANSYS, Inc. Release 2022 R1

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

U.S. Government Rights

Published in the U.S.A.

13.1. Medini .......................................................................................................................................... 29

Service packs may become available for some of the entries.

• Clean and re-solve the analysis.

5.2. Mechanical APDL

5.5. Ansys Composite PrepPost (ACP)

5.6. Material Designer

5.7. Additive Manufacturing

• No known issues, limitations, or documentation inaccuracies.

Ansys Additive (Print and Science)

• No known issues, limitations, or documentation inaccuracies.

• No known issues, limitations, or documentation inaccuracies.

6.1.1. Meshing Mode

6.1.2. Solution Mode

Graphics, Reports, and Postprocessing

Discrete Phase Model

6.1.3. Client Applications

6.3. TurboSystem and TurboGrid

Speos Light Box (539554)

Material Files (560769)

9.2. Ansys Speos for NX

9.3. Ansys Speos for Creo Parametric

Eulumdat File (546984)

Irradiance Sensor (549785)

9.4. Ansys Speos Labs

9.5. Ansys Speos HPC

• Trying to generate tangents on a non-visible mesh results in software instability. (549635)

11.2. AVxcelerate Sensors Simulator

• Weld Worksheet = Exported .CSV File

• Create HAZ Layer = Create Offset Layer

• Number Of HAZ = Number Of Layer

• HAZ Growth Rate = Offset Layer Growth Rate

• HAZ Distance = Offset Layer Height

• Weld Width (Leg01) = Weld Width

• Weld Height (Leg02) = Weld Height

12.4. ICEM CFD

14.2. Distributed Compute Services (DCS)

• Example (in myProject.scriptWrapper): variable: Parameter_bool bool input default=0 enumVal-

• Example (in myProject.scriptWrapper): variable: Parameter_dependent long input default=0

• Generate optiSLang App

• Generate Ansys ModelCenter Wrapper

Workaround: Close and reopen the project. (560056)

14.5. Remote Solve Manager (RSM)

14.6. System Coupling

• Open the file Ans.EngineeringData.ts from the following folder: v221\Addins\Engineering-

• Find this line: <multiname>Ans.EngineeringData.Utilities</multiname>

• Save the file and restart the application.

15.2. Ansys Discovery

Workaround: Export to Mechanical before solving. (552234)

You might also like