Bay 12 Games Forum
Dwarf Fortress => DF Adventure Mode Discussion => Topic started by: George_Chickens on July 01, 2018, 07:07:38 am
-
I've noticed that every single one of the last adventures I've played (probably around 17) has ended with some part of the map corrupting its self and becoming inaccessible, often a small place where my hearthsman has directed me. Eventually, even villages and cities become permanently inaccessible due to instant crashing upon entering.
I wanna know if this is just me, if I'm somehow doing something wrong. Or if it's just a common problem that I've been hit with.
-
Never had that.
-
Never had that.
On average, how long do your adventures last? I'm curious to know if I'm spending too long or too short as an adventurer, in case that has something to do with it.
-
Never had that.
On average, how long do your adventures last? I'm curious to know if I'm spending too long or too short as an adventurer, in case that has something to do with it.
About half a month (in game) before I do something dumb and die.
-
Haven't played any 44.xx.
Some 43.05 adventures can span up to around 2-3 seasons (dunno if that constitutes appreciable game length), so time hasn't yet been the factor for crashes.
Often if they occur, it's towns where an item issue might cause a specific area to become inaccessible in slow travel mode.
I've had whole inaccessible sites cause crashes/stalls as well for both fast & slow travel modes. These seem to be item/population/pathing oriented.
-
On average, how long do your adventures last? I'm curious to know if I'm spending too long or too short as an adventurer, in case that has something to do with it.
Between one season and a year, but since I'm focusing on world exploring and making friends and helping villagers, my adventurers rarely die. I end up finding them positions in a local army and go on with my business
-
Are you talking about now (post-44.10 nemesis error fix) or before that? There's a difference obviously...
I've had older versions succumb to Nemesis, where part of the map becomes inaccessible, but never total loss of an Adventurer save. Play several adventurers in a single world spanning a year or two usually.
(And probably best not to play with TWBT enabled.)
-
Yeah, I continue to get the crashes in 44.11. It's no longer a nemesis load error, it's something else completely.
-
If you upload your saves to the bug tracker someone will be able to tell you if it's save corruption and that'll help close in on the issue.
Best if it's not a save carried over from previous versions probably.
-
I've uploaded two already. After having reloaded my old, pre corruption save, I haven't had a single problem since. I really would like to know what caused this, because it's so weird. I did send my save to a friend to play a succession adventure at one point, but they did not tamper with it and they used version 44.11, so I don't think they could have caused the corruption.
Wait, nope, spoke too soon. Major cities are corrupting themselves yet again. Will upload the save and add it to one of my reports.
-
For whatever reason, my game tends to crash in placed when i go full screen/maximized window, but when i leave the game window at standard size, it only freezes up for a moment
-
The problem seems to be related to adventurer creation or worldgen. I can play the same one for ages, but when I start generating more, problems appear. I wonder what's going on.
-
I hate to double post like this, but I need a hand. How many of you have had retired adventurers in the latest version? I have noticed that it seems like the majority of my problems occur in worlds with retired adventurers, but it may not have any real correlation, as the problem often happens in places they have never visited.
-
I do, and have experienced problems with corruptions, albeit no corruption ending ones
-
Yeah, when I got the spare time I genned a bunch of pocket worlds to test the crash on, and it doesn't seem to have any correlation with retirees. I am assuming it must be glitched entities emigrating during worldgen periods and causing areas to become crash hell.
-
What's the error message you're getting from this? The only time I couldn't enter a city it was because I did a bunch of modding and when I tried to enter the city the game kept allocating memory until I had to kill it. I did a ton of adventuring earlier this year on 44.02-44.06, probably 200-300 hours, and I never saw any city corruption.
-
There is none of note. It's the regular Windows crash message. Does not seem to leave an error message in the log, either.
[EDIT] The problem has been confirmed and fixed by Toady and should be gone in the next release. All is well.
-
What's the error message you're getting from this? The only time I couldn't enter a city it was because I did a bunch of modding and when I tried to enter the city the game kept allocating memory until I had to kill it. I did a ton of adventuring earlier this year on 44.02-44.06, probably 200-300 hours, and I never saw any city corruption.
I've been playing adventure mode for two years. Whether I'm playing Vanilla or Masterwork, ASCII or tiles, friendly squads from my hometown will attack my companions in every world I generate. If there are travelling NPCs then they will either
a) Generate infinite clones of all monsters in the region after dying
b) Crash the game upon leaving travel mode
The only way to yield and cease hostilities is to teleport your companions away. This also prevents with drowning and suffocation.
Maybe the entity id gets corrupted when an adventure mode site (the area loaded when you exit travel mode) overlaps with a town/city/camp/ruin, and the client tries places the NPC in both the town/city/camp/ruin and the overworld site so that it is in two sites at once. Since a single travel mode tile can simultaneously exist outside of a town/city/camp/ruin while overlapping onto it so that a travelling NPC entering or leaving a town/city/camp/ruin has two data entries for a single location. Or something. I have waited two years for this to be fixed, but Adventure Mode is still unplayable and there are no handlers or workarounds to fix corrupted saves.
The icing on the cake is that since Dwarf Fortress consistently crashes every 16 hours due computing smoke, having a key pressed while loading a site, or moving too quickly (Adventure Mode often moves you two tiles when you move once, so there is no way to prevent this) this forces you to save often in order to mitigate crashes. Yet saving often increases the risk of file corruption, which causes crashes.
It is impossible to roleplay in Adventure Mode, as resting in towns or cities will regularly corrupt your NPC files, whereas sleeping outside of towns and cities guarantees a half-hour fight with bogeymen that indefinitely chase you by teleporting next to you and massacring entire towns when you try to flee.
Want to play as a mythical beast? Get ready for loyalty cascades, crashing on site creation, and exiting at player forts. Want to generate a custom map? Get ready for drowning, freezing and cave-ins at spawn, along with corrupt entity IDs and respawn loops. Player Forts corrupt saves in adventure mode.
-
Never experienced the stuff you talked about. Delete everything in your DF folder and start fresh, maybe?
-
That is truly bizarre. I have never, not in my near decade of playing DF, experienced anything like that. Is your CPU damaged or something?
-
EDIT: NEVERMIND! I had to scroll down in Dropbox to download all of the .dat files!
That is truly bizarre. I have never, not in my near decade of playing DF, experienced anything like that. Is your CPU damaged or something?
I have played on four computers, one of which had a fried motherboard, and one of which had its sixth cpu core overheat. I am currently playing on a new computer with nine Dwarf Fortress installations; half of which are on my solid-state drive. RAM, disk space, and CPU usage are never an issue. Most of the fortress mode bugs have been patched, yet modding other races to be civilized will still make them attack companions, any custom tilesets crash camp construction and switching tilesets after world creation corrupts your save. Surprisingly, apart from a corrupt save file and a resolved tree branch bug, I have never had problems in adventure mode when visiting player & NPC forts that are not connected to an underground cavern. I always use Vanilla, and have played v0.28, 0.42, 0.43, and 0.44. I crash on average once every 16 hours.
-
To the two other dudes experiencing the crash problem, it's finally fixed! 44.12 is out.