Skip to content

Known Bugs and Issues

Jump to bottom
heinsch-fa edited this page Oct 9, 2026 · 12 revisions

Think you found a bug in Behave7?

  • Check the Known Bugs below and the Frequently Asked Questions (FAQs) page to make sure the problem has not been reported or resolved.
  • If it hasn't, contact the IIA HelpDesk.
    • Be prepared to provide a detailed description of the issue and send screenshots that help describe the issue.
    • If possible, describe what you were doing in Behave when you found the issue.
divider

ComputerBug_20261007 Known Bugs, Behave Version 7.1.5

Note

💡 Interpreting the Bug Reports

  • Click on the title to view more information about a bug. Click on the title again to collapse the section.
  • If a module is listed in the title, we believe the bug only affects that module.
  • If no module is listed, the bug affects something in every module.
  • If a bug has been scheduled for resolution, the Status will show the version number.
  • If a bug has not yet been scheduled for resolution, the Status will be Reported. This only means it has not yet been added to the development calendar.

All Modules: Scrolling through selections for Fuel Model and GACC
  • Description: Select values in the the Fuel Model or GACC categories and scroll part of the way through the list. When you select a new category, you will see the middle of the list.
  • Reported: June 11, 2026
  • Status: Scheduled to be fixed in v7.1.6
  • Workaround: There is no workaround for this bug.

Surface Only, Surface & Mortality, Surface & Contain: Units for Fireline Intensity are “Null” in the Table Shading Filters
  • Description: On the Review Run tab, Fireline Intensity (FLI) shows units as "null" when Direction Mode is set to Heading or Direction of Interest and Fireline Intensity is selected as an Output. Fireline Intensity in the Direction of Interest includes units. Note: Fireline Intensity is calculated for a Heading fire unless otherwise specified. To see the error, click on this link and view the areas highlighted yellow. Note: To open the link in a new window, click Ctrl and then the link.
  • Reported: August 18, 2026
  • Status: Scheduled to be fixed in v7.1.6
  • Workaround: Output tables and graphs show the correct units for Fireline Intensity. Continue to use it as desired. Default units for FLI are Btu/ft/s (English) or kW/m (metric).
Error, Fireline Intensity Units do not show in Review Inputs tab.

Settings: Missing or incorrect units
  • Description: In Settings, some variable domains include incorrect or incomplete unit sets. If you select an incorrect unit, it will not appear in the worksheet.
  • Reported: June 17, 2026
  • Status: Scheduled to be fixed in v7.1.6
  • Workaround: If it is an input, create a run and look at the dropdown menu to the right of a variable to view the associated list of units. Select only those that make sense for the input (for example, DBH = in, cm) or the module. There is no workaround for output variables.

Finding Valid Units for Input Variables

Settings: Some settings are saved within Behave7 and appear the next time you open it.
  • Description: Behave is designed to maintain settings during your current session. However, if you update any Settings, including module selection and variable units, they may persist and appear the next time you open a run. This can also occur between versions (for example, 7.1.3 and 7.1.5). This . For example, if you choose to run Surface & Crown, it will be highlighted the next time you open Behave. This occurs even if you do not save a run.
  • Reported: October 01, 2026
  • Status: Scheduled to be fixed in v7.1.6
  • Workaround: When setting up a run, review the settings to ensure they are set correctly, especially if you changed them previously.

Surface & Contain: Individual Resources are plural
  • Description: The headers for individual Contain Resources are plural (see example below). For example, The input window will show Resources #1 instead of Resource #1.
  • Reported: March 03, 2026
  • Status: Scheduled to be fixed in v7.1.6
  • Workaround: There is no workaround for this bug.

Contain Resources are plural

Surface & Mortality: Multiple tables are created for fire behavior outputs
  • Description: In Surface & Mortality, if you select more than one Mortality tree species, Fire Behavior output tables are created for each tree species, even though the fire behavior does not change.
  • Reported: October 06, 2026
  • Status: Reported
  • Workaround: There is no workaround for this bug.

Settings: When Importing a Run, Output Units cannot be changed if they do not match the default settings in Behave.
  • Description: Unit selection preferences for output variables cannot be changed if you import a run with settings that do not match the default settings.
  • Reported: September 25, 2025
  • Status: Reported
  • Workaround: Create a new worksheet, which allows you to select the units you wish to use.

