Known anomalies in this release

Use the identification information in parenthesis to track the anomaly in future releases or for reference when receiving assistance from Customer Support with a related issue.

DNS names used in the

SubjectAltName

field of the certificate configuration are only recognized if they are lower case.

This anomaly first identified in version 1.2.0.

Special characters are not supported in PDF filenames, FTP Server usernames, Git repository names, ODBC database names, or when using the Microsoft Pinyin input method on the device or at design time in FactoryTalk Optix Studio web editor.

This anomaly first identified in version 1.2.0.

Deploying to a device with a name that contains a slash results in an error or the application not running on the device.

This anomaly first identified in version 1.2.0.

Pulling from the remote repository when an Object Type name has been modified both remotely and locally causes a merge conflict. The operation creates two different objects when keeping local changes and causes the loss of the renamed type when accepting remote changes. To avoid data loss, all users collaborating on the project must manually update the Object Type name on their local project before pulling from the remote repository.

This anomaly first identified in version 1.2.0.

The Compute Module cannot communicate with the controller if there is more than one Backplane in the controller path. For example, the module is unable to communicate with the controller if the path is Backplane\1\A\10.220.173.66\Backplane\3. However, paths resembling either Backplane\3 or Backplane\1\A\10.220.173.66 allow the module to communicate with the controller.

This anomaly first identified in version 1.2.0.

If an image file in a project does not appear in the runtime application, use a third party application to resize the image and make it smaller.

This anomaly first identified in version 1.3.0.

Filenames cannot contain special characters.

This anomaly first identified in version 1.3.0

Assigning a string tag to a Discrete input memory area does not display an error message and causes read errors on all tags for the Modbus Station containing the mis-configured tag.

This anomaly first identified in version 1.3.0.

OneDrive is not recommended for storing user-defined libraries and may result in synchronization errors and duplicate files when renaming libraries. If attempting to use OneDrive to rename a library, unlink OneDrive when renaming the library. To unlink OneDrive, see Turn off, disable, or uninstall OneDrive.

This anomaly first identified in version 1.3.0.

If you modify only the value for Range high or Range low for a sparkline, the range cannot display in sparkline. Modify both the value in Range high and Range low to display the range in the sparkline.

This anomaly first identified in version 1.3.0.

Elements added to a custom library do not appear in

Libraries

search until you restart FactoryTalk Optix.

This anomaly first identified in version 1.3.0.

If you emulate a project on a computer that is running

Microsoft®

Windows®

, some videos may not play. Videos will play if you deploy the project to a device.

This anomaly first identified in version 1.1.0.

The Emulator cannot run a project that contains a Rockwell Automation EtherNet/IP station if FactoryTalk Optix Studio is installed in a folder that contains a special character.

This anomaly first identified in version 1.3.0.

FTOptixRuntime.exe cannot launch if you export the project to a folder with a name that contains a special character.

This anomaly first identified in version 1.3.0.

Setting the environmental variable FTOPTIX_RHI_BACKEND to "opengl" may resolve this issue.

This anomaly first identified in version 1.3.1.