Dwarf Fortress Bug Tracker - Dwarf Fortress
View Issue Details
0000444Dwarf FortressDwarf Mode -- Interface, Military Screenpublic2010-04-04 20:442010-06-13 02:10
Toady One 
PCVista 32-bit
0000444: Crash when attempting to enter military screen
Immediate crash after pressing m.
1. Load save game
2. Press m
Save game: http://buffered.info/junku/buffered-31.01-crash-military-screen.7z [^]

Prior to this crash happening, I only opened the military screen exactly once before. The steps taken back then were, in order:
1. Pressed m to enter military screen, no squads assigned yet since it is a new game.
2. Edit uniforms
3. Remove indiv. choice/melee from Leather
4. Add indiv. choice/weapon to Leather
5. Add indiv. choice/weapon to Metal
6. Remove indiv. choice/melee from Metal
7. Create new squad with Leather uniform
8. Added four or five dwarves to the new squad
9. Exited military screen

Then some time passed (at least 1 season) and when I tried to access the military screen again the reproducible crash started.
No tags attached.
child of 0000378resolved Toady One Crash when selecting specific squad in military screen (daggers) 
Issue History
2010-04-04 20:44BufferedNew Issue
2010-04-04 23:02DoctorZuberNote Added: 0001006
2010-04-05 10:02WtamerNote Added: 0001104
2010-04-05 17:59BufferedNote Added: 0001271
2010-04-05 18:10BufferedNote Edited: 0001271bug_revision_view_page.php?bugnote_id=0001271#r403
2010-04-06 05:09freezeNote Added: 0001400
2010-04-07 10:37freezeNote Added: 0001789
2010-04-07 10:37freezeNote Edited: 0001789bug_revision_view_page.php?bugnote_id=0001789#r532
2010-06-13 01:31Toady OneNote Added: 0008255
2010-06-13 01:31Toady OneStatusnew => resolved
2010-06-13 01:31Toady OneFixed in Version => 0.31.07
2010-06-13 01:31Toady OneResolutionopen => fixed
2010-06-13 01:31Toady OneAssigned To => Toady One
2010-06-13 02:10FootkerchiefRelationship addedchild of 0000378
2010-06-13 02:10FootkerchiefResolutionfixed => duplicate

2010-04-04 23:02   
There are already two verified crash bugs in the military screen which you can look at here. 0000035 0000156

If you think either of these may have caused your problem than this matter can be closed. If however you still think you have a new military crash issue it would be useful if you try to carefully walk through your steps and try to come up with a reliable way to reproduce your problem.
2010-04-05 10:02   
There's also 0000029 that appears to crash the game pretty reliably.

As for this one, I've tried to replicate it on my own installation (eliminating as many variables as possible) without any success. The crash probably had nothing to do with your prior fiddling in the military screen.

What were the circumstances surrounding the crash (ex: during a siege, ambush, traders arriving)? They might be linked.

Note that I haven't tried your save, just pointing out that the "recipe" included in additional information doesn't actually include the active ingredients.
2010-04-05 17:59   
(edited on: 2010-04-05 18:10)
The save will crash without fail, but indeed, performing the additional information steps again on a new fort hasn't recreated the crash so far. I may have to play the new fort more until a caravan arrives.

It could be related to 0000029, since the assignment section is what comes up first when you enter the military screen. There is no siege, no revealed ambushes, and no traders at the time of the save. No dwarves have died yet, but one of the squad members is in the hospital suffering from the unhealable throat bug, 0000168.

It probably has nothing to do with the schedule screen, which can still be viewed without crashing through the squad orders interface.

2010-04-06 05:09   
here's another save that reliably hangs any time m is pressed
http://www.sendspace.com/file/63newd [^]
2010-04-07 10:37   
resolved via the fix in 0000378, data\save\regionX\raw\objects\item_weapon.txt change [SKILL:DAGGER] to [SKILL:SWORD]

Toady One   
2010-06-13 01:31   
The save is no longer available. Going to go with the dagger theory until there's some more information. Feel free to reopen if 0.31.07 doesn't fix it.