Need help with random CTD (log and mod list attached)

[c0c0c0]

  On 9/3/2013 at 4:48 PM, hentaishinri said:

 

Exactly what I plan to do right now. I removed and changed so many things that the game can't POSSIBLY be saved now... I will start a new game.

But the mod order problem still exists and before I start fresh I wanna fix it.

If you are using BOSS, why do you think your order is off? The False-Flag notice? here's the readme on False-Flag:

 

  Reveal hidden contents

 

False-Flagged Plugins

Whether a mod plugin is a master file or a non-master file is dependent not on its file extension (.esp, .esm), but is instead decided by the value of a setting inside the plugin file, known as its master bit flag. Master files have this set to 1, and non-master files have it set to 0. However, because ESM is an acronym forElder Scrolls Master, and ESP is an acronym for Elder Scrolls Plugin (even for Fallout 3 and Fallout: New Vegas), most people assume that master plugins are files with .esm extensions, while non-master plugins are files with .esp extensions.

This assumption is valid for the most part, as the vast majority of masters are .esm files, and the vast majority of plugins are .esp files. However, sometimes this is not the case. When a plugin has a .esm extension but has a master bit flag value of 0, or has an extension of .esp and a master bit flag value of 1, the plugin is said to be false-flagged, as its extension does not match its master bit flag value. False-flagged plugins are most common in Fallout 3 due to the use of FO3Edit's Master Update feature, which turns non-master plugins into false-flagged plugins, to avoid bugs that only manifest for non-master plugins.

The distinction between masters and non-masters is important for load order because the game will always load all masters before all non-masters, regardless of whether they are listed or dated (depending on your game) as such by the mechanism used to determine load order. Earlier versions of BOSS, and most if not all mod managers, put all .esm files before all .esp files, but failed to take into account the value of the master bit flag of plugins. As such, the load order they displayed was incorrect, as it failed to take into account the game always loading masters before plugins.

Since the master bit flag can be changed by users, it is not sufficient to update the masterlists to take into account the values of plugin master bit flags in the plugins available for download, as the user may have changed the master bit flag values (eg. using FO3Edit's Master Update). As such, BOSS instead checks that the masterlist used is ordering masters before non-masters, and moves any masters loading after non-masters so that they load before non-masters. If any masters are moved, it then displays a message in the BOSS Log to notify the user of this change. The BOSS Log does not detail which masters were moved.

 

So that may be telling you that you have an ESP loading above an ESM because of master bit flag, probably inserted by the author. If the author felt it needed to load as a master, presumably he did it for a reason. This is just saying the master bit isn't "normal" for that file type. Doesn't mean it's wrong.

[hentaishinri]

  On 9/3/2013 at 6:27 PM, c0c0c0 said:

 

  On 9/3/2013 at 4:48 PM, hentaishinri said:

 

Exactly what I plan to do right now. I removed and changed so many things that the game can't POSSIBLY be saved now... I will start a new game.

But the mod order problem still exists and before I start fresh I wanna fix it.

If you are using BOSS, why do you think your order is off? The False-Flag notice? here's the readme on False-Flag:

 

  Reveal hidden contents

 

False-Flagged Plugins

Whether a mod plugin is a master file or a non-master file is dependent not on its file extension (.esp, .esm), but is instead decided by the value of a setting inside the plugin file, known as its master bit flag. Master files have this set to 1, and non-master files have it set to 0. However, because ESM is an acronym forElder Scrolls Master, and ESP is an acronym for Elder Scrolls Plugin (even for Fallout 3 and Fallout: New Vegas), most people assume that master plugins are files with .esm extensions, while non-master plugins are files with .esp extensions.

This assumption is valid for the most part, as the vast majority of masters are .esm files, and the vast majority of plugins are .esp files. However, sometimes this is not the case. When a plugin has a .esm extension but has a master bit flag value of 0, or has an extension of .esp and a master bit flag value of 1, the plugin is said to be false-flagged, as its extension does not match its master bit flag value. False-flagged plugins are most common in Fallout 3 due to the use of FO3Edit's Master Update feature, which turns non-master plugins into false-flagged plugins, to avoid bugs that only manifest for non-master plugins.

The distinction between masters and non-masters is important for load order because the game will always load all masters before all non-masters, regardless of whether they are listed or dated (depending on your game) as such by the mechanism used to determine load order. Earlier versions of BOSS, and most if not all mod managers, put all .esm files before all .esp files, but failed to take into account the value of the master bit flag of plugins. As such, the load order they displayed was incorrect, as it failed to take into account the game always loading masters before plugins.

Since the master bit flag can be changed by users, it is not sufficient to update the masterlists to take into account the values of plugin master bit flags in the plugins available for download, as the user may have changed the master bit flag values (eg. using FO3Edit's Master Update). As such, BOSS instead checks that the masterlist used is ordering masters before non-masters, and moves any masters loading after non-masters so that they load before non-masters. If any masters are moved, it then displays a message in the BOSS Log to notify the user of this change. The BOSS Log does not detail which masters were moved.

 

So that may be telling you that you have an ESP loading above an ESM because of master bit flag, probably inserted by the author. If the author felt it needed to load as a master, presumably he did it for a reason. This is just saying the master bit isn't "normal" for that file type. Doesn't mean it's wrong.

 

I see. Well I will start a new game, this time I presume it will be more clean since I removed everything that everyone said I should remove (ERSO and some outdated mods). Hopefully this time I will not crash... and if I do... -sigh- it's back to the papers xD