This section lists limitations that are known to exist in ANSYS Fluent. Where possible, suggested workarounds are provided.
File import/export (for a list of supported files, refer to the table in this section, under Third-party software)
If you change the File Storage Options settings in the Autosave dialog box, the solution history will be lost.
Data export to Mechanical APDL result file is not available on the linx64 platform. (Mechanical APDL data export to .cdb file is available on all platforms.)
When exporting EnSight Case Gold files for transient simulations, the solver cannot be switched between serial and parallel, and the number of compute nodes cannot be changed for a given parallel run. Otherwise, the exported EnSight Case Gold files for each time step will not be compatible.
EnSight export with topology changes is not supported.
To properly view Fieldview Unstructured
(.fvuns) results from a serial or parallel
ANSYS Fluent simulation:
Mesh files must be exported using the
fieldview-unstruct-grid text
command.
Mesh and data files should all be exported from parallel ANSYS Fluent sessions with the same number of nodes.
Tecplot file import does not support the Tecplot360 file format.
The maximum number of profiles that can be read into a single Fluent session is 50.
The PARALLEL INDEPENDENT mode for Hierarchical Data Format file I/O is known to exhibit slow write performance. On parallel file systems, consider using the PARALLEL COLLECTIVE mode when writing HDF files. On other network file systems, consider using the HOST or NODE0 mode.
If you are accessing a file using a Universal Naming Convention (UNC) path, you must ensure that you have permission to access to all of the folders in the path or you will not be able to open the file.
Mesh
Boundary zone extrusion is not possible from faces that have hanging nodes.
For simulations that involve the Fluent, Mechanical, and Meshing applications, meshing problems can arise in instances where there are multiple regions and contacts between them. In Fluent, a zone can only exist in a single contact region. The Mechanical and Meshing applications both use a different approach concerning contact regions when compared to Fluent.
ANSYS Fluent does not support FSI data mapping of edges and, therefore, it is not supported in 2D.
At non-conformal interfaces, the Matching option is no longer allowed with the Mapped option. When opening a case set up in a previous release with both options enabled, you will be prompted to recreate the interface without the Matching option.
If your mesh topology has a step-wise prism mesh near the walls, do not use node-based gradients with MUSCL.
Models
ANSYS Fluent supports the Chemkin II format for Oppdif flamelet import only.
The surface-to-surface (S2S) radiation model does not work with moving/deforming meshes.
The DPM work pile algorithm is not compatible with the wall film boundary condition.
The shell conduction model is not applicable on moving walls.
The heat exchanger model is not compatible with mesh adaption.
The Fluent/ANSYS Reaction Design KINetics coupling is not available on the win64 platform.
DO-Energy coupling is recommended for large optical thickness cases (> 10) only.
FMG initialization is not available with the shell conduction model.
FMG initialization is not compatible with the unsteady solver.
The MHD module is not compatible with Eulerian multiphase models.
Bounded 2nd order discretization in time is not compatible with moving and deforming meshes.
When simulating porous media, the value of the Porosity (defined in the Fluid dialog
box) cannot be 0 or 1 (that is, it must be in between these values) if the non-equilibrium
thermal model is enabled.
When simulating porous media, the non-equilibrium thermal model is not supported with radiation and/or multiphase models.
For porous media simulations, the relative velocity resistance formulation is not supported with axisymmetric-swirl when there are non-zero swirl resistances.
The junction of a wall with shell conduction enabled and a non-conformal coupled wall is not supported. Such a junction will not be thermally connected, that is, there will be no heat transfer between the shell and the mesh interface wall.
After you enable the Eulerian Wall Film model, Fluent will not allow you to save the mesh modifications, such as separating cells, extruding face zones, and changing the cell zones type. If you want to modify the mesh in Fluent, be sure to complete all mesh operations prior to enabling the Eulerian Wall Film model.
The Transition SST model (also known as the γ-Reθ model) is not Galilean invariant and should therefore not be applied to surfaces that move relative to the coordinate system for which the velocity field is computed; for such cases, the Intermittency Transition model (also known as the γ model) should be used instead.
In simulations that use the discrete phase model, particle mass may be lost when simulation of transient particles released with constant parcel size is combined with auto-save of case files.
User-defined wall functions are not compatible with the Eulerian multiphase formulation and cannot be used.
The view factor files generated as part of a surface-to-surface radiation model calculation for version 16.0 or 16.1 of Fluent may not be compatible with newer versions if the Matching option was enabled for a mapped interface. For any case file with such a setup, you must recompute the view factors in the newer version to ensure correct results.
Parallel processing
These features are currently unavailable in the parallel solver:
Discrete transfer radiation model (DTRM)
Using the Intel MPI option on the Windows 10 platform causes the mpiexec.exe process to remain active even after Fluent is closed, since the Intel MPI version is not supported on Windows 10. It is therefore recommended that you use the default MPI (that is, IBM MPI) on Windows 10 instead.
Mellanox OFED version 1.5.3–1.0.0 is known to cause random crashes or startup issues in Fluent when using core counts greater than approximately 64. The last known stable Mellanox version is 1.5.2. You may use either of the following as a workaround:
Revert to OFED 1.5.2.
Set the value of log_num_mtt to
24 in the mlx4_core driver on all machines.
For more information refer to Solution #2024818 from the Knowledge
Resources at the ANSYS Customer Portal (ANSYS Customer Portal).
IBM MPI does not support running in parallel in an overload condition (using more cores than
are physically available on a machine). For performance reasons, running
in an overload condition is generally not recommended. However, if it is
required to run overloaded, then you can use Intel MPI
(-mpi=intel) or Open MPI
(-mpi=openmpi).
The version of IBM MPI that is distributed with Fluent is now limited to a maximum of 4096 processes for a single simulation. For higher core counts, an additional license is required. Refer to IBM Platform MPI with High (>4096) Process Count in the Installation and Licensing Documentation for more information.
Note that on systems using large pages for memory allocation (such as Cray), the virtual memory usage reported by Fluent may be much higher than actual memory used. In this case resident memory (also reported by Fluent) is a more reliable guide.
Degenerate contact points are known to cause topological mesh connectivity issues in parallel. Degenerate contact points are nodes that are shared by 2 or more cell zones that do not share faces. Fluent can detect degenerate contact points in serial via a mesh check with the mesh check verbosity set greater than 0. If a case has generate contact points then you must use the following command before reading the case for proper parallel handling of such contact points.
(rpsetvar 'parallel/add-dgcp-to-int-or-corner?)
The Eulerian Wall-film model is not compatible with the DPM Domain option of the hybrid parallel DPM tracking. For such model combination, the Use DPM Domain option must be disabled in the Parallel tab of the Discrete Phase Model dialog box.
The Fluent process binding (affinity) setting is not supported for Windows machines with more than 64 cores that are using the IBM MPI communication library, which may increase processing time. As a workaround, you can use Intel MPI or disable hyper-threading (if the machine has Intel processors) to lower the core count to be equal to or below 64.
Starting in version 18.0, ANSYS Fluent will require approximately 60 MB more memory per node process compared to version 17.0–17.2.
Platform support and drivers
On Windows Server OS, ANSYS Fluent supports only MS MPI for parallel runs. Installing any other unsupported MPI libraries (IBM MPI or Intel MPI) will result in conflicts.
On Windows 7 and later, installing ANSYS Fluent on any
drive other than C: may result in issues
arising from spaces in the pathname not getting converted to short
file names. This is the result of a change in the default value for NtfsDisable8dot3NameCreation starting with Windows 7.
If you need to install ANSYS Fluent on any drive other than C: you must run the following command prior to installing ANSYS Fluent:
fsutil 8dot3name set <driveletter> 0where <driveletter> is the target drive letter including the colon (for example, D:).
The minimum OS requirements for Linux are SLES 11 SP2 or RHEL 6.
The pathname length to the cpropep.so library (including the lib name) is limited to 80 characters. (Linux Opteron cluster using Infiniband interconnect only.)
On Linux platforms, including a space character in the current working directory path is not supported.
Visit the ANSYS Customer Portal (ANSYS Customer Portal) for the latest Windows graphics FAQ. Version 2.0 or higher of .NET Framework must be installed in order to run ANSYS Fluent on the winx64 platform.
If you are installing ANSYS Fluent 18.2 on a Windows machine that already has one or more previous versions of ANSYS Fluent, then after installing IBM MPI and Intel MPI libraries from the prerequisites, make sure to delete the environment variables MPI_ROOT (for IBM MPI) and I_MPI_ROOT (for Intel MPI). Otherwise there will be a conflict while running previous ANSYS Fluent versions in parallel mode.
Remote Solver Facility (RSF) is no longer supported in ANSYS Fluent.
Itanium platform (lnia64) is no longer supported.
ANSYS Fluent uses several TCP/IP ports for communications and error handling. Port conflicts with other programs trying to use the same ports are handled by ANSYS Fluent and generate warnings similar to the following:
428: mpt_accept: warning: incorrect exercise message "GET /" from 10.1.0.188 on port 56564
Long running large sessions are more prone to generating such warnings, but these are generally safe for you to ignore.
When using the default MPI (ibmmpi) on some newer hardware the
following message may appear when exiting the Fluent session.
hwloc has encountered what looks like an error from the operating system. object (Socket cpuset 0xff00ffff) intersection without inclusion! Error occurred in topology.c line 758 Please report this error message to the hwloc user's mailing list, along with any relevant topology information from your platform.
This message is from the hardware locality library used by IBM MPI. You can set the following environment variable to hide this message, or switch to Intel MPI.
HWLOC_HIDE_ERRORS=1
If you lock the computer screen before the Fluent graphics are
initialized, the Fluent session will not launch if you are using the
OpenGL graphics driver. To avoid this issue with the OpenGL driver, you
can use the alternative drivers x11 or
null for Linux/unix and
msw or null for
Windows. You can specify an alternate graphics driver either by defining
it in the HOOPS_PICTURE environment variable or
using the -driver Fluent command line
option.
Fluent may terminate abnormally during launch when running on
Community Enterprise OS (CentOS) 7.3 or Red Hat Enterprise Linux (RHEL)
7.3 when DISPLAY is set to a Virtual Network Computing (VNC) session. To
attempt to resolve this, verify that you are using a supported graphics
card and update the graphics card drivers (directly from the graphics
card vendor website). If the issue persists, you can do one of the
following: set the DISPLAY to a local machine; set the
LD_PRELOAD environment variable to
/usr/lib64/libstdc++.so.6; or use the
alternative drivers x11 or
null (either by defining it in the
HOOPS_PICTURE environment variable or using
the -driver Fluent command line
option).
Remote display
Connecting or disconnecting a VPN network while running a Fluent simulation will result in a failure because of changes to the network interface.
If you experience an abnormal termination when running Fluent via a remote display, check you graphics card to ensure that you have a modern professional graphics card that is up-to-date (that is, the latest updated driver for that card, which is available on the company's website). If your system does not meet the graphics card requirements, launch Fluent using a completely software-based driver, such as MSW (Windows) or X11 (Linux).
Cell Zones and Boundary Conditions
Fluid zones designated as 3D fan zones cannot have non-conformal interfaces.
Solver
The absolute and relative velocity formulations may yield different results in cases where a strong reversal of flow exists at a pressure outlet boundary.
The non-iterative time advancement (NITA) solver is applicable with only a limited set of models. See the ANSYS Fluent User's Guide for more details.
NITA (using fractional time step method) is not compatible with porous media.
The following models are not available for the density-based solvers:
Volume-of-fluid (VOF) model
Multiphase mixture model
Eulerian multiphase model
Non-premixed combustion model
Premixed combustion model
Partially premixed combustion model
Composition PDF transport model
Soot model
Rosseland radiation model
Melting/solidification model
Enhanced Coherent Flamelet model
Inert model: transport of inert species (EGR in IC engines)
Dense discrete phase model
Shell conduction model
Floating operating pressure
Spark ignition and auto-ignition models
Physical velocity formulation for porous media
Selective multigrid (SAMG)
The pressure-based coupled solver is not available with the following features:
Fixed velocity
On some Linux platforms, pressing Ctrl+C will not interrupt the solution. A suggested workaround is to use the checkpoint mechanism in Fluent to save files and/or exit Fluent. (Checkpointing an ANSYS Fluent Simulation in the Fluent Getting Started Guide)
In certain cases with tetrahedral or hybrid meshes, the use of the Least-Squares Cell Based gradient method in combination with the cell-to-cell limiter may cause divergence. If this is observed, it is recommended that you either change the gradient method to Green-Gauss Node Based or change the limiter type to the cell-to-face limiter.
You should not vary the timestep size during a calculation run when using second-order discretization. Doing so creates an error that reduces with a reduction of the timestep jump.
Beginning in version 17.0, the warped-face gradient correction (WFGC)
is not supported with shell conduction if the ability to define
multi-layer shells has been disabled through the
define/models/shell-conduction/multi-layer-shell
text command.
User-Defined
Any scripts or journals that attempt to add menu items to Fluent pull-down menus (which have been replaced with the Fluent ribbon) will no longer work. You must create separate user-defined menus to house all user-defined menu items. For additional information about user-defined menus, see Adding Menus to the Right of the Ribbon in the Fluent Customization Manual.
User-defined functions (UDFs)
Interpreted UDFs cannot be used with an Infiniband interconnect or, when running in parallel, on the Cray platform. The compiled UDF approach must be used instead.
The Visual Studio Express 2015 for Windows installer on Windows 10 installs libraries in non-standard locations, resulting in UDF compilation failures on this platform. It is recommended that you instead use the Visual Studio Express 2015 for Desktop installer, or manually set the library path based on your local installation (for example, LIB="C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\lib\onecore\amd64";%LIB%).
Graphics, Reporting, and Postprocessing
Monitors may continue to print/plot values, even if the zones on which they are defined are deactivated.
If you are autosaving multiple scenes on a Windows machine, the Headlight lighting effect may inconsistently change its state (on/off). This can be avoided by rendering each scene in a separate graphics window.
Mean and root-mean-squared-error (RMSE) quantities of custom field functions are only available for mixtures. In previous releases it was possible to specify these quantities for phases, which was an incorrect behavior. This behavior is no longer allowed in R16.0 or later releases. If you are running a pre-R16.0 case set to output such quantities in R18.2, you may get a segmentation error. To avoid the error, redefine the previously defined monitors reporting mean or RMSE quantities of phases.
The mouse-annotate feature is no longer available. Annotations can still be created using the Annotate dialog box (see Annotate Dialog Box in the Fluent User's Guide for additional information).
Beginning in version 15.0, if a flux report for the heat transfer rate is generated on the wall of a moving solid, the reported values will include the convective heat flux due to the motion of the solid. Depending on the mesh and quality of the geometry representation, this may present flux values that are different than the flux specified in the boundary condition definition (for example, a non-zero flux may be reported for an adiabatic wall).
Beginning in version 18.0, if you import a legacy case containing multiple monitors plotting in the same window, you must review the setup to ensure each report plot is assigned to a different window before running the calculation. If the plot windows are not reassigned, then plots assigned to the same window will be lost.
It is possible to use text commands to create contour, vector,
mesh, pathline, particle track, XY plot, and scene graphics objects with
spaces in the name (for example, through the
display/objects/create text command);
however, objects with such names cannot be displayed using the
display/objects/display text command, and
attempting to do so will only result in the printing of an error. As a
workaround, you can create graphics objects without spaces in the name
or use the graphical user interface to display graphics objects with
spaces in the name.
In rare cases, the Curve Length X Axis Function for XY plots may not plot correctly, even if the curvilinear surface is piecewise linear and appears to be a single closed curve. A workaround is to use the Direction Vector X Axis Function.
Transient statistics (Mean and RMS) reported for Fluent quantities that are nonlinear functions of the underlying solution variables represent evaluations of those quantities using the Mean or RMS values of the underlying solution variables. For instance, Mean Velocity Magnitude is computed as the magnitude of a vector constructed from the mean velocity components, and Mean Pressure Coefficient is computed as the pressure coefficient computed using the mean pressure. To construct the true Mean and/or RMS values of such quantities, you can define a custom field function and collect transient statistics of the custom field function. For example, define a custom field function vmag_cff = sqrt (Vx ^ 2 + Vy ^ 2 + Vz ^ 2), and report Mean and RMS of vmag_cff.
Fluent in Workbench
Coupling between Fluent and HFSS or Q3D Extractor is not supported.
When the parallel version of Fluent or Icepak is coupled with Maxwell 3D in Workbench, the solver may report imported surface losses that are slightly higher than the actual losses. The serial version of the solver does not have this limitation.
For two-way coupling between Maxwell and Fluent, by default Fluent uses the
following zones: when mapping volumetric losses, the same list of zones
that you selected for receiving volumetric losses in Fluent's
Maxwell Mapping Volumetric dialog box are used;
and when mapping surface losses, all cell zones are used. To change the
zones that are used for feedback mapping, you can use a Scheme command,
shown in the following example. This example specifies that only cell
zone ID 1 and 2 are used: (em-set-feedback-map-cell-zone '(1
2)). Note that you can only specify the IDs of the cell
zones as the arguments.
In a Fluent analysis system, the Clear Generated
Data option for the Solution cell
will not clear the files associated with animations. To have the
Clear Generated Data option clear the animation
files as well, you must define the FLUENT_WB_REMOVE
ALL_GENERATE_FILES as a system environment variable on
your local machine, prior to opening Workbench.
Fluent as a Server
When running Fluent with the -aaS option, if you have a mesh with a very low cell count and have set
a large number of iterations to be stored using the Residual
Monitors dialog box (see Storing Residual History Points in the Fluent User's Guide), you will see a relative degradation of performance. Reducing the
number of stored iterations will reduce this degradation.
When launching Fluent with the -gu or
-g command line options and Fluent as a
server enabled, Fluent will run with the graphic user interface
minimized.
Third-party software
Fluent-Platform LSF integration is not supported on the MS Windows platform.
Fluent-SGE integration is supported only on Linux platforms.
Wave and GT-POWER coupling are available only with stand-alone ANSYS Fluent and not in the Workbench environment.
Supported versions of third-party software are listed below:
| Third-Party Software | Supported Version |
|---|---|
| Abaqus | 6.14 ODB Library: 6.14.5 |
| Altair HYPERMESH | 5.1 |
| AVS | 5.0 |
| CGNS | 3.1.3 |
| Cray MPI (MPT) | 7.0* |
| Data Explorer | 4.2 |
| EnSight 6 (TUI only) | Ensight 6 |
| EnSight Case Gold | 10.1.6 |
| FAST | 1.3 |
| Fieldview | 16.0 |
| GT-POWER | v2017.1 |
| HOOPS | 21.21-1 |
| HP/IBM MPI | 09.01.04.02 |
| I-deas | I-deas NX Series 11 |
| Intel MPI | 5.1.3.223** |
| libpng | 1.6.18 |
| LSTC-DYNA | 970.0 |
| MPCCI | 3.0.5 |
| NASTRAN |
Bulk data input file - MSC.NASTRAN 2010 OUTPUT2 data file - NX/NASTRAN 10 |
| NIST | 9.1 |
| Open MPI | 1.6.5 |
| PATRAN | 3.0 |
| PTC MECHANICA | PTC/Mechanica Wildfire 4.0 |
| Sundials | 2.5.0 |
| TECPLOT | Tecplot file format, version 11.2 |
| VKI | 4.3.6 |
| WAVE | 2014.1 |
| zlib | 1.2.8 |
* When using MPT version 5.0 and higher (up to,
but not including 7.0), you must set the following environment variable:
export FLUENT_USE_CRAY_MPT5=1.
** By default, Intel MPI does not support heterogeneous environments (that is, a mix of operating system versions or hardware) for Windows. As a workaround, you can use the following environment setting:
I_MPI_PLATFORM zero
Other
If the network connection is lost during a serial or parallel calculation, the Fluent session may terminate abnormally.
The IRIS Image and HPGL hard copy formats are no longer supported in ANSYS Fluent.
When using ANSYS Fluent with the Remote Solve Manager (RSM):
Only one copy of a saved project that is in the pending state can reconnect successfully.
Maxwell coupling is not supported.
UDFs are supported with limitations as detailed in Submitting Fluent Jobs to RSM or an EKM Portal in Workbench User's Guide.
The turbo-averaged contour plot in turbomachinery postprocessing may give an unexpected contour region in a selected topology.
The Inverse Distance and Least Squares profile interpolation methods are not applicable when a profile is attached to cell zones.
Heat exchanger networks are not supported in HDF-formatted case and data files.
When opening the Help Viewer from Fluent in Linux, you may receive an error message in the Linux console. This can result when another user has created the installation and run Fluent, thus creating a registry file; if you then run this same installation, there will be a permissions conflict. As a workaround, remove the registry file:
path/ansys_inc/v182/Tools/mono/Linux64/etc/mono/registry
(where path is the directory in which you have placed the release directory). Then change the permissions for the Mono platform in order to remove write access from the directory:
path/ansys_inc/v182/Tools/mono/Linux64/etc/mono
On Windows, mesh reading into a serial ANSYS Fluent session may fail if you use more than 20 million cells per core.
For non-conformal interfaces, the use of the Matching option with the Mapped option is not recommended, especially if the extents of Interface Zone 1 and Interface Zone 2 do not coincide.
Fluent does not support non-ASCII characters in the names of files, zones, and boundaries.
When exiting a Fluent session on Linux that was started with the Load ACT option, Fluent may become unresponsive. If this occurs, the Fluent process must be manually terminated. In the console, the error message specifies that a corrupted double-linked list is responsible for the error. Because this unexpected shutdown occurs after the project has been saved, no data is lost.
When Fluent is run on Linux with the Load ACT option, Fluent may repeatedly issue the following warning during solution iteration:
Unexpected error checking licensing server.
This warning is harmless and does not impact Fluent or ACT usage.
When running a stand-alone instance of Fluent
in a mixed Windows / Linux configuration or from a remote Windows
installation, ACT does not open. To correct the problem, you must set
the AWP_ROOT182 environment
variable to point to the ANSYS installation directory.