General Settings

To change the general settings, navigate to Settings | Application Settings.

Section Enable Autosave

If the Enable Autosave box is checked, the Fenix+ 3 application automatically saves the project that is currently being worked on at a specified time interval.

{width=80%}

Saving a large project requires some time. During this time, the project is unavailable for editing. Therefore, when working with large projects, it is not recommended to set short autosave intervals.

Text Settings

{width=80%}

There are two caption display modes in the Fenix+ 3 application:

1. Constant size on screen (used by default). In this case, regardless of the scene scale, the text and caption size (in pixels) on the screen is always the same. Accordingly, the text size in the world coordinate system (in meters) will vary with different scene scales.
2. Constant size in the world coordinate system. In this case, the text size in the world coordinate system is constant, but the size on the screen changes depending on the scene scale.

Depending on the selected mode, the Size text property is interpreted differently. For details, see the Text section.

In the first case, this is the standard font size accepted in text editors, and in the second, it is the maximum height of font symbols in meters.

The default text size is set in the field next to the name of the corresponding mode.

This size is also used when creating automatic text when generating a report. For example, registering devices signatures.

Since the display mode is an application setting, there might be situations where, when opening the same project on different PCs, text is displayed differently. This happens if the display mode on the PC where the project was created differs from the one set on the PC where the project is opened. In such cases, changing the display mode is sufficient.

FDS Settings

{width=80%}

To conduct a Fire Dynamics Simulation, it is necessary to configure FDS settings.

When you first launch the Fenix+ 3 application, the parameters necessary for FDS operation are initialized - the paths to the FDS executable files are determined.

In some cases, such as non-standard application installation ways, incorrect values may be assigned to parameters. Therefore, before starting the fire dynamics simulation, it is recommended to check the necessary parameters and adjust them if necessary.

Description of FDS parameters:

• fds.exe - path to the FDS executable file.

The application uses this executable file for running simulation in both single thread and multi-thread modes.

• smokeview.exe - path to the Smokeview executable file (necessary to visualize the calculation results).

• mpiexec.exe - path to the MPICH2 library executable file, which is required for multi-thread mode of the fire dynamics simulation.

The application uses the executable file mpiexec.exe to run fire dynamics simulation in multi-thread mode. For details, see Setting Fire Dynamics Simulation Parameters.

If some values are not specified, you can enter them manually. To do this, click the Browse… button next to the corresponding parameter and specify the path to the required file.

In addition to specifying the paths to the executable files fds.exe and mpiexec.exe, you may need to add them to the permissions list of the Windows Firewall and installed antivirus.

There are two ways to add permissions to the firewall:

1. Launch the firewall and manually create a rule for the fds5_mpi.exe, fds.exe and mpiexec.exe applications specified in the FDS settings window.
2. Allow access in the windows that appear when you first run the fire dynamics simulation in multi-thread mode.

{width=60%}

Updates

{width=80%}

If the Check for updates automatically at startup checkbox is enabled, Fenix+ 3 sends a request to the mst.su website to check for an official application update each time the application is started. This checkbox is enabled by default. Disabling this feature can reduce the time required to launch the application if there is no Internet access or if the connection is very poor.

Fire results presentation

{width=80%}

When viewing the results of fire dynamics simulation, the presentation of the displayed dangerous fire factors (DFF) on the graph may differ.

If similar DFFs are selected (for example, temperature or visibility), the application can display either their absolute values or their values relative to the critical value. In the first case, the graph displays actual values of the selected DFF, and the red line shows its critical value. In the second case, values of the selected DFF are displayed in relation to the critical value, which equals to 1.

To display absolute values of the seclected DFF, select the Absolute option. To display values in comparison to the critical value, select the Relative to critical value option.

When you select different DFFs (for example, temperature and visibility), values are always displayed in relation to the critical value. For more information, see Fire Dynamics Simulation Results.

For the convenience of analyzing the fire dynamics simulation results, you can select the desired graph display mode. The following options are available:

• Point;

• Line.

You can use the following presentations for the fields of DFFs:

• Continuous gradient - the DFF field is an image in which the color of each point corresponds to the DFF value. All values of the DFF that exceed the critical value are indicated in red. Default (safe) DFF values are displayed in blue. All colors used, as well as the top and bottom boundaries of the range of DFF values ​​are presented on a scale of values.

{width=80%}

• Discrete intervals (selected by default) - the field is an image where different value ranges of the DFF ​​are indicated by different colors without a gradient. The critical value corresponds to the boundary at which the transition occurs between the intervals where the DFF exceeds or does not exceed the critical value. All colors used, as well as their corresponding ranges of values, are presented on a scale of values.

{width=80%}

Project Verification

{width=80%}

This section is used for setting up the project verification tool. For information, see the Project Verification section

In the project verification settings, you can specify what verification procedures the application performs.

By default, all checks are enabled and are always performed before simulating evacuation and fire dynamics.

If automatic project verification before fire dynamics simulation is enabled, general checks and checks for fire dynamics simulation are performed. If automatic verification before evacuation simulation is enabled, general checks and checks for evacuation simulation are performed.

Checks for critical errors in the settings window are highlighted in red. These checks cannot be disabled.

Regardless of whether automatic verification before simulation is enabled, checks for critical errors are always performed before conducting a simulation. Checks for possible errors and inaccuracies are only performed if the corresponding automatic check is enabled.

When hovering the mouse cursor over the name of the check in the Verification Purpose field, a description of the check appears, as well as the errors or inaccuracies that the check is used to detect.

Rendering Modes

Use these settings to configure the thickness of lines that are used when displaying objects.

You can change the thickness of the lines in the range from 0.10 to 5 pixels. By default, the line thickness is 1.5 pixels.

References

To specify the materials and people profile database, materials and people profiles from which will be used in the project (User Database), click the Browse button and specify the path to the required database. By default, the databases located in the C:\Users\USER_NAME\AppData\Roaming\MST\APPLICATION_VERSION\DataBases folder are used as user databases.

There are two modes for using the database:

1. Use one database for all projects. In this case, the same database is used for all projects. If the material and people profile parameters change in one of the projects, they are changed in all other projects where the same materials and people profiles are used. This change occurs the moment you open another project. This mode is the default.
2. Create a copy of the database for each project. In this case, when creating a project, the DataBases folder is created in the project folder, which contains a copy of the User Database. Further, all changes to the properties of materials or people profilea is only in these databases and does not apply to other projects. For details, see Project Directory Structure.

To save the changes made, click Apply.