This is the sequence.
1. Flying YAK-53 at KHAF with TS. No problem. (as far as I know this aircraft doesn't have crash fire)
2. Accept an invitation to test somebodies work on A-6B Gituber. (aircraft could contain crash fire)
3. Spawn at SVMI with TS failing terrain, waiting for so long, checked terminal wildfire cells active. 200%. PC Emer shoot down.
4. Start FG again with YAK-53 at KHAF. Problem Wildfire cell active problem 2500% CPU even worst because KHAF terrain exists. More load. PC Emer shoot down.
5. Spawn same YAK-53 at a little airport, getting less time loading FG. Very fast uncheck menu wildfire and save it by ESC + accept.
6. GOTO 4 It seems is not saved.
7. GOTO 5
8. Following AndersG recommendation
--prop:/environment/wildfire/enabled=0 This causes no effect, FG starts with wildfire cells.
NOTATIONS
Initially It seems fire was declared when spawning with no terrain, however seems to be portable to other aircraft and places. I notice on terminal where (I have debug level=info) the wildfire cells procedure begins before terrain is finished. I mean looks like there is no priority.
This is an quick extract of the terminal info, just before PC Emer shoot down
- Code: Select all
Wildfire: generation 380589235 updating 1120 / 23255 created cells. 1010 burning cells.
Wildfire: generation 380589236 updating 1102 / 23324 created cells. 1033 burning cells.
Loading tile 942025.stg
Generating ocean tile: w130n30/w123n37/942025
Loading tile 942027.stg
Wildfire: generation 380589237 updating 1105 / 23402 created cells. 1027 burning cells.
Loading stg file Path "/home/michat/.fgfs/TerraSync/Objects/w130n30/w123n37/942027.stg"
Loading stg file Path "/home/michat/.fgfs/TerraSync/Terrain/w130n30/w123n37/942027.stg"
Wildfire: generation 380589238 updating 1110 / 23489 created cells. 1023 burning cells.
Wildfire: generation 380589239 updating 1142 / 23609 created cells. 1022 burning cells.
Wildfire: generation 380589240 updating 1128 / 23700 created cells.
Thank you.