Simcenter Amesim How to visualize customized components in related assistant (visualization tool - e.g PLMASSEMBLY, M6DOFASSEMBLY, ACFATTISIMP001, ... )

Simcenter Amesim Automation Connect Simcenter System Simulation Client for Git Simcenter Amesim Teamcenter Share


When customizing components in Amesim's Submodel Editor Tool (Ameset), users often encounter an unexpected situation: their customized component disappears from its visualization assistant. This behavior might initially seem puzzling, but there's a straightforward reason behind it.


Configuration files play a crucial role in software applications, especially in visualization tools. A configuration file like AMEAssistants is necessary for visualization applications. In Simcenter Amesim, this file is located in its library directory (e.g. %AME%\libplm, %AME%\libacf, ... )

By externalizing component and visualization mappings to a configuration file, developers allow for easier updates and modifications. For instance, if a new submodel is added or an existing one changes, only the configuration file needs to be updated rather than the software's core codebase.

When we customize a submodel or create a new one, this change is not automatically reflected in the AMEAssistants configuration file.

Since the visualization assistant depends on this file to know which components to display, we need to update the file to include an entry for your new component and make it visible.

For instance, if I have customized an acf submodel that can be visualized in its library assisitant I should add its "plugin name",  "submodel name" and "classname" in its related configuration file, as follows:



Without being listed in the configuration file, the assistant won't recognize the submodel as a valid or supported component for visualization.


KB Article ID# KB000122281_EN_US



Associated Components

Amesim Automation Connect