Cannot get AI to work properly in MO

[RoyBatty]

A bit of background first, I've read all the threads here about AI and MO for both Oblivion and Fallout 3/NV and tried all the methods.

 

I deleted my ini's, and recreated them through steam. All my tweaks are done through MO.

 

I took my old install which I don't want to reinstall because reasons, and made it it's own mod in MO with it's own profile. This install works perfectly fine outside of MO.

 

I do have 2 other basic profiles setup for modding and testing with vanilla that don't have any issues as far as I can tell.

 

That said.

 

Some textures don't work and some do which is very very strange, with either MO's AI, or using Quarn's or FOMM's AI method. I also tried the ArchiveInvalidated.txt generator which worked the best of the bunch, but I had purple textures sometimes (bodies, hands, loading screens, random). When it partially works it's very odd that rock textures and landscape will work, but the rock skirt texture will not even though they are in the same directory and BSA. I'm starting to think this is just a bug in MO.

It didn't matter if BSA management was on or off (I left it off after trying both), and all BSA's were checked. In the instance of MO's AI, it was at the top of the list.

 

I've also tried back dating all the bsa's with Better File Attributes and forward dating all the loose files/folders.

I've never had a problem with Skyrim, so I'm at a loss as to what to do.

[GrantSP]

Hey Roy thanks for the detailed report. Could you provide a bit more information though?

It would be good to know exactly which textures are missing, maybe some screenshots with the console open to show which plugin is calling that texture?

[RoyBatty]

They are vanilla textures. The entire set of textures for metros, where as landscape textures are being overridden fine and for instance the Rock textures, but not the skirt on the rocks. Custom stuff is also loading fine (I don't see why it wouldn't be).

 

It doesn't make much sense, I can get it to work by replacing the original textures in the BSA's with the new ones, but I don't feel like wasting multiple plugin slots to account for the extra bsa's. Perhaps the hook on Update.bsa in the exe is doing something wrong. I don't know, all I know is that AI doesn't work properly under any circumstances for me, even with a fresh install and newly added mods.

 

I think it must be because the installation or mods where not installed with MO. Is there a way to force MO to think they were? I'll have to dig around in the files I guess.

Edited July 10, 2016 by RoyBatty

[GrantSP]

Very odd. Can't recall anyone reporting issues with only some vanilla textures. Logic would dictate that if other assets from Update.bsa are being loaded then these few would also.

Not really sure the installation of mods outside of the MO environment would have any affect with this issue since you report these are vanilla assets, and therefore they can only be found in the one location: Data.

 

Sadly I don't know how to direct you on this, you can try and install ALL mods via MO if you wish, though I doubt that is the problem. We have a lot of Fallout guides created here for Fallout New Vegas, Fallout 3 and even Tales of Two Wastelands and even with heavily modded setups like those, no one has reported what you are seeing, at least I can't recall anyone. I doubt very much it is something as dire as the code not reading that BSA correctly as surely it would manifest itself many times for many users?

 

I'm assuming you have checked simple things like ensuring all the BSAs are in fact checked on the 'Archives' tab? This was the only issue I can recall that was remotely similar to yours, a user had not made sure ALL BSAs were checked and the one providing the asset was indeed unchecked.

[RoyBatty]

I can't check or uncheck any of the archives, they are greyed out. As I said, I took my entire old installation and just copied it into a folder in "mods" vanilla assets and all. Perhaps this is the issue and I need to remove the vanilla NV BSA's and esm's from it. Either way all BSA's are greyed out and I can't do anything with them.

 

I did this because I want to retain my old install for my live streams and testing, It took me 2 years or so to get it where it is and I don't remember half what I've done to it and have no desire to do it all over again. :D

 

I wanted to use MO, so I could have a vanilla setup for testing mods I'm working on and for creating vanilla LOD etc, and an alternate setup for testing mods for other people.

 

I apologize, I'm just incredibly good at breaking any kind of software by doing unconventional things, hehe.

 

EDIT

 

Quick question, does MO 2 work for the older games? I heard he removed the BSA stuff from it entirely.

Edited July 24, 2016 by RoyBatty

[EssArrBee]

If you have BSA management off or if the corresponding ESP is named identically to the BSA then it will be greyed out. 

 

MO 2 removes the BSA management feature.

[RoyBatty]

None of the BSA's have been renamed, and I've renamed mod ones (mostly mods I've made or worked on) properly like "esmname - main.bsa", they don't load correctly if they have an identical name even not using MO.

 

It didn't matter if BSA management is turned on or off, same.

 

I'll try 2.0, the bsa management is just broken I think. Can I easily migrate things to it?

[GrantSP]

<snip>

Can I easily migrate things to it?

Should just be a case of copying into MO2's folders the contents of your existing folders. ie. 'mods' into 'mods', 'profiles' into 'profiles' etc. The actual profile system should be identical in that both versions read the plugins and mods enabled from those *.txt files in each profile.