lil_ramen said:
Bah, you know what. Nevermind, just close this thread. It's just wasting my time, haha, I'll just *try* to e-mail the developers. Thanks anyway.
I would add something, but it would be like kicking a small child.
Oh, what the hell.
I even tried turning off my video card (as said in the Troubleshooting Sticky), for some reason, when my PC rebooted, it was acting like crap.
No, I recall it says to disable the acceleration, not turn it off. Disabling the DirectX acceleration is different than disabling the card. If you disabled the card, then that could explain why your computer was "acting like crap".
Good explanation again, genious. Just as fucking useless as "Application Error". Why don't you just go for Total Moron and just say "It r broke!" and donate your computer to someone who could obviously use it for more constructive purposes, like in a school. You remember school, right? No? Oh, well, no big loss. Don't forget to salt the fries.
Been there, done that. 'everything they said', meaning all those threads I've read about application errors, none of those threads gave me a good solution.
And we're supposed to be psychic and magically know which of the threads you've read. Including the ones that mention Ctrl+R to manually load a map.
The third thing I tried was to replace the .SAV with a .map. VAULT13ENT.map is what I'm looking for, because that's the file that is corrupt I think, because when I try to enter the 'Vault 13 Entrance', I get the Application Error. But for some reason, there is no VAULT13ENT.map. If you have FO2 still installed into your PC, can you check if you have the VAULT13ENT.map in your \data\maps\ folder? I already tried reinstalling (without deleting the saves), still no luck, and there's still no VAULT13ENT.map in the \data\maps\ folder.
Specific map saves are NOT in your \data\maps\ folder, they are in your \DATA\SAVEGAME\SLOT* folders. The \data\maps is merely a base map cache the difference map data in the save folder is compared against, should only have map files in it if you are currently running the game or the engine closed wrong or something else belched and should be purged of all files if you are having map-related problems. It starts out and is regularly cleared, it seems. Try looking for the V13ENT.SAV file in the save file's maps folder instead, and replace that with a brand new version of the map.
Or, here is a method I have tried and successfully used to get the engine to extract a fresh copy of a map, and to better document the map replacement process.
Figure out which map you need to use.
Make a backup of the map from your \DATA\SAVEGAME\SLOT folder.
Make sure \data\maps\ is completely empty.
Start Fallout 2.
On the title screen, hit Ctrl+R, then pick the map in question.
Save in a fresh slot. (The data saved in that fresh slot is not important, as long as it unpacks a master map copy for that area into the \data\maps\ folder, which the engine does when it saves a fresh Ctrl+R copy. In the normal operation of the engine and through subsequent saves, maps cached in the \data\maps\ folder for later games are NOT master map copies, but instead temp map files based upon the saved map data, to be used as a reference against your current changes in gameplay. Ctrl+R fixes this by just loading up a fresh copy of the map without anything else done to it.)
After it loads, hit Esc to pause the game and Alt+Tab.
In the \data\maps folder, there will be a freshly unpacked copy of the map file in question, as long as the engine is running. The engine does this for speed purposes, so it doesn't have to unpack the master.dat for a map each load time.
Copy that file, no renaming required (it should be with a .SAV extension anyways), into your \DATA\SAVEGAME\SLOT folder.
(For stability reasons, I suggest you exit the Fallout engine at this point, but I have tested it to work without reloading.)
Then reload the save file in question, and it should use the fresh map.
I have checked this with a few maps, I can't say for certain for all maps. There may be a bit of scripting that may conflict with event sequences and requirements, so there is no telling until you try it.
