0010466: Magma-safe raised bridges deconstructing

Notes
(0037382) Quietust (reporter) 2017-12-22 18:22 edited on: 2017-12-22 18:23	If the bridges contained non-magma-safe mechanisms, then what happened is normal - if any component of a building melts, then the entire building deconstructs. A save file upload would help confirm that this is what actually happened here.

(0037383) Agent Wowza (reporter) 2017-12-22 23:55 edited on: 2017-12-23 00:06	However, out of the nine bridges, only ones which contained mechanisms made of materials which have a melting point lower than or equal to 11500 U deconstructed, such as those containing granite or microline mechanisms. The other bridges contained hornblende and diorite mechanisms but did not deconstruct. Also, none of the bridges deconstructed for about a year when the remained closed. Does this mean the mechanism is only exposed to magma when the bridge is lowered? Link to zipped save file: https://drive.google.com/open?id=1F0hGbvsBIh_1ZhuEVPDY-Gc7pCtwQVBi [^]

(0037384) Quietust (reporter) 2017-12-23 06:23 edited on: 2017-12-23 06:26	Looking at your save, all of the behavior you described is 100% expected - if the bridge contains even one non-magma-safe mechanism, then that mechanism will melt when the bridge opens and cause the whole building to deconstruct. I lowered all 28 bridges (on both Z-levels), and after several minutes (running at only 5-6 FPS) nearly all of them melted (in order of increasing melting temperature), except for the 9 which didn't have magma-unsafe mechanisms. The reason it only deconstructs when the bridge is lowered is because the mechanisms are logically located at the center tile of the bridge - if you used an actual drawbridge, you could also see the bridge melt while raised if it was blocking the magma from the inside rather than from the outside. For the record, this is all documented on the wiki: http://dwarffortresswiki.org/index.php/DF2014:Magma-safe [^]

(0037389) Loci (manager) 2017-12-23 13:33	Indeed. The wiki is a good reference for expected behavior, as are previous bug reports (0008216, 0005983, 0003444).

Issue History
Date Modified	Username	Field	Change
2017-12-22 11:23	Agent Wowza	New Issue
2017-12-22 18:22	Quietust	Note Added: 0037382
2017-12-22 18:23	Quietust	Note Edited: 0037382	View Revisions
2017-12-22 23:50	Agent Wowza	Issue Monitored: Agent Wowza
2017-12-22 23:50	Agent Wowza	Issue End Monitor: Agent Wowza
2017-12-22 23:55	Agent Wowza	Note Added: 0037383
2017-12-23 00:06	Agent Wowza	Note Edited: 0037383	View Revisions
2017-12-23 06:23	Quietust	Note Added: 0037384
2017-12-23 06:26	Quietust	Note Edited: 0037384	View Revisions
2017-12-23 13:33	Loci	Note Added: 0037389
2017-12-23 13:33	Loci	Status	new => resolved
2017-12-23 13:33	Loci	Resolution	open => no change required
2017-12-23 13:33	Loci	Assigned To	=> Loci

Relationships