(copied from the nexus forums)

Good Morning

I'm currently using the Oblivion Mod Manager. Worked fine up untill a few days ago. Now even the most minor mod won't work, even mods that worked in the past. Upon activation (new mods) and game start, instant CTD. There appear to be no conflicts in the detector. I've downloaded BOSS today and that got rid of my in game crashes. All else is working as intended. Just that for some reason I can't add new mods to the list.

Any ideas as to what might be causing this ?


edit: If it helps, It's the steam version. Had no probs with is so far...

Specifically, what do you mean by "can't add new mods to the list"? Like, what happens when you try? Can you not find your Data folder, are the mods not showing up in the list in the launcher, or are they showing up and they're activated but they just aren't showing up in-game?

http://sites.google.com/site/khettienna/mod-user-guides/mod-use-troubleshooting

Thanks for your reply


Mods show up, but when I activate them by Mod Manager and the default data files my game crashes on startup. There is no discernible order to this and I've tried it with multiple mods, ones I know should work. All of this just occured a few days ago, didnt change anything specific so I'm completly lost as to what caused it. I've just tried to rename the default ini however the manager wont start up and if I try by default launcher the game crashes all the same.

You could try backing up your Oblivion.ini somewhere and deleting it. Let the game generate a new one. See if that helps. Also, try deleting you plugins.txt file.

Leave "default_ini" the way it is. Don't make adjustments to it.

Don't rely on OBMM to sort your load order. It just puts mods in by date and that has nothing to do with the order they should be loaded in. After installing a mod, run BOSS to sort your load order. Ignore OBMM's conflict detector as well - it really doesn't work. Lastly, depending on the nature of the mods you're loading and how many of them you have, you might have to use Wrye Bash to build a Bash patch. This helps resolve conflicts.

Turns out I simply had too many mods working at the same time that it came to the max of 255 If it hadent been for wrye bash listing the no. I'd have remained completly oblivious to this. Thank you so much for your time and help. wrye looks like an extremly usefull tool once i figure it out.

Greets

Ry