Dwarf Fortress Bug Tracker - Dwarf Fortress
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0010626Dwarf FortressAdventure Mode -- Generalpublic2018-03-14 16:402018-03-28 19:25
Reportersquamouss 
Assigned ToToady One 
PriorityhighSeveritycrashReproducibilitysometimes
StatusassignedResolutionopen 
PlatformOSOS Version
Product Version0.44.07 
Target VersionFixed in Version 
Summary0010626: Experiencing a crash when exiting fast travel and encountering another group/entity
DescriptionWhen you are close to an asterisk in fast travel there is a chance that you will crash on exiting it if you are close enough to the creature. It seems like a pretty big deal considering how many times such a scenario is going to happen in play, hence my rating.

Here is a bugged (modded) save that is repeatedly experiencing the issue: http://dffd.bay12games.com/file.php?id=13566 [^]
Steps To ReproduceI've experienced this bug on both vanilla and modded saves, but as it happens I found a reproducible instance in my modded game so that's the save file here. Upon loading the save, you will be playing a creature in a hamlet. Just enter the overworld travel screen, and you will find yourself near an asterisk. Attempt to travel to that asterisk and exit the fast travel screen, or simply end up adjacent to it and let it encounter you. In all situations, you will end up crashing. Using legends mode and other utilities, I have ascertained that the creature within the asterisk is a procedurally generated night creature, and thus I suspect the issue is part of the vanilla game even though it occurred in my modded save. I apologize if this is incorrect.
Additional Information
TagsNo tags attached.
Relationships
related to 0008225new  If I go near this spot the game crashes 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2018-03-14 16:40squamoussNew Issue
2018-03-14 16:43squamoussNote Added: 0037930
2018-03-14 16:46squamoussNote Added: 0037931
2018-03-14 22:51squamoussNote Added: 0037934
2018-03-15 10:59LociRelationship addedrelated to 0008225
2018-03-28 16:07Toady OneNote Added: 0038053
2018-03-28 16:07Toady OneAssigned To => Toady One
2018-03-28 16:07Toady OneStatusnew => needs feedback
2018-03-28 19:25squamoussNote Added: 0038062
2018-03-28 19:25squamoussStatusneeds feedback => assigned

Notes
(0037930)
squamouss   
2018-03-14 16:43   
So I just did some testing. I was correct about it being a night creature. I have also learned that if you approach the creature on the ground without using the fast travel feature, you will encounter it normally and no crash will occur, but I only did this once so maybe I just got lucky. Upon killing the night creature, I could enter and exit fast travel in the area it lurked in, and no crash would occur.
(0037931)
squamouss   
2018-03-14 16:46   
On further testing I now know I was indeed just lucky the first time when I encountered the original night creature without fast travel. Upon encountering a second night creature without entering the fast travel mode, I crashed after a minute of following it. This also means there might be some other issue causing the bug to happen.
(0037934)
squamouss   
2018-03-14 22:51   
Upon even further testing it may have something to do with the [CITY] site type rather than night creatures. I don't know for sure.
(0038053)
Toady One   
2018-03-28 16:07   
What OS is this? In the Windows 64 bit 0.44.07, I don't experience a crash. The * is a skinny moon brute wrestler, and I can encounter it from travel without problems.
(0038062)
squamouss   
2018-03-28 19:25   
This is definitely weird, because upon testing this myself and doing some experiments with other genned worlds I've also not run into that crash but again. But one thing that did happen was windows 10, the OS I run, received a major update a few days ago. My game was crashing all over the place with this particular set of mods, but now I seem to be able to play it just fine. My only hypothesis is that there was something with the previous version of Win10 that did not play nicely with dwarf fortress, but the new update rectified that, either unintentionally or not. Which is really odd. I have not changed anything about this particular mod setup since submitting the report, so I know its not that. Either way the problem seems to have solved itself, I think? If that's the case and I'm not missing anything, I'm sorry for wasting your time.