Helpful notes on using Mod Organizer with TTW

Post by **manos** » Wed May 14, 2014 3:07 pm

It seems that our problem is related to not hiding some files with MO.

I've read on Nexus that some people had the same problem with Skyrim.

I know that EssArrBee (a member of the STEP team for Skyrim) had this problem too and he didn't found from where it comes yet.

To me it could comes from not hiding the right files with mods like JIP-CC&C, etc, or the way MO handle the BSA.

Maybe some scripts have to be extracted or the entire BSA to make it work properly. I'm saying that because every time I've read that some people had this problem, they where trying to instal some big mods like EVE.

Post by **Metal_Izanagi** » Sun May 18, 2014 5:16 am

Just wanted to add that I've run into the same issue, with JIP Companions Command and Control, and Flashlight NVSE. Something about those two in particular, even when using FOMM to install them, instead of MO,(Since it can't handle HUD mods.) is causing the game to crash on startup. I just spent around four hours messing with this stuff, and all I've come up with is that something between Mod Organizer, Tale of Two Wastelands, and both JIP Companions Command and Control and Flashlight NVSE doesn't allow them to work together. Deactivating one of the two doesn't help, but both allows the game to launch normally.

Post by **drumber** » Sun Jun 15, 2014 4:33 pm

Did anyone ever figure out what was causing this? Been searching for why my game wasn't starting and then found this and removing Flashlight and JIP Companions Command and Control fixed it. Bit weird.

Post by **enneract** » Sun Jun 15, 2014 9:25 pm

I've had good luck using MO with FONV, with the following caveats and idiosyncracies;

I extract everything, I have no BSAs except for the vanilla Obsidian ones. I don't know if this is *best* practice, but it works for me.

Archive Invalidation does not work correctly initially. I first saw the problem with character skin textures, even when other textures were definitely working correctly. The solution (and this is bizaare) is to uncheck all the BSA's on the 'Archives Tab', run the game (watch it crash or not crash), exit, and run it again (they'll all automatically check themselves again). Textures should be properly invalidated at this point, and you shouldn't need to repeat this procedure.

HUD mods must be installed exclusively with FOMM-fork, run through MO. You must move their files from the 'overwrite' folder, to a new 'mod' after each installation. Do this early and don't touch it again.

EssArBee on the STEP forums\wiki has a guide which is a great resource for building a TTW install with MO. 'Fear and Loathing in New Vegas', I believe. Use your brain, though, not all of the specific mods he recommends are compatible with TTW, but he shows the proper procedures for installing some of the trickier mods (HUD, etc) with FOMM\MO combo.

Post by **drumber** » Mon Jun 16, 2014 11:23 pm

^^ This fixed all my issues. Extract all BSA's and follow EssArBee's guide and Mod Organizer works perfectly.

Post by **manos** » Tue Jun 17, 2014 2:26 am

Fear and Loathing in New Vegas by "EssArrBee"

http://wiki.step-project.com/User:EssArrBee/FalloutNewVegas

Et voilà ;)

Post by **enneract** » Tue Jun 17, 2014 2:34 am

Nah, too snarky

Post by **manos** » Tue Jun 17, 2014 2:37 am

Huh ??

Post by **enneract** » Tue Jun 17, 2014 3:02 am

Ignore the last comment by me.

Post by **FamousDeadGuy** » Wed Aug 13, 2014 7:12 pm

Not sure if this helps, I was working on the UI portion last night during my initial PITA of using Mod Organizer, and I figured out how to make PN, PN Extra Options, and MCM play nice with DarnUI. I was pretty proud of myself. It involved hiding files in MO's interface I want to say the .../menus/hud_main_menu or some other..