Vortex Changing Files Outside Vortex

[BrotherShamus]

I keep getting prompts from Vortex telling me that mods have been changed outside Vortex.  I don't make any changes but Vortex keeps prompting me about changes (in some case asking to delete files).  Also... 'manage rules' is broken but... one thing at a time.

[7531Leonidas]

I use CBBE3BA, and one of its adjustments to the lady parts makes/saves a file that Vortex reads as an outside file.  Drove me crazy, but I just have to deal w/it every time I update or reinstall 3BA.

Some dynamic mods may do something similar.  Have you taken a screen shot, so you can find the files in Vortex, or Explorer, to help you make a decision later?

[BrotherShamus]

I may have explained my issue poorly... what's happening is that I'll add a mod and then hit 'deploy'.  When Vortex deploys the mods, I'll get a pop-up window that tells me 'mods have been changed outside of Vortex' and it'll list the mods that have been changed (even though I haven't changed them) and give me the option to save, revert or... I can't actually remember the third option but I don't know why I'm getting the message at all as I've made no changes to any mods outside Vortex.

[ChemBoy1]

Which game are you managing where you are seeing this behavior?

[dizietemblesssma]

I get this all the time with Bethesda games on mods that I have not edited, now I just click yes to all delete prompts then deploy then reinstall that mod from scratch.

 

diziet

[BrotherShamus]

I'm modding Skyrim... also have FO4 installed but haven't opened that up in months so I don't know if it's also affected.  The problem with deleting and redownloading is that this is happening frequently.  I'm now having an issue with some missing textures that I haven't touched so... something has happened to my save without my changing anything.  At this point, I'm considering a switch to MO2 simply for stability and peace of mind.  I feel like there's a steep learning curve though.

Edited Tuesday at 04:07 PM by BrotherShamus

[ChemBoy1]

If this happens, you can simply Reinstall the mod from the mod list. You don't have to re-download (unless you deleted the archive).

It's had to say exactly what is causing these changes without understanding more about your environment. 

[BrotherShamus]

The thing is, it's happening frequently.  I'd have to load up Vortex and check for changes every time I play.  What's worse... it seems that with the latest update, it's reverting changes I've made manually so... I'll use the 'Manage File Conflicts' to sort conflicts... go into game and find an issue only to go back into Vortex and find that the changes I made have been reverted.  I actually did a full scan of my drives thinking this must be a virus but nothing came up.  I'm too invested at this point to switch over to MO2 but will be doing that going forward.  Managing a heavily modded game brings some degree of uncertainty... not being able to trust the tool you use to make things work just adds a complication that I'd rather not deal with.  I do appreciate the suggestions though.

[ChemBoy1]

3 hours ago, BrotherShamus said:

... not being able to trust the tool you use to make things work just adds a complication that I'd rather not deal with. 

I mod hundreds of games in Vortex, including Elder Scrolls and Fallout games with 1500+ mods. I rely on Vortex completely. 

[7531Leonidas]

Too many times ppl have problems w/Vortex because they expect it to work like NMM, or MO2, and don't really have any idea what Vortex is doing.  When I first started w/Vortex, I made the mistake of using a separate LOOT installation to make my LO, like I had to w/both NMM and MO.  That meant that LOOT was running w/o the benefits of the conflict resolution routines in Vortex.  Going back and re-reading the manual, and/or reviewing video help files might be useful.