Oh it definitely crashes reliably in that context. As it stands, my current save gives me about 2-5 minutes of game play before the crash occurs, and that is entirely dependent on how fast I am personally going about doing things. As it stands, the save file I possess is essentially paralyzed by the persistent occurrence of this error. Whatever is causing it is happening very shortly after the load.
I will see if I can narrow down the timing and environmental factors for you. In the meantime, I’m still not entirely sure how you’d like me to get you the save file. Does the crew here maintain a dropbox account I can link to a dropbox folder with the save file, or do you perhaps have a game specific business e-mail I can I send the file to?
So I just played the game a few times to get a feel for the possibilities of the error.
I played once as I normally do, slipping into the lab and looting until the error appeared. I was underground by 1 Z level. It took me roughly 30 minutes in game time for the error to occur. This is pretty much the standard for my crashes.
My second play through involved me attacking the zombie horde south of the lab and then returning to the entrance of the facility. I had a hunch that maybe the game was wigging out on account of one of the zombie types loading improperly. I managed to kill the horde without any sort of incident, but when I returned to the entrance of the surface structure of the lab my game crashed due to the same error as previously. The error occurred much later than I’ve experienced while exploring the lab… over an hour of time in game passed between loading the save, killing the horde, and returning to the outside area of the lab.
On my third play through, I abandoned exploring the laboratory entirely and went back to my outpost/personal base. The error did not occur in this instance. I simply played the day all the way through into the next morning and quit the game without incident.
I did a forth play through to test an idea I had. On the first underground floor of the lab there is a mi-go in captivity. My guess was that maybe one of its sound prompts was causing the issue. I went to where it was held, basically the “east wing” of the lab, and waited around for several in game hours. There was no crash until after I left the room and went into the “west wing” of the lab, where in it occurred during a movement action.
Finally I did a fifth play through, again going into the lab and straight into the mi-go’s room. This time I scavenged through all of the area I consider to be the east wing of the lab. Again, the game did not crash despite the time I spent walking circles and scouring the place, and again, the game crashed due to this error once I was moving around the west wing of the lab.
So… whatever is happening is happening because of the lab, but even then there is a geographic inconsistency. My guess at this rate is that there is something occurring either behind one of the locked doors in the “west wing” or one z level down beneath the west wing. Every time the crash has happened it has happened during movement, so it’s not something that requires my interaction or even line of sight to whatever is causing the error.
I hope this information helps, and I await your response to my proposal for the save transfer.