Well, if we can help in any way, i would. Id also say definitely wait for the master bug chaser to finish chasing bugs before declaring it dead.
Also, it may be that the corrupted file was a recent corruption and older versions from prior saves can be used.
I found it. Like legit I FOUND IT. And I fixed it. Tested it, and it runs great. But my solution was lazy. And there's something of a problem/concern/dead-end of sorts, what have you, which complicates things.
Its not just one file, its TWO. And the two different crash log variants I've been getting seems to suggest this as well.
After awhile I said "fuck it", and I went with the nuclear option, and deleted all of them, in a mad fit of hysterical madness.
And it worked, surprisingly.
My test fort "TestFortress" ran great. Adv-mode, no crashes. New features populated well, and the save file was stable. Who'd have thought? What could go wrong? Nothing! It fixed everything. Everything was fucked, so we got rid of it. Every Feature-.dat file, gone trash. PEACE - See ya. We don't know what went wrong, but things got fixed.
But as Putnam pointed out, and I myself just noted,
we still don't know what went wrong in the first place, and finding the file would be awesome. So in the interest of this, Putnam suggested a binary search nuclear destroy pattern, in order to expedite things. Delete half and see if it fixes shit, then delete a quarter, if shits broke, delete the other quarter, and narrow it down. Smart thinkin! But things went wrong pretty quickly. Clearly, the corruption was in the first half of the 191 files, that was clear after some testing. What was not clear, was why the game was still crashing when either one of the two quarters of that corrupted 1/2 of files were left in the game.
So there's two of these corrupt pieces of missingno. filth. Apparently, that's a thing.
And I played hotshots golf for a little while today, but didn't understand why there wasn't more jumping and somekind of talking mime who yells "FOUL!", and spent time hanging out with those tall things over there, who live in the corner and whisper at me, and made plans to make a golf fortress mod, where you have crossbow-like ranged weapons that fire notched golf balls at alligators and windmill monsters and flag-poles. And the wagon creatures are golf carts. And the only workshop is a computer that allows you to buy shit on ebay.
So I've gone insane. More so than usual. I can fix the save with hellfire. But it won't do much good for determining the source of the bug. And perhaps, I owe it to my fellow df players to find both. Maybe some of the bay12 users here don't want me doing jack to the save, and want to let it rot in a gutter, fine by me, good riddance. Maybe I can get some feedback here before I start shoving parts of the save into a literal data woodchipper, and making unilateral decisions about the fate of the world, and its inhabitants before I reset the world's population of sailfin mollies, ospreys, and gorlaks, and like alligators I think? All of those are extinct btw, well except gorlaks.
I'm going to return to my golfing for the rest of the night, and I'll see what the responses are tomorrow, and go from there.
----
Even if the save runs great now after a scorched earth campaign, as Putnam and Rome noted, this save is "proper fucked." Like, even if I 'fix' it, and the save is able to run without crashing, where it can spawn birds, caribou, and cave fish people down in caverns—species once thought extinct. Sure, the train that is this save may technically be 'running,' but it’s doing so completely off the rails. There are no tracks to guide it anymore. The illusion of forward momentum which is seen in the prior turns is merely caused by the downward sliding trajectory of this train as it travels down the rocky scree of a mountainside, careening into timber laden uncertainty, free falling off of a sheer cliff, or meeting its thunderous head-on collision and end as it smashes into the unyielding side wall of yet another mountain.
The save is already doomed. Corruption is permanently caked within it.
There is no simple fix for the save. It is already dead. But players can choose to still play on it, none the less. The save is doomed to share a similar fate to Museum III, in its current version. Whatever people did to it, whatever subtle tweaks were made, all of which I cautioned strongly against, have evidently caused irreparable harm to the save file's stability. And that is definitely the case. And there is no way to walk this shit back without rewinding turns. All I can do if people want to move forward with this, is give the save an emergency tracheostomy to keep it breathing, and stop the crashes for a little while. But something else will invariably show up later, and slowly the world is just going to become more and more fucked.
Author
Topic: Museum IV; the end times have arrived early (Read 6714 times)