Sunday, March 7, 2010

Crash Ahoy!

Seriously. Fallout 3 has been one of the most unstable, bug ridden games I've ever played. By far.

Testing the improved starting packages for the vanilla companions who start outdoors, hoping to keep them from wanderin' off a-home when left in the vault.

Initial testing looks good. Do some wandering, drop by Recon Craft Theta, and so forth. Decide to pop up towards Old Olney to kill some deathclaws as a way to pass the time while the package continues to not revert.

Fast travel to the abandoned farm.

Keeeeeeee-rash. Not unexpected. That area has given me trouble since day one. The only area that's had more crashes has been the Anchorage memorial, during an incident involving MMM, the Unofficial Patch, and MasterUpdate. Screwed that entire area of the wasteland for me for over a month. Haven't had any more trouble with it since I axed those "fixes", funnily enough...

Anyway.

CTD itself wouldn't warrant a bitch from me here, but FO3 decided to oneup itself.

I got a BSOD. Haven't seen one of those in years. Since like Windows 2000. Pulled a stack dump. Haven't seen one of them in even longer.

Those of you who are big fans of the RR mods should give brief thanks to whatever deity you follow that my PC sucks. 'Cause if I could play something better, my ass would so be uninstalling FO3 and figuring out how to create companions in something not coded and bugfixed by autistic chimpanzees.

Windows seems to be fine after the unexpected reboot. Now I suppose I get to see if FO3 corrupted itself...

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.