Possible mod conflict...

[Shastania]

I recently downloaded the "Commonwealth Of Gamers" add-on and installed as per instruction, plonking everything into my Fallout 3/Data file.

I've got Mod Manager installed but whenever I try to start up the game after selecting the appropriate file, the game will start up and the "slideshow" start-up menu will play, but the little green cursor won't appear so I cannot create a new game or load my current one.

 

I had a number of different mods running at the time so, thinking it was a conflict, I turned everything off except for my DLCs.

Again, the same thing happened- the cursor is not showing up and i can't access the start-up menus.

 

It's frustrating as all hell as I was really looking forward to playing that mod. :(

 

Any help would be greatly appreciated. Also, any tips on how i can avoid this annoyance in the future?

I'm not running FOSE as I'm not exactly an expert with scripting-based programs.

 

If anyone needs a mod list of what I had running, I'll gladly provide.

(no home internet so I can't upload it right now...)

[csb]

I had the same issue with that mod. However, that was before a re-install of Fallout3, so if it left some lingering thing, that got rid of it.

 

Such things can happen when (a) a mod grants a mod-specific "Perk" to work behind the scenes to accomplish its intent and then is uninstalled without removing the particular perk. Some mods are good about posting the perk thing in their Uninstall instructions, some aren't; and (b) the mod makes changes to game mechanics that don't get reset when uninstalled. Quite often, these are changes to the Fallout3.ini file.

 

In this case, check the mod's readme file and see if it reveals anything. If not, contact the mod author and ask what changes installing the mod made and what needs to be done to remove them when uninstalling.

 

Good luck in fixing the problem.