Talk:SMOKREF.DAT
Offset 7: looks like a visibility flag. It is set to 1 when the SEEMAP.DAT entry of the tile indicates that the content of the ground has been seen (bit 3). Anyone can confirm the theory?
- Seb76 07:26, 12 February 2008 (PST)
If you set it to 1 for an out of sight smoke cloud, it'll remain unseen until your soldiers spot it.
By memory, if you set it to 0 for a cloud that should otherwise be visible, it won't appear.
I checked the cloud generated by a just-crashed UFO and all records were set to 0.
So it seems likely to me that it is a indeed a visibility flag. :)
- Bomb Bloke 15:04, 12 February 2008 (PST)
Offset 5
According code, this value increased when number of explosions happened around. new_density=summarized_density/overlaps-1 and after these calculations overlaps value nulled.--Volutar 10:35, 23 February 2011 (EST)
- So if I'm reading you right, every time smoke/fire gets assigned to a tile, this value goes up by 1. Say five smoke grenades go off and the smoke density (offset 3) goes through the roof. Once all the explosions have gone off in that turn/action/whatever, the density is then divided by the amount of explosions (minus one) in order to get a rough average figure, and the counter value is cleared.
- Presumably the calculation is only performed if there is more then one overlap, and it looks like the results will be skewed towards a higher figure then the actual average. Existing smoke clouds have a tendency to spread each turn, and this might go a long way towards explaining why a large area covered in smoke gets denser during the first few, then eventually dies out... - Bomb Bloke (Talk/Contribs) 17:48, 23 February 2011 (EST)
- MINUS ONE - is just an "end of turn" smoke dissolve action. Avaraging is done only for overlapped patches, of course. Spreading of smoke patches is another smoke processing procedure and it have nothing with dissolve and avaraging procedure. --Volutar 01:05, 25 February 2011 (EST)