So the "Data" folder "empty" state will no longer actually be empty.īefore you beat your head against this problem, if you are running on Win10 suggest you read the 'About your choice of "mod manager"' section recently added to the wiki " FNV General Mod Use Advice" article. The technique laid out in the quoted TTW post (aborting the game so it doesn't "quit" normally) will in effect be "leaving" the non game-save specific files (including the "Archives" tab) in the supposedly empty state "Data" folder, which presumably will include the "Fallout - AI!.bsa", instead of removing them when the game closes normally. But MO keeps it in the "Archives" tab and not in the "Data" folder. The "Fallout - AI!.bsa" used by MO should be recognizable by FOMM. Since FOMM does not understand MO, it knows nothing about the VFS, and all it sees is an empty "Data" folder. This means the "Data" folder is always "empty" except when the game is launched, and is empty again when the game closes normally. The primary problem is that MO uses a "virtual file system" (VFS) to populate the game "Data" folder. I would try to get "ArchiveInvalidation" working in MO first, and then install my FOMM mods. When you go back to MO, all of the archives/BSA should be rechecked, and when you go back into the game, the textures should all be showing up correctly. Then launch the game, and either wait for it to crash, or wait until you get to the main menu and then find a way to close it (I normally use Task Manager for it). The simplest solution I've found is to go to the Archives tab (near where the plugins part is), and uncheck everything listed in there. MO is pretty odd with archive invalidation for at least New Vegas. Not an expert on either MO or FOMM, but a little digging found this on the TTW site:
0 kommentar(er)
