|
Bug Reports: If you think you have found a bug within FlamMap, we would appreciate hearing from you. Please check below to make sure that this problem has not already been resolved. Then, send us a copy of any screenshots or a detailed error message describing the problem and what you were doing with the problem arose. This will help us to recreate the problem and then fix it.
Bug Reports should be sent to the National Support Desk.
Thank you very much for your help!
Known Bugs with FlamMap:
| FlamMap Version 3.0 |
|
| FlamMap crashes on Forest Service computers running Windows XP operating system |
| Description |
FlamMap crashes partway through the run. This bug has only appeared on Forest Service computers running Window XP. This can be confused with another bug (see below) that occurs on all computers when utilizing a conditioning period in a FlamMap run.
|
| Status |
This bug is being investigated to find the best way to fix it.
|
| Work Around |
Three work arounds exist for this bug.
- If FlamMap was installed while the user had Administrative Privileges (the usual case), run FlamMap while after again acquiring Administrative Privileges. Administrative Privileges can be acquired for the current day at http://gadgets.ds.fs.fed.us/EUTools/ad_promote.asp.
- While you have Administrative Privileges, change the Permissions of the C:\Program Files\Flammap3 folder to Full Control for the Users group.
- Reinstall FlamMap in a folder other than C:\Program Files when the user DOES NOT have Administrative Privileges. One suggested location is to create a C:\FlamMap3 folder to install in.
|
|
| FlamMap crashes when attempting a run using the conditioning period feature |
| Description |
FlamMap crashes when attempting a run using the conditioning period feature but runs successfully when not attempting the use of a conditioning period.
|
| Status |
This bug will be fixed in the next release of FlamMap early in 2008.
|
| Work Around |
This problem occurs when FlamMap attemps to adjust the fuel moisture for a cell and a NODATA value for one of the topographic themes is found. You can check this by looking at the number of NODATA cells for each of the topographic themes. The number of NODATA cells should be the same for all three of the topographic themes. If one of the themes is different (usually the slope theme) that theme needs to be recreated. Usually the problem shows up when the cells with no slope are given a NODATA value instead of 0 or -1.
|
|
| Problem viewing ASCII grids created with FARSITE |
| Description |
ASCII grids created in FARSITE do not display correctly when viewed in FlamMap v3.0.0. After loading the grid the display pane appears blank, but on closer inspection (and perhaps zooming in) you will see a single column of cells displayed along the left side of the display pane.
|
| Status |
This bug is planned to be fixed in the next release of FlamMap.
|
| Work Around |
A work around is to import the FARSITE grids into a GIS, then export them as ASCII grids and they should then display correctly in FlamMap.
|
|
| Unable to Open Saved or Archived FlamMap Projects |
| Description |
When attempting to reopen a previously saved FlamMap Project (.fmp) file the "Unable to find Ideal Landscape File" error message appears and the project will not open. When attempting to load an archived project (.fza) file a generic error message appears and FlamMap crashes.
|
| Status |
This bug is planned to be fixed in the next release of FlamMap.
|
| Work Around |
If you are attempting to open a FlamMap Project (.fmp) file first make sure the Ideal Landscape (.lcp) file has not been moved or renamed sine the project was last saved. If this is not the case it appears there is no way to open the saved .fmp or .fza files.
This problem has only been observed with projects containing large landscape files and multiple TOM/MTT runs. So limiting saved projects to one TOM/MTT run may prevent the problem. You can also save the results as individual ASCII grids or shapefiles as a precaution.
|
|
|
|
Last Updated ( Friday, 15 August 2008 )
|
FlamMap 
