Databases saved with a service pack for 2024 R1 cannot be read and resumed with the initial release of 2024 R1. Furthermore, this applies to each service pack update. Once the database is saved in a service pack, it is no longer compatible with the previous service pack. The application displays an error message when this situation is encountered.

The application does not currently support all available graphical display options using the Accelerated Graphics feature. As a result, you could see inconsistencies for how graphical contours are displayed. This is a result of the application automatically switching to the Standard Graphics display capability which is not based on the newest available technology. Examples of associated display options include the use of the Thick Shells and Beams option, Section Plane display, and result probes (although probe values are correct). Select the High Fidelity option to potentially minimize some of these display issues.

Section Planes enable you to view the internal elements of your model. However, if you specify a command for how the application writes solution data, such using the OUTRES command to produce results for exterior elements only, you might encounter unexpected contour displays on interior elements exposed by a Section Plane.

When you have the Solution Information object selected during a lengthy solution of an analysis that includes a substantial number of load steps, you could see memory requirements increase to the point that the solution fails. In this situation, select a different object in the Outline and rerun the solution.

A graphical display issue exists for the Analyses Selection worksheet. Certain actions may cause the partial status icon   to redisplay to an unselected state  . This issue has been observed when resizing the pane and/or scrolling right and left in the window.

When a model has multiple bonded MPC contacts with the Behavior property set to Program Controlled or Auto Asymmetric and have common contact surfaces or common target surfaces, it could potentially lead to an over constrained problem. Ansys recommends that you merge such contacts to a single contact using Merge Selected Contact Regions operation to overcome the over constraints issue.

If your analysis includes a Surface Coating created using the Pull feature, whose Stiffness Option property is set to Stress Evaluation Only and the Thickness property is set to 0, any Contact Tool included in the analysis will fail to generate contact results.

An issue exists in releases prior to 2024 R1 SP03 when assembling Mechanical systems in a downstream analysis. Named Selections do not properly transfer to downstream systems if you make updates to an upstream system and re-read the updates in the downstream system. Instead of rewriting the Worksheet in the downstream system with updated rows of Named Selections, the application adds new rows to the Worksheet.

This issue does not affect the entities selected by the Named Selections, however, if a large number of new rows of Named Selections are added to the Worksheet as a result of upstream changes, larger and larger amounts of memory is required. Ansys has corrected this issue, however, if you open a project saved in a release prior to 2024R1 SP03, Ansys recommends that you make a manual change in the upstream system, such as adding and then deleting a Named Selection and then re-read the upstream data in the downstream system to correct any unnecessary worksheet entries.

When you select Dark as the interface theme for Mechanical, you may notice certain interface elements that do not adhere to the color scheme.

When you launch multiple sessions of the application (for example, to compare analyses), it may take some time for each instance to start and for the application to respond to requests. You can potentially address this issue by setting the Ribbon Toolbar Refresh preference to Manual. The Manual setting instructs the application to refresh only when you navigate and/or make selections, rather than updating many times per second.

Whenever you are saving or exporting data from the application, the character limit for the file path is 260 characters. An entry that exceeds this value may cause system issues.

For harmonic-based analyses when you:

The application may display incorrect values in the Minimum Frequency and Maximum Frequency properties of the Options category of the Details pane for the result. For this case, the data included in the Graph and Tabular Data windows is correct.

Loads that are distributed evenly across geometric entities may use averaging that can cause the applied load value to deviate from the exact input value depending on mesh quality. For more accurate loading application, increase mesh quality in the region of application especially for curved surfaces or any time the mesh deviated from the idealized geometry.

The application creates reference files that contain analysis information that is read back into the application during solution processing. Certain textual characters can create issues during this reading process. Avoid the use of the following unsupported characters in your file naming conventions and file path definition:

If your analysis includes an exceptionally large number of objects, the Outline content may appear incomplete. The application has a display limitation of 65,536 objects. If the number of objects exceeds this threshold, any additional objects are not displayed.

For results displayed in Tabular Data window, if 0 (zero) displays for both the Minimum and Maximum values of a row, the result set may not contain result data. You can use the Retrieve This Result option (via right-click on table row), to view result sets in order to determine if any data exists for the set. If no data is available, the result contours in the Geometry window display as fully transparent.

Color coding may change or disappear when displaying shared topologies using both the By Connection edge coloring and the Section Plane features. The By Connection option displays connectivity color coding, while the Section Plane feature is used to cut or slice the model to view its interior.

When you are running Mechanical version 14.0 or any previous version on a Linux system, you may experience graphical distortions when animating results, rotating an animation of results, as well as zooming in and/or out on your results.

When running a Mechanical session on the Linux operating system, if you encounter a delay while meshing or launching the Mechanical application or even a crash of the Workbench application, a potential solution is to create a new session with the Hardware Acceleration option turned off (display the OpenGL tab and deselect the Hardware Acceleration option).

If you are resuming a project in Mechanical on the Linux platform, there is a restriction that the path to the project, as well as the project name, include ASCII characters only, otherwise, the project will not open.

When using Nice DCV to remotely connect to a Linux machine running Mechanical, you may encounter display issues when using the Report, Print Preview, or Image to File features. To correct this issue, it is necessary to turn off DCV in the Nice DCV control panel, close and reopen Mechanical, and then generate the Report, Print Preview, or Image to File. Once complete, close the application, turn DCV back on, and then reopen the application once again.

If you are running the Nahimic audio driver on your system, the Mechanical application could unexpectedly close when performing certain tasks, such as exporting an image of the Geometry window. Disabling the driver should address the issue. The Nahimic application is not provided by or related to any Ansys products.

Currently, Mechanical does not support 4K displays. When Mechanical is initially launched on a 4K display, it appears to display normally. However, some panes (such as Scripting View, ACT Log, and ACT Wizards) will not display correctly. Content in these pages may be cut off or appear too small compared to the rest of the user interface.

To address these issues, do the following: