Responding to Crashes

When a crash occurs, you can email an incident report with supporting files to .

Crashes on Windows

If a crash occurs when running on Windows, restart your project with the debug executable and reproduce the crash. You can find the debug executable in the installation path (sos_console.exe) or using the environment variable SoS_debug_exe. When you start this command from a terminal, you get the complete traceback and possibly even error messages that can occur before the log system of oSP3D starts.

Crashes in optiSLang integrations

If a crash in an optiSLang integration occurs, attach the file in the subfolder sos_log from the respective working directory to the incident report. For example, the SignalMOP node creates such a folder in project.opd/SignalMOP/sos_log.

Crashes in the ACT extension for Ansys Workbench

If a crash occurs in the ACT extension for Ansys Workbench, add a user environment variable named SOS_ANSYS_LOG and set the value to 1. This causes the ACT plugin to write a log file to %USERHOME%\AppData\Local\Dynardo\Statistics on Structures on Microsoft Windows, including any debug messages.