Mods aren't unisntalling - Vortex?

[LucidLady]

Alright. One thing to be thankful about with Vortex - it realized that something happened to the PhyOp mod (which reduces the size of basically every single vanilla/dlc thing's texture) and it was a simple click to undo whatever got borked.

 

Gotta say, now the game seems to actually be running faster. Not blowing my mind fast, by any means. But noticeable. Odd.

Except... now my moon problem is back. I am deeply confused.

[StormWolf01]

Oh wow. It sounds like you've really had a strenous, stressful time of this :( I am sooo sorry :(

I am glad to hear tho, that you've got it all straightened out, (mostly) so at least all the effort was worth it.

I know exactly what you mean. You've got that problem solver mentality that won't let go of you, until you fix it. Same here to some degree.

Thanks for mentioning that texture mod. I'm gonna start the DL on that here pretty soon.

Steam. Ha. Yeah, that's another reason why I keep backups!

I'll check back in later to see what I can figure out about your mooning problem. It's been a long day, but I'll look into it this afternoon ;)

[StormWolf01]

Ok, I'm really sorry for the long delay in getting back to you. Doing too much distraction to keep me from doing the things I wanna do, LOL.

 

Ok, I've looked at the files from the moon mod. They've got several different versions, so I've listed the files from ALL of them.

 

Textures

Sky

MoonShadow.dds (5.6 MB)

Secunda_Full.dds (2.8 MB)

Secunda_Half_Wan.dds (2.8 MB)

Secunda_Half_Wax.dds (2.8 MB)

Secunda_New.dds (2.8 MB)

Secunda_One_Wan.dds (2.8 MB)

Secunda_One_Wax.dds (2.8 MB)

Secunda_Three_Wan.dds (2.8 MB)

Secunda_Three_Wax.dds (2.8 MB)

This is the main file. In this one, they're just texture files. Nothing that I know of that would bake itself into a savegame or anything. So somewhere or another, those files got put back into your game.

Under their "Larger Moon" optional file, that one is an ESP. I haven't downloaded it to open it up, but that would be another culprit to look for.

"Smaller moon" is also an esp. So again, another file to look for. And I also haven't DL'd to crack it open either. Mostly because I think that if it had scripts that were "baked in" then you'd have still been seeing it, before the problem went away and then came back.

First, you're gonna have to do another windows search of your entire computer, for the filenames that I posted. That sucks, I know. I'm really sorry. :(

Obviously, if you find them, delete them, and try the game again.

If you don't find them, I want you to disable everything, and start up a clean game. Just long enough to see if the problem is there with the moon or not. That will tell us if it's an issue that is baked into your save games. IF that's the case, I'm afraid that's bad. I don't know of anything that actually WORKS to deal with the savegames, aside from Face Ripper. Anything that I've tried, either doesn't install right, or just doesn't work right.

[G4M3W1NN3R]

Alright, yeah. Looks like a reinstall of every visual mod is all it takes.

Not sure what exactly killed all my textures, though. I've validated game files a BUNCH of times before, and never had this happen.

 

It made me way more tense than I needed.

This is just my personal issue, but - I get extremely, weirdly stressed when something on my PC isn't working, yet I can't figure out why. This simple face-sliders mod thing is bothering me way more than it realistically should. It's so basic, it should be easy to make it work and yet it doesn't work.

 

Gonna just play for a while and see if something non-visual makes the game explode.

 

"This simple face-sliders mod thing is bothering me way more than it realistically should. It's so basic, it should be easy to make it work and yet it doesn't work."

 

Ensure that you have both Looksmenu and it is installed and F4SE (Fallout 4 Script Extender), and that you are Definitely Launching the Game via the F4se_Loader.exe

 

Extended facial sliders, requires Looksmenu, which requires the Fallout 4 Script Extender, Looksmenu will Not Work if the game is Not Loaded by the Fallout 4 Script Extender, which in turn means the Extended Facial Sliders will also Not Work.

 

As for Vortex, it should Not be Installing to the Fallout 4 Data Folder, as it uses a Virtual Drive, as such, it will Not Uninstall from the Data Folder either.

[AugustaCalidia]

As for Vortex, it should Not be Installing to the Fallout 4 Data Folder, as it uses a Virtual Drive, as such, it will Not Uninstall from the Data Folder either.

 

 

You have apparently confused "virtual drive" with "virtual file system." Vortex absolutely does not create virtual drives, nor does it use a virtual file system for Bethesda Gamebryo titles. Rather, in these cases, Vortex uses Windows hardlinks, not symlinks. These hardlinks are deployed, not installed, directly to the game data folder. In the case of Fallout 4, once a mod is installed and deployed, a hardlink will appear in the game data folder. This hardlink mirrors the installed mod in the mod staging folder. For all practical purposes, it is the installed mod and persists in the game data folder even when Vortex is not running. The hardlink can be removed temporarily by purging and permanently by uninstalling. Purging does not remove the installed mod from the mod staging folder, but uninstalling does.

 

See this Nexus Mods Wiki article for some helpful information: https://wiki.nexusmods.com/index.php/Deployment_Methods.

[G4M3W1NN3R]

 

As for Vortex, it should Not be Installing to the Fallout 4 Data Folder, as it uses a Virtual Drive, as such, it will Not Uninstall from the Data Folder either.

 

 

You have apparently confused "virtual drive" with "virtual file system." Vortex absolutely does not create virtual drives, nor does it use a virtual file system for Bethesda Gamebryo titles. Rather, in these cases, Vortex uses Windows hardlinks, not symlinks. These hardlinks are deployed, not installed, directly to the game data folder. In the case of Fallout 4, once a mod is installed and deployed, a hardlink will appear in the game data folder. This hardlink mirrors the installed mod in the mod staging folder. For all practical purposes, it is the installed mod and persists in the game data folder even when Vortex is not running. The hardlink can be removed temporarily by purging and permanently by uninstalling. Purging does not remove the installed mod from the mod staging folder, but uninstalling does.

 

See this Nexus Mods Wiki article for some helpful information: https://wiki.nexusmods.com/index.php/Deployment_Methods.

 

i dont use vortex at all, will probably never use it and could care less about it or its installing methods, simple fact is, their are many people having issues with installing mods with it, and yet i have never had a single issue with NMM in many years. regardless of what method Vortex uses, it is clearly different to NMM, and Manual Installation, that is all that matters here, while it may not use Virtual Methods, it is clearly still having the same issues that Virtual Methods could have as well (Mod installation).

 

Virtual Installation Methods are more likely to have issues, then Direct Installation Methods, hence my assumption on Vortex Using Virtual Methods and the Fact that the same Author Working on Vortex is also the Same Author that made Mod Organizer, thus further enforcing my assumption.

[AugustaCalidia]

Virtual Installation Methods are more likely to have issues, then Direct Installation Methods, hence my assumption on Vortex Using Virtual Methods and the Fact that the same Author Working on Vortex is also the Same Author that made Mod Organizer, thus further enforcing my assumption.

 

Your assumption about Vortex is mistaken. If you understood what hardlinks are and how they function, then you would know that Vortex does not use what you call a "virtual install method" when dealing with Bethesda Gamebryo titles The referenced Nexus Mods Wiki article makes that abundantly clear. Furthermore, if Vortex uses some kind of virtual file system, then how is it possible for me to play my modded Bethesda games while Vortex is shut down and not running? If your "virtual install method" claims about Vortex were correct, then I could not do that. But, in fact, I can.

[G4M3W1NN3R]

 

Virtual Installation Methods are more likely to have issues, then Direct Installation Methods, hence my assumption on Vortex Using Virtual Methods and the Fact that the same Author Working on Vortex is also the Same Author that made Mod Organizer, thus further enforcing my assumption.

 

Your assumption about Vortex is mistaken. If you understood what hardlinks are and how they function, then you would know that Vortex does not use what you call a "virtual install method" when dealing with Bethesda Gamebryo titles The referenced Nexus Mods Wiki article makes that abundantly clear. Furthermore, if Vortex uses some kind of virtual file system, then how is it possible for me to play my modded Bethesda games while Vortex is shut down and not running? If your "virtual install method" claims about Vortex were correct, then I could not do that. But, in fact, I can.

 

 

read the post fully. and understand the context fully.

 

that is the last i have to say on the subject.

[AugustaCalidia]

 

 

Virtual Installation Methods are more likely to have issues, then Direct Installation Methods, hence my assumption on Vortex Using Virtual Methods and the Fact that the same Author Working on Vortex is also the Same Author that made Mod Organizer, thus further enforcing my assumption.

 

Your assumption about Vortex is mistaken. If you understood what hardlinks are and how they function, then you would know that Vortex does not use what you call a "virtual install method" when dealing with Bethesda Gamebryo titles The referenced Nexus Mods Wiki article makes that abundantly clear. Furthermore, if Vortex uses some kind of virtual file system, then how is it possible for me to play my modded Bethesda games while Vortex is shut down and not running? If your "virtual install method" claims about Vortex were correct, then I could not do that. But, in fact, I can.

 

 

read the post again. before replying.

 

i clearly stated this: while it may not use Virtual Methods, it is clearly still having the same issues that Virtual Methods could have as well (Mod installation).

 

context is very important here, i am not saying it using virtual methods, what i am saying it it suffers from the same issues that virtual methods have. understand this.

 

so as you can clearly see, i have accepted it does not used virtual methods. make sure you read the post fully before replying.

 

 

You also said:

 

 

Virtual Installation Methods are more likely to have issues, then Direct Installation Methods, hence my assumption on Vortex Using Virtual Methods and the Fact that the same Author Working on Vortex is also the Same Author that made Mod Organizer, thus further enforcing my assumption.

 

This sounds rather like a claim that Vortex does in fact use "virtual methods," your previous remarks notwithstanding.

 

Two other matters:

 

 

what is the point in even replying if you are not trying to help the op, all you are doing is trying to teach me something i really dont care about.

 

The point is to correct mistaken claims about Vortex for the sake of the OP and others reading these comments.

 

 

also do not even try and insult my intelligence by making it sound like Virtual Install method is a made up concept

 

Nowhere did I say or imply that "virtual Install method" is a made up concept.

 

Consummatum est. Vale.