How confident can we be that Vortex will restore the Game Directory to a Vanilla State after uninstalling all mods?

[ThelebKaarna]

Topic.

 

So for example, let's say you install texture replacer "A". Then "B", which overwrites some files from "A". Then you install replacer "C" which overwrites some files from both "A" and "B" (but not all). Then "C" which overwrites some from "A" and "C", but not "B". Anyways, you see where I'm going with this - get things really twisted. THEN you uninstall "A", "B", "C" & "D".

 

So is your game directory restored to a perfect vanilla state, without any missing or leftover files, or will things be wonky like with NMM?

 

Thanks in advance and sorry if already covered and I've not seen it.

 

-Theleb

[rmm200]

No one ever claimed that Vortex will return the game to a vanilla state.

It will return it to the state it was in when you started using Vortex.

Vortex copies nothing to the game directory, so when it removes it's hard links, all you are left with is the game directory.

If you want your statement to be true - do a clean install of your game, then use only Vortex to manage it.

If you install anything manually, like SKSE, then obviously Vortex won't remove those either.

[ThelebKaarna]

No one ever claimed that Vortex will return the game to a vanilla state.

It will return it to the state it was in when you started using Vortex.

Vortex copies nothing to the game directory, so when it removes it's hard links, all you are left with is the game directory.

If you want your statement to be true - do a clean install of your game, then use only Vortex to manage it.

If you install anything manually, like SKSE, then obviously Vortex won't remove those either.

Appreciate the response.

 

"How confident can we be that Vortex will restore the Game Directory to the exact state it was in prior to using it to install any mods with?" would've been a more accurate way to word my inquiry, sorry. And I of course get that Vortex isn't going to touch anything done manually (xEdit, ENB, etc).

 

Anyways, I was somehow under the mistaken impression Vortex moved files around. After further searching, found on the wiki:

 

Hardlink vs Virtual File System (VFS)

A common question users ask is "How is Vortex deployment different to Mod Organizer's VFS?". Both methods achieve a similar result but go about it in different ways. The VFS used by Mod Organizer (originally designed by Tannin, Lead Vortex Developer) has been heavily customised to work with Gamebryo (Bethesda's Elder Scrolls and Fallout series) games and popular tools for that modding scene. Using this approach in Vortex would have the following drawbacks:

There is no stable high-quality VFS with a free-to-use licence.

VFS methods require extensive customisation to work with different tools, hard links are supported natively as they are no different to access normal system files.

Diagnosing errors in VFS deployment is considerably more difficult.

USVFS is a Windows-only feature, whereas hard links are supported on all platforms. This means Vortex would be easier to support Linux or Mac operating systems.

USVFS can often trigger false positives on anti-virus software.

Hard links have no performance impact on the game, whereas USVFS will access files considerably slower.

This is not to say that using VFS is worse or bad, simply that Vortex did not opt for this as a default deployment method.

So I guess that pretty much answers it. And appreciate your confirmation as well=)

[NewThalos]

You can be confident that it won't much permanently overwrite your data folder, but it does add Vortex managed folders that are left empty once you purge the mods from the game folder. That said, these empty folders are benign and don't effect anything.

[Grestorn]

If I'm not mistaken, those empty folders are also deleted, if you use "Purge all mods".

[ThelebKaarna]

Thanks guys, but look at FNIS though. That mod is fully installed by Vortex (nothing done manually), yet purging all mods with Vortex doesn't remove everything. See Taylem's Youtube Video, time index 8:58. I've tested recently and had to follow his instructions to remove leftover file manually.

 

So I guess this is where my confidence is a bit shaken here...

[Grestorn]

FNIS creates files itself, these are not managed by Vortex. So before disabling FNIS, you have to use the 'CleanUp' feature of FNIS itself first.

[rmm200]

FNIS creates files itself, these are not managed by Vortex. So before disabling FNIS, you have to use the 'CleanUp' feature of FNIS itself first.

 

What version of Vortex are we referring to? Before the FNIS Extension was a thing?

Now FNIS data is written to it's own profile specific mod, which you enable like a normal mod, and which gets removed with the rest of the mods when you purge.

If it is not working this way - it sure gives a good imitation. All my profiles are happy with their own unique data, and there is no cross contamination.

[Grestorn]

FNIS Extension is still optional. I'm not using it and unless you're using multiple profiles with differing FNIS configs, there is no need for it. It's just another level of complexity.

[rmm200]

Well let me just say it has my highest recommendation. Between Skyrim and Skyrim SE, I have a good dozen profiles - and it works perfectly.

I just wish Bodyslide worked the same way.