Nasty crash bug related to special encounters (semi-spoiler)

Dukester

First time out of the vault
If you visit all of the special encounters, the next time it tries to load a special encounter the game crashes to the desktop. *Always*

You probably know how you can get multiple special encounters from a "special encounter square". Well, if you are lucky enough to get them all, then your luck has just ran out. The next time you go into a special encounter square, the game tries to load another special encounter, except they are all used up, and it blows up.

I'm currently playing the Awaken mod and this just happened to me. It also previously happened to me in a regular FOT game. All I know is to revert to a save which still has one special encounter remaining and avoid that last encounter.

I tried poring over the campaign files to see if I could find anything but it seems ok to me. This bug is really annoying. Anybody else ever notice it or have any idea if its correctable somehow?
 
I completed all the encounters and I have bugs. Buggers!
1 bug is like yours, I guess. When I came across a possible site of SEs, a green cirle appeared and then the game hang up.
another bug is different. when I go into Gas station, Trader, Hermit, Bazaar day, Merchant it's possible I won't be able to exit to world map. And after bunker epsilon, when i got the jet bike key, I killed Phil the Nuka dude (i left him alone till now)--> I still couldn't drive his bike (his bike go with his body)??? :cry:

BOy boy boy! I really hate bugs like that. :evil:
 
I completed all the encounters (hard mode, patch 127) and I have bugs. Buggers!
1 bug is like yours, I guess. When I came across a possible site of SEs, a green cirle appeared and then the game hang up.
another bug is different. when I go into Gas station, Trader, Hermit, Bazaar day, Merchant it's possible I won't be able to exit to world map. And after bunker epsilon, when i got the jet bike key, I killed Phil the Nuka dude (i left him alone till now)--> I still couldn't drive his bike (his bike go with his body)??? :cry:

BOy boy boy! I really hate bugs like that. :evil:
 
Additional Info

I neglected to post my system info earlier, so here it is:

FOT v 1.27 running under Win2K v 5.00.2195 Service Pack 4
ASUS A7N8X w/ Athlon XP 2400+ and GeForceFX-5900
1Gb PC2700 RAM / 120Gb WD1200JB / NTFS File System

I do most of my online stuff while booted into Linux, so my Win2K setup is pretty lean and mean and its more or less dedicated to gaming. FOT does run very nicely at 1024x768@32bpp w/ Antialiasing on.

I first noticed this weird bug last year when I was goofing around playing the original missions and trying to follow Guiler's FAQ and Walkthrough to scope out all the special encounters.

Its almost like the game engine overflows when it seeks the next special encounter. This only seems to happen if you have gotten all of the special encounters already.

Currenly in the Awaken mod, I have a save game that can reproduce this crash 100%. Most of the time it simply core dumps and drops back to the desktop, but sometimes it pops back to the main menu with an error message. I just made the bug occur and this time it crashed to the main FOT menu with the following error dialog box:

Code:
           Failed to open mission file:
tlsMutisMuti LOSRc/onanForGae_okF1S.i

Typically the mission file it tries to load is different each time this bug happens. Looks like some kind of buffer overflow most likely or an improperly incremented pointer.

This bug is definately not specific to the Awaken mod, as it annoyed the $#!4 out of me last year when it happened. This time I knew about your forum and decided to document it.

BTW The Awaken mod is tremendous fun. I'm going to make a post concerning it in another area in a little bit. Ok, well thats about all the info I can come up with concerning this bug.

Recommendation: if you are farming the special encounters, best make a separate save after each one happens because if you run out of them it tends to mess your game up. Nothing worse than cruising around the wasteland killing stuff when unexpectedly you crash back to the desktop. Well at least you don't have to reboot or anything, gotta give them credit for at least handling fatal exceptions in a sane manner. Other than this bug, the game has never, and I mean never crashed on me. Its gotta be one of the most stable games I've ever had the pleasure to play.
 
Back
Top