Tanebowdash Posted June 4, 2015 Share Posted June 4, 2015 Righto, let me just say I have been findling with this for quite some time. I'll give you all of the details first. I am using Mod Organizer and using FOMM for Archive Invalidation. I am using Breezes New Vegas Males along with BEWARE OF GIRL Type 3 HiRez HiDetailed Replacer. [Archive]SInvalidationFile=ArchiveInvalidation.txtiRetainFilenameOffsetTable=1iRetainFilenameStringTable=1iRetainDirectoryStringTable=1bCheckRuntimeCollisions=0bInvalidateOlderFiles=1bUseArchives=1SArchiveList=Fallout - Textures.bsa, Fallout - Textures2.bsa, Fallout - Meshes.bsa, Fallout - Voices1.bsa, Fallout - Sound.bsa, Fallout - Misc.bsa This is my archive selection of falloutprefs.ini inside of MO's .ini editor. I'm using FOMM and using it's Archive Invalidation function as MO's doesn't seem to work. I installed type-3 and the fomod seemed all alright http://gyazo.com/c0f953bb94e9f6f1e3985e7524a95154 (Another thing when I do finish this fomod it does come up with errors. http://gyazo.com/9e8ef4ec4d861d092ffc4f50818ed4c8 ) And yet when I get into game, I get the graphical bug that occurs when Archive Invalidation isn't activated. This is the same for male and female graphics from both type-3 and Breeze's males. http://gyazo.com/19421a5fee265ead4558d5221d25520f MO's Archive Invalidation is still checked and the archives are managed by MO. ( Though still MO's Archive Invalidation doesn't seem to actually work ) http://gyazo.com/a1cba2f394fd1643b27b58fc98be4255 FOMM's archive invalidation is activate as-well. Yet still, the graphical bug remains.http://gyazo.com/a7d6797cd586f694fac29ef60fb715a1 I have absolutely no clue what to do anymore, I've tried quite a lot. Only activating FOMM's archive invalidation, re-installing New Vegas and MO ( I've done this thrice now ), tried just FOMM but even then FOMM crashes quite a lot for me so I do not wish to use it. Any help would be welcomed. Link to comment Share on other sites More sharing options...
MotoSxorpio Posted June 5, 2015 Share Posted June 5, 2015 Mod Organizer guides:On the Nexus- DeathNeko11's GuideSTEP - Step Guide to MO FOMM, as I remember, needed to be reset for new mods, especially mods packed as bsa. Using FOMM and MO for the same feature might be creating the issue(?) Good luck. :) Link to comment Share on other sites More sharing options...
Tanebowdash Posted June 5, 2015 Author Share Posted June 5, 2015 What do you mean by 'reset'? The Archive Invalidation being removed and re-applied? If so, I've done that for each mod, did nothing. And as-well, I have used only FOMM archive invalidaiton only without MO's automatic Archive Invalidation and that did nothing for it as-well. Thanks though. Link to comment Share on other sites More sharing options...
MotoSxorpio Posted June 5, 2015 Share Posted June 5, 2015 (edited) There's a toggle/check box for AII!! in FOMM, uncheck and re-check. That's a "reset". I apologize for not being clearer...I have my fav sport on the TV. :D I might have been distracted, but only a little. PS: iirc: On reset of Aii!!, it timestamps all esp and bsa so that not only load order but time stamp tells what to load, ofc loose files override everything. How load order and archive invalidation works has evolved with the games, ie Oblivion, Fallout 3 and New Vegas, Skyrim. The former three in that little list used time stamp, iirc, for the main part of load order, because mostly they were only concerned with DLCs working. So, it almost didn't matter if your load order was set or not...it only read the last modified date. Lengthy, but shorter than it deserves, explanation. Good luck. Edited June 5, 2015 by MotoSxorpio Link to comment Share on other sites More sharing options...
Tanebowdash Posted June 5, 2015 Author Share Posted June 5, 2015 (edited) Oh, thanks I never actually knew that reseting it, etc. But it seems it's a MO issue, I just got archive invalidation to work with FOMM with the player model mods and when I launched the game through FOMM it worked fine. But alas, all of my mods are on MO and FOMM scares me to living death. I've at-least narrowed it down to Archive Invalidation not actually being picked up(?) when MO launches the 4GB launcher inside of it. Any tips? Also slipping into a coma, so I'll read any responcies tomorrow and try to get this working. tl;dr MO doesn't pick up Archive Invalidation, help? Edited June 5, 2015 by Tanebowdash Link to comment Share on other sites More sharing options...
Tanebowdash Posted June 13, 2015 Author Share Posted June 13, 2015 Ha, I think I've exhausted everything now to the best of my knowledge ( Which is quite limited, probably staring me in the face ). Giving up. Going to bump it still and see if has somesort of secret to how to get MO to work with Archive Invalidation. I might just put up with the FOMM crashes at this point. Link to comment Share on other sites More sharing options...
fitzxvii Posted July 21, 2015 Share Posted July 21, 2015 Hey, sorry if this is a pointless necro, but one thing worth checking if you were still hoping for an answer: In the Archives tab of MO, between Plugins and Data, is "Fallout - Invalidation.bsa" the first archive in the list? If not, try moving it up to the top, above "Fallout - Meshes.bsa". That was what fixed it for me. Link to comment Share on other sites More sharing options...
maxman885 Posted June 30, 2018 Share Posted June 30, 2018 It seems im suffering the same problem but with nmcs texture pack roads.. andy help? Link to comment Share on other sites More sharing options...
dubiousintent Posted June 30, 2018 Share Posted June 30, 2018 NMC is a VWD/LOD texture replacement. These are handled differently by the game engine than the usual mesh/texture files for objects like weapons and armor. If you add any VWD/LOD textures, please see the 'Checklist Item #15 & 16' entries in the wiki "Fallout NV Mod Conflict Troubleshooting" guide regarding the need to run both TES4LL and FNVLODGen. -Dubious- Link to comment Share on other sites More sharing options...
Recommended Posts