Fallout 1 (patched, modded) crash in RadScorpion cave

Kreshna Aryaguna Nurzaman

First time out of the vault
I installed Fallout 1 with the following patches and mods:
(1) v.1.2.1 patch (semi-official).
(2) v.1.3.5 patch by TeamX (unofficial).
(3) high resolution patch Ver 2.2b.
(4) NPC Mod by TeamX v3.5 (enabling NPC to raise level).
(5) Fallout restoration project mod (enabling quests and NPCs that are omitted before the game's official release).

So I created my character, killed all the rats in the cave, and proceeded to Shady Sands. I then accepted the RadScorpion quest.

But whenever I go to the RadScorpion cave, the game crashes with the following Application Error:
The exception Breakpoint
A breakpoint has been reached.
(0x80000003) occurred in the application at location 0x7c90120e

Click on OK to terminate the program
Click on CANCEL to debut the program


What happened? Which patch and/or mod is the most likely culprit? I think the high resolution patch is not the cause, because I uninstalled the hi-res patch, and the error remains (the hi-res patch is easy to install/uninstall with a click on the .exe, without having to reinstall the game from scratch). Anyone has ever experienced this before?

My system is the following:
MSi Wind U100 netbook
Intel Atom N270 1.6 GHz
2GB of RAM
Windows XP Home Edition Service Pack 3

Thanks,
 
Fallout 1 restoration project mod?

This is how I install F1

1) Install Fallout
2) Find and install "Fallout_1_TeamX_Patch_ENG_1.2w"
3) Install "f1child_patch"
4) Install "fallup13" - this is the TeamX patch 1.3.4
5) Install "f1npcmod" from TeamX
6) Install "sfall1"
7) Install "Fallout1_High_Resolution_Patch_v1.3"
8) Open f1_res and set AUTO_SCRN_SIZE = 0, then your desired resolution




Install the files in the right order.
 
Did you installed the restoration mod in the right order? There should be two available content parts (caravan stuff and city invasion) and if I remember correct, you have to install them in the right order.

But even then, it's strange that your game is crashing with some "exception breakpoint", imo.
 
(5) Fallout restoration project mod (enabling quests and NPCs that are omitted before the game's official release).
I believe, Kreshna Aryaguna Nurzaman is talking about Fallout Update Mod, not about Fallout Restoration Mod. If it is true, it is not compatible with any patches and may cause random crashes.
 
Wasteland Ghost said:
(5) Fallout restoration project mod (enabling quests and NPCs that are omitted before the game's official release).
I believe, Kreshna Aryaguna Nurzaman is talking about Fallout Update Mod, not about Fallout Restoration Mod. If it is true, it is not compatible with any patches and may cause random crashes.
You are right. Pardon the typo. It is Fallout update mod, not restoration mod.

But it seems the particular patch is not the problem here.

I don't know, but it seems the problem is the TeamX v.1.2.1 semi-official patch (the first patch I installed with Fallout).

See, I re-installed the whole game. And then I run it unpatched. Naturally, my saved games cannot be restored. Then I installed the v.1.2.1 semi-official patch, and only that patch. I did not install v.1.3.5 patch, hi-resolution patch, etc.

After installing the v.1.2.1 semi-official patch, I can load my saved games. I then accepted the RadSocrpion quest, went to the RadScorpion cave, and the game crashed. Just exactly the same way it crashed when I still had every patch installed.
 
it seems the problem is the TeamX v.1.2.1 semi-official patch
After installing the v.1.2.1 semi-official patch, I can load my saved games. I then accepted the RadSocrpion quest, went to the RadScorpion cave, and the game crashed.
No, good sier, thee shalt never get a good result trying to load a saved game made with a different combination of mods or patches. Especially with an improper combination. Abandon those saves and start a NEW game with clean install of 1.2.1. If Radscorpion quest will crash in this case as well then yes, 1.2.1 is a culprit, and I would like to hear the details on your problem. Otherwise (what is a much more probable result) blame yourself for the lack of attention to installation manuals and read the FAQ after all.
 
Sorry for the late reply. I've been occupied lately, but I managed to test the patches and mods step-by-step.

(1) First, I install v.1.2.1 patch (TeamX semi-official), create my character, go to Shady Sand, and then proceed to the RadScorpion cave. No problem.

(2) I then install the v.1.3.5 patch over the v.1.2.1 patch, create my character, go to Shady Sand, and proceed to the RadScorpion cave. Still no problem.

(3) I install the high resolution patch over the two patches above. I create my character, go to Shady Sand, and proceed to the RadScorpion cave. No problem either.

(4) Now the mods. I install the NPC Mod v3.5 (the one enables companion to raise level) over all the patches above. I then create my character, go to Shady Sand, and proceed to the RadScorpion cave. No problem either.

(5) Finally. I install the Fallout restoration project mod. Just like above, I create my character, go to Shady Sand, and proceed to the RadScorpion cave. No problem.


Thus, the only explanation for my problem described in the OP is that my savegame file is somehow corrupted, for a reason unknown.


But just to be safe, I think I'll re-install the entire stuff as PainlessDocM suggested:
PainlessDocM said:
This is how I install F1

1) Install Fallout
2) Find and install "Fallout_1_TeamX_Patch_ENG_1.2w"
3) Install "f1child_patch"
4) Install "fallup13" - this is the TeamX patch 1.3.4
5) Install "f1npcmod" from TeamX
6) Install "sfall1"
7) Install "Fallout1_High_Resolution_Patch_v1.3"
8) Open f1_res and set AUTO_SCRN_SIZE = 0, then your desired resolution
 
savegame file is somehow corrupted
That simple. Since you had Fallout Update in your first installation, your saved game still had some problematic components inside of it. So when you have reinstalled the game properly this save still have been causing Fallout to crash. Namely those components are location maps. And Fallout Update itself has a bad habit to ruin the saves sometimes.
 
Back
Top