When launched from Workbench, EnSight always opens using an EnSight Standard license; you cannot do parallel processing from within Workbench.

Workbench cannot effectively use the EnSight native, Case Gold data format due to Workbench limitations in the handling of large numbers of files.

Care must be taken when using EnSight Python and command language files from within Workbench. The Workbench interface relies on specific ordering of cases in the EnSight session and any Python or command language operations that modify case attributes (for example, names, etc) will conflict with Workbench conventions.

EnSight cannot be run in script-driven, batch mode using Workbench. Workbench will evaluate design points in batch mode if an EnSight session is not open, but there is no mechanism to run a specific script in batch mode.

When using design point parameter in the current release, Workbench is not automatically made aware of any EnSight constants that are created/activated. The list of design point parameters is updated when the EnSight task Enable Design Point Parameters property changes state. Therefore, if you have a running EnSight session and use the calculator to create a new constant that you wish to appear in the current Workbench design point variables, one may need to uncheck and recheck the Enable Design Point Parameters property.

The current EnSight session state is explicitly linked to the collection of solutions marked as inputs into the EnSight Results task in Workbench. If one changes the inputs (for example, adds an additional solution or removes one), the state of the EnSight session will be reset to the default (the EnSight context file will be reset). It is strongly recommended that users configure all of the inputs to the EnSight Results task before setting up the visualization in EnSight that they would like to be retained.

When using CFX data, the EnSight default is to just show some of the variables. Check the Advanced toggle to see all possible variables and to load all timesteps.