Jump to content
⚠ Known Issue: Media on User Profiles ×

consciouslycomatose

Members
  • Posts

    3
  • Joined

  • Last visited

Nexus Mods Profile

About consciouslycomatose

consciouslycomatose's Achievements

Newbie

Newbie (1/14)

  • First Post
  • Week One Done
  • One Month Later
  • One Year In
  • Conversation Starter

Recent Badges

0

Reputation

  1. I did verify, after reinstalling three times. uwu. I'm desperate as you can tell lol Yes, I did do that. However, it extracted them properly and all files are where they should be according to the readme of both. F4SE functions. I tried going from a clean backup, and in the process found that there is another Fallout4Prefs.ini in my Fallout installation. I don't know if that's part of what changed things, but I added the invalidation there, and now it's working. Thank you very much for your help.
  2. I have exactly two mods. F4SE and Fallout Who. These are proven to work together. I have implemented every workaround by now in my quest to do what must be done. I brought both mods into NMM and installed and activated them. I put the famous archive invalidation lines into both Fallout4.ini and Fallout4Custom.ini [Archive] bInvalidateOlderFiles=1sResourceDataDirsFinal= I've also opened only the launcher, made sure both the ini's and the plugins were all checked and activated still; I went into the mod order ingame and made sure they were all activated; I've tried launching from F4SE & the base game, both with and without NMM. I've done just about EVERYTHING, and yet, anything a mod adds (if it even exists at all) behaves as though archive invalidation hasn't been implemented. I'm using Windows 10. Please, if someone can help me-- I'm happy to bend over backwards if I can just. finally. play. with. mods.
×
×
  • Create New...