Surface & Mortality: Both Crown Length Scorched and Crown Volume Scorched appear in results
  • Description: Crown Length Scorched (CLS) and Crown Volume Scorched (CVS) should only be displayed if they are used to calculate mortality for the selected tree species. If both variables are used in the calculations, values should only appear if that variable is used to model mortality for a species.
  • Reported: July 13, 2025
  • Status: Reported
  • Workaround: There is no workaround for this bug.

Surface & Mortality: Bark Char Height appears in results, even if the Crown Scorch Equations are used
  • Description: Bark Char Height appears in the Results, even if the Equation Type is Crown Scorch and Bark Char Height is not used.
  • Reported: November 18, 2025
  • Status: Reported
  • Workaround: There is no workaround for this bug. Ignore the Bark Char Height when interpreting results unless a "bark char" equation is used to calculate Probability of Mortality.

Settings: Users may not be able to scroll in the settings box
  • Description: The Settings box size does not always let users scroll down. This bug is dependent upon computer screen size.
  • Reported: February 17, 2026
  • Status: Reported
  • Workaround: There is no workaround for this bug.

All Modules: Input values are not stored with saved runs
  • Description: When importing a run, some inputs are missing because they were not imported. This behavior is inconsistent. It will not happen with every worksheet, nor does it occur to specific inputs.
  • Reported: June 18, 2025
  • Status: Reported
  • Workaround: If you share a run with others, include a copy of the PDF so that they can enter any missing inputs.

Printing: Run Description missing in outputs of PDF
  • Description: The Run Description will not be printed to the PDF unless the run has been saved.
  • Reported: November 05, 2025
  • Status: Reported
  • Workaround: Save a run prior to creating a PDF if you are including a Run Description.
divider

Squashed Computer Bug Squashed Bugs

Version 7.1.5, Released at some point in the past

The following bugs from earlier versions were squashed in Version 7.1.5.

  • Surface & Contain: Fire Behavior sub-module must be clicked in Contain when using the Guided Workflow

    • Description: When running Contain in the Guided Workflow, users must click on the Fire Behavior outputs sub-module to view Fire Behavior inputs and results.
    • Reported: Unknown

  • Results: Table Shading filter is inconsistent

    • Description: Table Shading filters do not consistently highlight results, likely due to rounding within the system.
    • Reported: Unknown

  • Results: Difficulty reading results on line graphs

    • Description: Line graph outputs sometimes appear on top of the axis, making it difficult to view or interpret results
    • Reported: Unknown

  • Surface Only, Surface & Mortality: Table and graph order for Heading, Flanking, Backing and Direction of Interest

    • Description: When running either single or ranged inputs when either Heading, Flanking, Backing or Direction of Interest is selected, table and graph order is inconsistent. The order should be Rate of Spread, Flame Length, and Fireline Intensity within each spread direction. This applies to all tables and graphs.
    • Reported: Unknown

  • Results: Graph Legend is blank if there is only one ranged input

    • **Description:**f there is only one ranged (multi-valued) input provided, the graph legend appears blank.
    • Reported: Unknown

  • Surface Only: Missing inputs for Spotting Distance from a Wind-Driven Surface Fire when Dead, Live Herb, and Live Woody Categories is selected

    • Description: When Spotting Distance from a Wind-Driven Surface Fire is an output, and one of these fuel models is used (FB1/1; FB3/3; GR1/101; GR2/102; GR6/106; GR7/107; GS1/121), Dead Moisture is not a required input. Results are calculated, but are incorrect.
    • Reported: Unknown

  • Results: Saved runs using Table Shading Filters do not retain Minimum and Maximum filter values.

    • Description: When importing a worksheet with a table shading filter, the filter is enabled, but the minimum and maximum values are not preserved.
    • Reported: Unknown

  • All Modules: New lines do not appear in Notes

    • Description: If users enter a line break when modifying or editing a note, it is ignored. The note appears as a single line
    • Reported: Unknown

  • Settings: Extraneous Units in Settings

    • Description: Extra units for inputs and outputs appear in the settings for most variables. Behave7 will only use the appropriate units for a variable. If invalid units are selected, Behave7 will use the default units.
    • Reported: Unknown

Logo for Behave version 7

Home

For the latest information, visit the Behave website on Frames.

Overview of Behave7

Software Installation and Release Notice

Additional Information

Clone this wiki locally