Game Skyrim Forum

Bug #1: Saving Crash
Non-Persistant creatures\NPC's placed by mods will cause the game to crash upon trying to save after visiting and leaving the area where they are in.

Affects: esp's only, esm's and interior cells are unaffected.

Steps to reproduce the bug:
1) Create a new plugin, place a Brahmin (CrBrahmin) at GirderShadeExterior and save the plugin.
2) Activate the plugin, start Fallout 3, load a gamesave and COC to GirderShadeExterior.
3) Fast travel to some place far enough away say Megaton or just COC to megaton01.
4) Try save your game and enjoy the crash!


Bug #2: Vanishing\Resetting Objects
Non-Persistant objects (statics ect) placed by mods will vanish upon loading them the second time. If you changed an already existing object in Fallout3.esm then it will reset to the default position (state, as it was in Fallout3.esm) upon a second loading.

Affects: esp's only (seems to include everything even navmeshes), esm's and interior cells are unaffected.

Steps to reproduce the bug:
1) Create a new plugin, place a static of your choice outside Vault 101 (Vault101Exterior) and save the plugin.
2) Activate the plugin, start Fallout 3 and load any gamesave.
3) Fast travel to Vault 101 (you'll see the object that you placed) then fast travel to Megaton.
4) Fast travel back to Vault 101 and you'll see the object is now gone.


Bug #3: Skin color on new NPC's defaults to "white" no matter what

Affects: esp's only, esm's are unaffected.

Steps to reproduce the bug:
1) Create a new plugin and create a new African American NPC.
2) Place that NPC into the game then save your plugin.
3) Load up a gamesave and pay a visit to your albino African American NPC.



If you're using mods you really SHOULD you roll back to v1.4 (or even better v1.0+fake patch) right away, Bethesda has messed v1.5 up real good... :flame:

No, and no.

Patch 1.5 adds 1 function. Which is to swap water types.

There are two ways around this, one is fairly quick and can be done within an hour, which is commenting out that line of script. You'll get 100% playable BS, but still old water.

Once that's done, it is possible to manually swap the water properties, and that the user simply activates the mod with the correct water after starting out BS.


More wizardry methods involving disabled water and x markers may appear later, but these are the ones doable quickly.

Quick question... How does one make water not radioactive when swiming in it? I know the means in which drinking can no longer be radioactive, but how is immersion in water being rendered non-radioactive handled?

There are global variables that handle that sort of thing

The wierd part is, I'm using patch 1.5, but not getting any problems. I'm running 180 mods, many of you probably run the same and are having glitches with them, but I'm not. Strange. Maybe its because I'm in Australia? Is there an Australian version of the patch?

I reiterate my solution proposal: a batch ESMifier program with reversible functionality that works by reading the file extension (for editing and the event that the bug gets fixed). ESPs become quasi-ESMs (as the ESM state is controlled by a flag in the header, not the filename extension) and theoretically spared these bugs. The main caveat is that load order will have to be watched more closely as there will effectively be no more "ESMs load first" prioritizing of the load order.

I just found out you cannot load multiple esm's for geck modding :brokencomputer:

http://thenexusforums.com/index.php?showtopic=121033

I have tested this, it seems odd given that we have several dlc esm's!

You can... just have to open GECKCustom.ini (located in \My Documents\My Games\Fallout3\) and set bAllowMultipleMasterLoads to 1.

You can... just have to open GECKCustom.ini (located in \My Documents\My Games\Fallout3\) and set bAllowMultipleMasterLoads to 1.

i think this is ufefull http://www.fallout3nexus.com/downloads/file.php?id=6142

So, before I go around executing my master plan to fix my game I need a little help.

1) I want to use Broken Steel when it comes out.
2) My game crashes due to the non-persistent issue when I save.

Since I want to use broken steel, I can't revert below the latest mod breaker patch (Correct? Please correct me if I'm wrong.) so INSTEAD what I'm going to do is remove all of the mods I have that place NPCs and creatures.

This should solve the save game crash right? I'm willing to do it, if there's no better way. I just wanted to make sure this isn't a stupid idea, lol.

Just a general information for anyone intending to try and use Broken Steel with a pre-1.5 version of the engine.

In addition to the new script command. There are also some EXPL subrecords which contain a new INAM subrecord that I've never seen before (neither in Fallout3.esm, nor the other 2 DLCs, nor any other mods) and which I was unable to create using GECK 1.1 when I created the record definitions for FO3Edit. I have to assume that this subrecord is new in v1.5 and requires changes made in the 1.5 game engine to work correctly.

Just a general information for anyone intending to try and use Broken Steel with a pre-1.5 version of the engine.

In addition to the new script command. There are also some EXPL subrecords which contain a new INAM subrecord that I've never seen before (neither in Fallout3.esm, nor the other 2 DLCs, nor any other mods) and which I was unable to create using GECK 1.1 when I created the record definitions for FO3Edit. I have to assume that this subrecord is new in v1.5 and requires changes made in the 1.5 game engine to work correctly.