Due to a limitation in third-party packages used by ACT, the help for an ACT wizard can only link to on-disk locations (ref="file:///..."). Using a location other than the local disk will result in an empty help content area within the wizard.

Extension images residing on a network location or a mapped drive do not display on web browser-based ACT views. Affected views include all tools available from the ACT Start Page, such as the Extension Manager and Wizards Launcher. Instead of seeing the intended image for an extension, you will see a "?" icon. However, the extension will execute properly.

When naming a caption for a custom object, the software automatically appends a number to the name if it is identical to existing objects. Do not end the name with a space followed by a number. While no error appears, the number will be removed and may be changed. Workaround: When renaming a caption for a custom object, always follow a space with a non-numeric character before using a number. For example, rather than renaming a caption to my custom object 2, rename it to my custom object n2.

A third-party solver exposed through the <solver> simdata tag may not display in the Workbench Toolbox if the XML file specified for the attribute system_template relies on a ValidationCode. To obtain a correct ValidationCode value compatible with recent licensing system upgrades, contact your local support channel.

Some ACT panels, such as the ACT Console and ACT Debugger, may not "spring" the entire width of the parent dialog. Panel behavior and user interaction are unaffected.

A Workbench extension can define new systems to insert in the Project Schematic. Reloading such an extension after creating new system instances will result in unexpected behavior. Before reloading, delete all extension-related systems or save and reset the project.

In an HTML component, an image, custom JS, or CSS file does not display unless the file URL protocol (file:///) is placed before the file path.

Prior to 2020 R2, an absolute path could be used:

img src="c:/Users/User1/myimage.jpg"

However, the file:/// protocol must now be placed before the file path. Some examples follow.

For an image file:

img src="file:///c:/Users/User1/myimage.jpg"

For a custom JS file:

component.CustomJSFile = r'file:///' + str(ExtAPI/Extension.InstallDir)+ r'\custom_table.js'

If after installing Ansys products, you see that the ACT Start Page is blank, right-click inside the blank window and select Reload.

When using a VPN, IP information can be retained, even after turning off the VPN and rebooting the computer. The workaround is to release the IP configuration using the following script:

echo Releasing IP
ipconfig /release > NUL
echo Acquiring new IP
ipconfig /renew > NUL

When running with an enabled FIPS security policy, ACT User Interface elements are not supported.

When using ACT to create Workbench custom workflows, not all optional attributes for the tag <property> are currently supported. For example, visibleon is not supported.

For DesignModeler, the ACT Console, Extensions Log, and ACT wizards are supported only when DesignModeler is running on the Windows platform.

When using ACT for Fluent customization, ACT is supported only when Fluent is running on the Windows platform.

In a new Fluent installation, the initial attempt at opening the Extensions Log from the ACT Start Page does not display the log dialog box. Instead, Fluent shuts down unexpectedly. However, subsequent attempts at opening this dialog box are successful.

The ACT Debugger is supported only on the Windows platform from the Project page in Ansys Workbench and from DesignModeler and Mechanical. The ACT App Builder is supported only on the Windows platform.

The ACT App Builder is not supported in Ansys Electronics Desktop (AEDT). Clicking the Open App Builder icon on the ACT Start Page in AEDT will not start the App Builder.

Localization of ACT is limited to the languages currently supported in Ansys Workbench. This limitation does not apply to the ability to manage various languages within the extension. For example, the property names created by an extension do not have to be in the same language as the current activated language in Workbench.

There is no mechanism to integrate localization for the property names defined by an extension. To manage different languages for your property names, you must develop localization yourself. Both regional settings based on the "." or the "," decimal symbol are available. However, the implementation of the extension should use the "." symbol for any value defined at the XML or IronPython level.

The default location in which SpaceClaim is to look for ACT extensions is %ANSYSversion_DIR%\scdm\Addins. However, SpaceClaim is not currently recognizing this location. Workarounds include either installing extensions in %APPDATA%\Ansys\v242\ACT\extensions or using the gear icon on the graphic-based Extension Manager accessed from the ACT Start Page to add the folder for the default location or the folder to which you installed the extension.

ACT does not support Mechanical read-only mode. If you launch Mechanical and see read-only mode, avoid interactions with ACT extensions and features as changes could result in unexpected application behavior.

When renaming a caption for a custom object, do not follow a space with a number. While no error appears, the caption is not renamed. Workaround: When renaming a caption for a custom object, always follow a space with a non-numeric character before using a number. For example, rather than renaming a caption to "my custom object 2", rename it to "my custom object n2".

When ExtAPI.Extension.Attributes is used to store a value of type OrderedDict, an empty dictionary is stored instead of the supplied value.

When loading a project with custom ACT objects whose attributes have been filled with dictionaries, it takes Mechanical much more time to open. In cases where these dictionaries are very large, Mechanical may be unable to recreate results as ACT results, displaying user-defined results instead.

Accessing UserInterface on ExtAPI in Mechanical from an onInit callback or globally causes errors to be thrown in the Extensions Log, resulting in instability. Workaround: Access UserInterface from an onLoad callback or any place other than the onInit callback. Keep in mind that an onLoad callback is invoked only when Mechanical is started. Reloading an extension using the button in the GUI will not invoke an onLoad callback.

The Electronics Desktop module CoreGlobalScriptContextFunctions is unavailable in ACT. The following functions are available only through the Command window in Electronics Desktop:

As alternatives, you can use the following:

When you start the ACT Start Page on Linux, an unexpected shutdown can occur. On some Linux operating system variants such as Red Hat, removing the package totem-mozplugin resolves the issue:

yum remove totem-mozplugin

In some Linux versions, a JPEG library conflicts with the Ansys package. When using ACT wizards with JPEG images, this conflict can produce an SIGSEV error and an application crash. If this occurs, you can convert your images to other file formats such as GIF or PNG.

When no extensions are loaded, there are some limitations on the Graphics API from the ACT Console in Ansys DesignModeler and Mechanical. For instance, Factory2D does not work. Therefore, you should load one or more extensions before using the Graphics API from the ACT Console.