Known anomalies

The list identifies the known anomalies in
FactoryTalk Optix Studio
version 1.0.3.
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.
Error opening project located on OneDrive [1911544]
When a project is located on OneDrive, pulling an update from the remote repository may result in an error when the project is opening. Restart
FactoryTalk Optix Studio
and reopen the project.
This anomaly first identified in version 1.0.2.
Incompatibility between FactoryTalk Optix Studio and FactoryTalk Motion Analyzer [1844818]
Installing
FactoryTalk Optix Studio
and FactoryTalk Motion Analyzer on the same computer prevents FactoryTalk Motion Analyzer from working.
This anomaly first identified in version 1.0.2.
Tag write error appears on all controls referencing the tag in error [1765666]
When a tag write failure occurs such as when writing to a safety tag, the expected error message appears briefly on all controls that reference the tag. The error appears on labels instead of only controls that attempt to write to the tag.
This anomaly first identified in version 1.0.2.
Unable to connect to Logix controllers from the Emulator using FactoryTalk Optix Studio in the web version [1900931]
Unable to read and write to logic controllers when emulating a project using
FactoryTalk Optix Studio
in the web version. Use the
FactoryTalk Optix Studio
desktop editor to emulate projects that reference Logic controllers.
This anomaly first identified in version 1.0.2.
Trend line is drawn when no data is logged for a period of time [1911501]
When trending historical data from a database, a trend line is drawn between points when the logger is not capturing data.
This anomaly first identified in version 1.0.2.
MouseClick and MouseUp events perform when clicking and holding a button when remote desktop does not have focus [1932679]
Clicking and holding a button on remote desktop when remote desktop does not have focus automatically increments the button if it is configured with MouseUp and MouseClick events. This is because bringing focus to remote desktop by clicking and holding the button automatically performs MouseUp and MouseClick events.
This anomaly first identified in version 1.0.2.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.