So, AWOP may have made my game unsaveable.

Subject: So, AWOP may have made my game unsaveable. Fri Jul 27, 2018 11:21 pm

For starters, here is a modlist.

Modlist:

And a load order.

Load Order:

Basically, I installed A World of Pain for Fallout New Vegas, not even ten minutes ago, then disabled it before going into the actual game just because I wanted to finish a few things. As soon as I had launched FNV, WITHOUT AWOP, I saw numerous errors. For example, I use cellHUD. And as I loaded into the game, cellHUD was no longer a thing. No textures, nothing. I also use ADAM, and as I loaded in, there were no textures for the Outcast Ranger armor and the NCR Ranger Helmet. And, to add more icing to the cake, there was an error to the side of my screen, stating "PipBoy OS Not Found," or something along those lines.

So, I want to save my game. Badly. This is around 30 to 40 hours of playtime into a character that I absolutely love. I just do not know how I can. Any help?

Screenshots of the problem.:

Posts : 1947 Join date : 2014-03-01 Age : 31

As I recall AWOP doesn't even have any custom assets of its own so this is very weird. However I notice you're very close to the limit of 138/9 plugins loaded. If AWOP is an ESM those get loaded even if you disable them if I remember right.

Try toggling archive invalidation but failing that try disabling a few esps, see if the problem continues.

To clarify on the plugins thing, around ten or twenty of these plugins are disabled. And, I already had tried to disable and re-enable archive invalidation, both with Mod Organizer's integrated version and the downloadable one from the Nexus.

Any other ideas?

Posts : 1947 Join date : 2014-03-01 Age : 31

Looked into a little more and it turns out it doesn't matter if any plugin is disabled, them just being in your data folder will count towards the limit. Move the disabled plugins out of your data folder to somewhere you can get them again if you need to.

Other then that I'm out of ideas I'm afraid.

It doesn't look like the errors you've described are a result of overwritten textures. The screenshots are showing symptoms of too many plugins loaded

edit: since you're using MO it should be very simple to move the plugins. If you can't do try that I would recommend using Mator's Merge Plugins to reduce your plugin count

_________________
"It's me again, Mr. New Vegas, reminding you that you're nobody 'til somebody loves you. And that somebody is me. I love you."

Subject: Re: So, AWOP may have made my game unsaveable. Sun Jul 29, 2018 7:35 am

Alright. I took the day to do a fresh install of New Vegas, got the modlist to 119 ESP's (including a merge patch), used the Ordenador to make textures more optimized, and used FNVLODGen to get some better lod. Same thing happens. It seems that cellHUD is affected like before. The mouse cursor and the menu are all default DarN UI stuff and that same error from before is very small and in the place of the grenade indicator for Project Nevada. Any ideas on what this may be?

Modlist:

Load Order:

(It also messes with the main menu, specifically the new main menu that NMC adds.)

Screenshots:

Also, it appears it messes with Solid Project, specifically the hitmarkers (causing the same error message in the third image), and also flat out removes textures, like Mojave Sandy Desert.

I am honestly completely stumped. I can't tell if it is something like the Ordenador or if it is AWOP. Any ideas or help?

EDIT: All plugins are activated and numerous merges are in the list. The total plugin count is 119.

Posts : 1947 Join date : 2014-03-01 Age : 31

Did you use the texture optimizer before? I wouldn't be surprised if running it on textures used for the interface broke something, they need to be saved in a certain way that I can't quite recall to work (its been a really long time since I've done UI stuff). I've also heard of it messing up textures that have already been saved correctly, but that was mainly a Skyrim thing.

Subject: Re: So, AWOP may have made my game unsaveable. Sun Jul 29, 2018 9:58 pm

I did, yes. But it was before the AWOP installation.

This is honestly the most confusing issue that I have ever had with New Vegas. Because I do not understand how AWOP could possibly cause my game to not load in texture mods and cause these errors.

Posts : 1947 Join date : 2014-03-01 Age : 31

I'm afraid I'm out of ideas man, the symptoms are of loose files not loading, hence the interface files and the main menu replacer not working. That would mean ether archive invalidation, Inis set to read only (UIO doesn't work with inis that can't be edited), corrupted textures/incorrect file formats or being over the plugin limit. If one of those isn't the problem then I've never seen this happen before.

I hope you can get it sorted.

Thing is, if I have a set of mods, without AWOP, none of the issues I have said come up. But as soon as I install AWOP, the game breaks.

Now I have done three installs. Just going to not install AWOP for future reference. Thanks for trying though.

Subject: Re: So, AWOP may have made my game unsaveable. Mon Aug 06, 2018 6:35 pm

Been testing my mod list and order for a new playthrough. Saw your post and decided to throw AWOP into the mix sooner than later to see if similar issues cropped up even with a fairly different mod list to yours (much smaller and no TTW, just New Vegas). And yep, issues cropped up quickly and constantly; missing textures, missing LODs, voice files not working, infinite load screen, random freezing. And as soon as I remove it and start a new save, everything is A-OK. I've never had issues like this with older versions of the mod (but that was a couple years ago). I messed with the load order, bashing/not bashing, patches, no patches. Problem never got resolved. So I'm guessing there's either a serious mod conflict (which I can't find in xEdit) or something is wrong with the latest version, including the very latest update file. My hunch is something in AWOP.

