The most common warning messages are listed below along with a brief description
of what they mean and how to avoid them in future.
Module not loaded
The project requires a plug-in module that is not currently installed. When the
project is loaded, Overture should prompt to install the module automatically. Try
reloading the project and accept the prompted update.
Assembly not loaded
The project requires an assembly that is not currently installed. Assemblies are
installed by modules, so it is highly likely that modules are also missing. See
the entry above regarding missing modules.
Analysis Folder Clash
Overture projects store all analysis files in a folder called 'Analysis' that is
located in the same folder as the project file itself. Two projects from the same
folder cannot be opened at once or there can be clashes between analysis files.
To prevent this happening in future, move the project files into different folders.
Calculated Flags are read-only and cannot be set
Some entity flags are calculated automatically and hence cannot be set manually
or through a spreadsheet import. This warning often happens because the spreadsheet
export naturally contains these flags, but the import does not allow them. This
warning only means that the column for this flag was ignored, the rest of the import
is unaffected. To avoid it in future, remove read-only flags from the import spreadsheet.
Unknown Import Entity ID
Every component within Overture has a unique ID (a GUID). This allows them to be matched up in future merging
operations such as spreadsheet import even if their names have changed. This warning
means that the ID in the imported spreadsheet could not be matched to anything in
the project, however Overture will still try to match entities by name if it can.
The warning is issued because this fall-back behaviour might not be what you expect.
Failed to create mesh file
Mesh files are Overture's file-based grid system for storing analysis data.
This error message can occur when