Why dosen´t install Vortex Mods in a virtuell Folder?

[dilldappel]

I try with Skyrim Vortex and was realy suprise, that Vortex put the mods in the Install folder of the game. I had choose the install path and aspecting that all mods would be leave there. Why dosen´t install Vortex Mods in a virtuell Folder? I can´t like this not used different Modmanager together ore playing the game nativ.

[Dark0ne]

From Tannin on a similar question on our Discord server:

- There is no stable "commercial grade" vfs for free.
- The vfs I built for MO2 should work fine for the games and tools it has been tested with (since it has received a bunch of bugfixes from other devs now) but it is a common problem that a new tool wouldn't work until the vfs has been fixed to support it.
Considering Vortex supports >30 games plus their associated tools vs the 6 games MO2 supports (that all use the same engine) this would have been a maintenance nightmare.
- the MO2 usvfs can produce very hard to diagnose errors.
- usvfs is windows only whereas hard-links are supported on all platforms so it will be easier to port to Linux/MacOS
- usvfs will frequently trigger AV software
- usvfs causes a performance hit, hard links don't

There is probably a few other cons against the vfs - at least as the "primary" deployment method

Having said that, Vortex allows you to return to a "clean" state very quickly simply by clicking the "Purge" button.

[dilldappel]

From Tannin on a similar question on our Discord server:

 

- There is no stable "commercial grade" vfs for free.

- The vfs I built for MO2 should work fine for the games and tools it has been tested with (since it has received a bunch of bugfixes from other devs now) but it is a common problem that a new tool wouldn't work until the vfs has been fixed to support it.

Considering Vortex supports >30 games plus their associated tools vs the 6 games MO2 supports (that all use the same engine) this would have been a maintenance nightmare.

- the MO2 usvfs can produce very hard to diagnose errors.

- usvfs is windows only whereas hard-links are supported on all platforms so it will be easier to port to Linux/MacOS

- usvfs will frequently trigger AV software

- usvfs causes a performance hit, hard links don't

 

There is probably a few other cons against the vfs - at least as the "primary" deployment method

Having said that, Vortex allows you to return to a "clean" state very quickly simply by clicking the "Purge" button.

 

THX for the fast answer. I petty, but seems changes can´t happend in the future.

[Zanderat]

I wouldn't worry about it. Functionally does what I used MO for. The hardlink method works better and can be read by external tools whereas with MO they couldn't be read.

[dilldappel]

I wouldn't worry about it. Functionally does what I used MO for. The hardlink method works better and can be read by external tools whereas with MO they couldn't be read.

 

Mabye I need to understand what you mean with hardlink. On Unix hardlink means, the link become same functionelty as the parent file. Like this?

[Zanderat]

Yes. Tannin can explain better. But that is my understanding.

[HadToRegister]

It's essentially what NMM does, the actual mod is in the "Virtual Install" folder and is hardlinked to the Data folder.

What I like about Vortex is, if you edit an esp, Vortex detects it, and will physically write the edited esp to the data folder by asking if you want to SAVE changes or REVERT.