Know that doesn't really help resolve the overall problem, but at least you know you're not the only one and chances are it's AWOP and not you. If I figure out it is something else I'll be sure to mention it.

Posts : 75 Join date : 2018-03-14 Location : SPAIN

yeah its a problem from the new version of AWOP try the old version !!

_________________
So, AWOP may have made my game unsaveable. A4DDC105E3ED40BC44123C6E92322C4C5638C41B

Posts : 95 Join date : 2015-01-25 Age : 52 Location : Mars

Strange, I've played through both games with 350 mods merged together into 127 plugins including TTW, Interiors, AWOP, AWOP4FO3 all someguy's mods and many others with NMC's Large texture pack on top.

You are simply running out of ram from too many texture replacers.

Try not to blame mods for problems with your setup.

Posts : 26 Join date : 2015-07-28

Hello, I am a king lurker but I thought I would chime in since I have seen this problem before in my game.

As others have said this is what happens when you have too many plugins loaded. The "hard" plugin limit is what, 135? Depending on the mods you use you will hit the "soft" limit sooner than that. This differs for everyone. Personally I use many large mods and cannot run anything over 120 or I start to get exactly what you have - black dropped textures and exclamation marks.

If you are using many large mods that add new worldspaces, dialogue, and scripts (TTW, quest mods), high res texture mods (any texture pack, Weapon Retexture Project, Enhanced Blood Textures, cellHUD or any UI replacer) any mods that significantly increase the poly count of meshes in the world (armor replacers like dragbody's Ultimate NCR, New Vegas Redesigned, Millenia's Weapons, probably LODs), anything that adds new NPCs to the world, especially spawn multipliers, then all of these things are going to weigh heavily on your game and cause you to run out of memory much more quickly. Your problem is that you are running out of memory the moment you load the game.

I suspect that AWOP seemed to be "causing" it because that mod creates a massive new world space with lots of AI packages, scripts, and quests and the stress of loading all these things was depleting your memory before you could get into the game. In reality AWOP probably has nothing to do with the problem itself and is just the tiny stick of driftwood that floats in and breaks the already overflowing dam.

The easiest way to see if this is a memory issue is to simply start subtracting plugins from your load order. Keep AWOP and start dropping some plugins in batches of 5. If it eventually stops with AWOP still active, you can start to figure out if it is a memory problem and where your memory limit lay. It's different for everyone.

Many of your plugins can be merged. I cannot see which ones you have checked on or off but I see many which I immediately recognize as mergable. All those weapon mods should be merged into one plugin. The TTW optional files can all be merged into a single file, I believe the TTW says not to do this but it works perfectly and there is no reason not to. Just don't merge TTWOptions because it breaks its MCM. There is a merged plugin for More Perks and Traits that combines all of their perks and traits from the base game + dlcs into one esm.

There may also be some magical ini edits that could help, but I have no suggestions in that area. Sheson's memory patch for skyrim works for New Vegas now, you're probably using it but in case you aren't, here is a post for it. http://forum.step-project.com/topic/4490-memory-patch-has-been-ported-to-nvse/. This may fix your problem by itself if you aren't using it, as it does not come with NVSE by default.

Guest

This sounds simple, and probably will not work, and is a really outdated response, but for anyone else having this problem who uses MO2, check your file paths. Also check that NVSE did not mysteriously break, and try updating.

» If Bethesda Made a Star Wars Game?
» [SOLVED] [FNV] Compatability issue with AWOP and FCO 3
» Well I made it. Now what?
» What do you think of this wallpaper I made?
» If they have made it I shall find it.........

So, AWOP may have made my game unsaveable.

So, AWOP may have made my game unsaveable.

Similar topics

Similar topics