Multiple Mods not Apearing In-Game

[JamesRednok]

So I've noticed lately that freshly-installed mods are not appearing in-game. Specifically, the three mods that are most conspicuous by their absence are Red Shift Power Armor, Stealth Suit - New Vegas, and Nixie Wall Clocks. I have tried installing them through NMM, Vortex, and manually; I've tried deactivating and uninstalling every other mod until it's just the vanilla game, the expansions, and these mods in the load order but nothing seems to work!

 

What's strange is, I've installed other mods before, after, and in-between these three and some of them work just fine. Others experience the same issue. It appears to be entirely random in which ones will work and which won't- effecting both ESPs and ESLs alike. I don't know what to do, any help would be greatly appreciated, thank you! =)

[LucidLady]

This sounds very puzzling. I experienced slightly similar problems back when I was using only Vortex - it's one of the reasons I swore not to return to it.

But you say you've tried installing the mods through NMM and manually, too? And you've tried only installing those three (plus F4SE)?

Are you installing/uinstalling these mods on an existing playthrough - or are you trying to see if they show up on a new character?

I wonder if it's an issue with your PC itself. Your PC may be resetting in some way. Do the files remain in the Data folder after you've stated and then closed the game?

Can you tell me what your Cached Memory is at? List off your other PC specs while you're at it. How often do you shut your PC down?

Afraid that at the moment all I can suggest is to stop using Vortex.

[JamesRednok]

Thanks for the advice! Funnily enough, I only tried installing them via Vortex when they failed through NMM and manually. Yes, the files appear and remain in the data folder; it's all business as usual there. But even searching for elements of the mods in question via the console produces no results. On old characters, new characters, or even a bear, certain mods just refuse to run in-game. I shut down my computer pretty much daily, but I don't see how it would have anything to do with my PC itself. Do you know of anyone else who shares this issue? Even if with different mods?

[LucidLady]

You had mods fail to install via NMM? Oof, this is a real pickle.

I think it MUST be something with your PC because so many people use NMM and Vortex and i've never heard of anyone with your particular problem.

It doesn't sound like both mod installers are the problem, here.

Have you recently changed something with Steam? Do you think Steam did an automatic update that might have messed you up? Steam might be trying to Sync files and failing. Maybe...

 

I really hope someone who knows more about this than me comes along.

[edgeburner]

I had the same issue with the Stealth Suit-New Vegas mod when I first installed the mod mid-game..

Have you tried a character that hasn't entered the area's were the unique variants spawn yet? I believe this mod may be script-injected at load, so a cell reset may not work....at least it didn't for me. running a character that hadn't entered those cells yet did work. Also, the unique assassins suit in not located IN the building itself, it's on a corpse lying on the ground outside of the building.

Not 100% sure, but I believe the craftable variant is listed as "recon suit" or something similar in the chem-station.

[JamesRednok]

So I found the issue! TL;DR: I was using an outdated version of F4 and F4SE.

 

Turns out, Steam didn't even recognize the fact that the game was still installed and insisted that there were no files for me to verify the integrity of. So after 'reinstalling' and installing the latest F4SE, Bingo-Bongo, the items were traceable in the console and appeared in-game just fine! turns out, the reason other mods were working- even ones I installed after the ones that weren't appearing- were older mods that had been published before the non-working ones. Hence, even though I downloaded them after the 'bad' ones, they were still compatible with my older version of F4, where as the 'bad' ones I installed earlier had been published later and were therefore newer.

 

Kind of an odd loop-de-loop flippity-floo, eh? Either way, it was Steam refusing to recognize my installed version that tipped me off. Now everything works, party's over, good night everyone; and thanks for your help! ;)