Dwarf Fortress Bug Tracker - Dwarf Fortress
View Issue Details
0001610Dwarf FortressMap Featurespublic2010-04-28 11:132014-02-17 11:31
Logical2u 
Footkerchief 
normalminorN/A
resolvedduplicate 
LG P300 (Laptop)Windows 7Professional x64
0.31.03 
0.31.03 
0001610: Buggy volcano - warm stone flag not properly placed on tiles around volcano
See - http://img202.imageshack.us/img202/3171/buggyvolcanotiles.png [^]

The volcano seems to have generated warm tiles inappropriately. I first noticed an issue when there was an arbitrary warm tile quite far away from the volcano proper. The issue didn't stop at the volcano, as shown here.

Some tiles of obsidian surrounding the volcano are not flagged as warm, even though they are surrounded by magma, and surrounding stones are warm. (Edit: This is true all the way up and down the height of the volcano)
Generate the world according to the parameters below.
Embark on the location in the image below.
Go to the designation menu and investigate tiles surrounding the volcano.
http://pastebin.com/vU5mkip3 [^]

Fortress location: see http://img707.imageshack.us/img707/470/fortresslocation.png [^]
No tags attached.
duplicate of 0005077resolved Toady One Browsing world gen map causes corrupted feature files 
related to 0001272new  Warm stone status is not cleared properly 
has duplicate 0003294resolved Logical2u Walls are not being properly marked as warm stone. 
Issue History
2010-04-28 11:13Logical2uNew Issue
2010-04-28 11:21Logical2uDescription Updatedbug_revision_view_page.php?rev_id=2031#r2031
2010-04-28 11:21Logical2uSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=2033#r2033
2010-04-28 11:48FootkerchiefRelationship addedrelated to 0001272
2010-04-28 11:54Logical2uDescription Updatedbug_revision_view_page.php?rev_id=2038#r2038
2010-05-27 19:32Logical2uAdditional Information Updatedbug_revision_view_page.php?rev_id=2768#r2768
2010-09-21 18:06Logical2uRelationship addedhas duplicate 0003294
2010-09-25 21:53GauHelldragonNote Added: 0012991
2010-09-28 15:11LemundeNote Added: 0013043
2010-09-28 17:06Logical2uNote Added: 0013047
2010-10-03 03:28jeiNote Added: 0013161
2011-07-07 19:30Khym ChanurNote Added: 0018152
2011-07-08 18:51dree12Note Added: 0018159
2014-02-17 11:31FootkerchiefNote Added: 0024528
2014-02-17 11:31FootkerchiefRelationship addedduplicate of 0005077
2014-02-17 11:31FootkerchiefStatusnew => resolved
2014-02-17 11:31FootkerchiefResolutionopen => duplicate
2014-02-17 11:31FootkerchiefAssigned To => Footkerchief

Notes
(0012991)
GauHelldragon   
2010-09-25 21:53   
I've found a similar problem with one of my forts down in the magma sea, about 150+ zlayers deep
(0013043)
Lemunde   
2010-09-28 15:11   
I did some testing and found out that this happens when you have temperature disabled. Enabling temperature fixes it.
(0013047)
Logical2u   
2010-09-28 17:06   
That would be great and all but I never had temperature disabled.
(0013161)
jei   
2010-10-03 03:28   
WARM STONE LOCATED, no magma around. Savegame below.

One straight empty pipe found, also volcanoes no longer show variations in Z-axis, which they used to. Now they're just straight unnatural pipes.

http://dffd.wimbli.com/file.php?id=3211 [^]
(0018152)
Khym Chanur   
2011-07-07 19:30   
Version 0.31.25, found this problem with a magma sea. Embarked with temperature off, but turning it on and saving/restoring doesn't fix it, even if I leave the game unpaused for a while. I re-embarked in the same location with temperature on, and the same problem happens. The site does have a magma pipe, which might be what's causing the problem. Oh, and this is playing on Linux.

I have a save available on request, which has problem areas hotkeyed with F2, F3 and F4.
(0018159)
dree12   
2011-07-08 18:51   
Warm stones DO NOT require magma. In the old 0.31.0x days, the scorching environments produced WARM buildings and hillsides, simply cause it was too hot. The stones next to magma that are not warm is the only bug here.
(0024528)
Footkerchief   
2014-02-17 11:31   
jel's save has feature corruption. Unless there's a non-corrupted save that shows this problem, we can probably chalk it up to 0005077.