Vortex 1.0 Release

[HadToRegister]

I really don't know why these people complain. Vortex is amazing. Since your switching to actively developing features now, would you mind looking into emulating NMM's shortcuts to programs such as FNIS, Dual Sheath Redux, etc, right from the mod menu?

 

 

Why not just use the dashboard?

 

 

[RD61]

vortex = s#*!.....problems do not end

[HadToRegister]

vortex = s***.....problems do not end

 

So far everybody who has had problems with Vortex try and force it to be NMM, and 99% of the problems is user error.

[GravitationalPull]

In response to post #73089893.

MikeInWare wrote: The killer app for Vortex will be modpacks. It will suck in individual mods and create a "one click" install for newbies. Which is good!

when?

[Deleted59475776User]

I just installed Vortex to see how it works. The default "dark/gray interface" is not user friendly. Not good for the eyes. Go light for all interfaces, even Microsoft switched from Dark interface to light interface in the latest release of Windows 10. There is a reason behind this...

Also using the default installer, the installer didn't even inform me where it installed his files and a warning "Some loose files will not load due to a bug in game engine...", "Fix or dismiss?".

Should I trust blindly everything that do a manager? at least I should have some information about what he has done..

 

I just loaded a plugin from Skyrim LE (example the latest mod Citizens.esp) to see how this mod manager will react?

I didn't got a warning menu message "Old plugin" like what do Wrye Bash (and that's a complain I have about that manager) but there is a discret "Triangle" warning and if you click on it you read:

"This plugin was created by the original Skyrim and maybe not compatible with Skyrim Special Edition ..."

At least here Vortex is more cleaver than WB and recognize he is not sure about this ... "maybe yes, maybe not... right?"

Edited September 17, 2019 by Guest

[HadToRegister]

I just installed Vortex to see how it works. The default "dark/gray interface" is not user friendly. Not good for the eyes. Go light for all interfaces, even Microsoft switched from Dark interface to light interface in the latest release of Windows 10. There is a reason behind this...

Also using the default installer, the installer didn't even inform me where it installed his files and a warning "Some loose files will not load due to a bug in game engine...", "Fix or dismiss?".

Should I trust blindly everything that do a manager? at least I should have some information about what he has done..

 

I just loaded a plugin from Skyrim LE (example the latest mod Citizens.esp) to see how this mod manager will react?

I didn't got a warning menu message "Old plugin" like what do Wrye Bash (and that's a complain I have about that manager) but there is a discret "Triangle" warning and if you click on it you read:

"This plugin was created by the original Skyrim and maybe not compatible with Skyrim Special Edition ..."

At least here Vortex is more cleaver than WB and recognize he is not sure about this ... "maybe yes, maybe not... right?"

 

 

 

 

 

The default "dark/gray interface" is not user friendly. Not good for the eyes. Go light for all interfaces,

 

Change the colors to whatever you want.

 

 

 

 

 

 

 

Also using the default installer, the installer didn't even inform me where it installed his files

 

 

There are two versions of the installer, and they are clearly labelled

 

 

 

[Deleted59475776User]

In response to post #73446193.

HadToRegister wrote:

I just installed Vortex to see how it works. The default "dark/gray interface" is not user friendly. Not good for the eyes. Go light for all interfaces, even Microsoft switched from Dark interface to light interface in the latest release of Windows 10. There is a reason behind this...
Also using the default installer, the installer didn't even inform me where it installed his files and a warning "Some loose files will not load due to a bug in game engine...", "Fix or dismiss?".
Should I trust blindly everything that do a manager? at least I should have some information about what he has done..

I just loaded a plugin from Skyrim LE (example the latest mod Citizens.esp) to see how this mod manager will react?
I didn't got a warning menu message "Old plugin" like what do Wrye Bash (and that's a complain I have about that manager) but there is a discret "Triangle" warning and if you click on it you read:
"This plugin was created by the original Skyrim and maybe not compatible with Skyrim Special Edition ..."
At least here Vortex is more cleaver than WB and recognize he is not sure about this ... "maybe yes, maybe not... right?"

 

 

 

 

 

The default "dark/gray interface" is not user friendly. Not good for the eyes. Go light for all interfaces,

 

Change the colors to whatever you want.

 

 

 

 

 

 

 

Also using the default installer, the installer didn't even inform me where it installed his files

 

 

There are two versions of the installer, and they are clearly labelled

I know I can tweak everything ... even in Windows 10 (May update) you can get the dark theme with one click but the default is light, that is the difference. Even if there are two installers, the automatic installer should have at least showed the path where it install files.
Another thing, Vortex changed discretely my load order and the new load order recalled me the results I was getting when using LOOT. My load order never go beyond 50 plugins and I don't need that tool.

[HadToRegister]

 

In response to post #73446193.

 

 

 

HadToRegister wrote:

I just installed Vortex to see how it works. The default "dark/gray interface" is not user friendly. Not good for the eyes. Go light for all interfaces, even Microsoft switched from Dark interface to light interface in the latest release of Windows 10. There is a reason behind this...

Also using the default installer, the installer didn't even inform me where it installed his files and a warning "Some loose files will not load due to a bug in game engine...", "Fix or dismiss?".

Should I trust blindly everything that do a manager? at least I should have some information about what he has done..

 

I just loaded a plugin from Skyrim LE (example the latest mod Citizens.esp) to see how this mod manager will react?

I didn't got a warning menu message "Old plugin" like what do Wrye Bash (and that's a complain I have about that manager) but there is a discret "Triangle" warning and if you click on it you read:

"This plugin was created by the original Skyrim and maybe not compatible with Skyrim Special Edition ..."

At least here Vortex is more cleaver than WB and recognize he is not sure about this ... "maybe yes, maybe not... right?"

 

The default "dark/gray interface" is not user friendly. Not good for the eyes. Go light for all interfaces,

Change the colors to whatever you want.

 

 

Also using the default installer, the installer didn't even inform me where it installed his files

There are two versions of the installer, and they are clearly labelled

 

 

 

I know I can tweak everything ... even in Windows 10 (May update) you can get the dark theme with one click but the default is light, that is the difference. Even if there are two installers, the automatic installer should have at least showed the path where it install files.

Another thing, Vortex changed discretely my load order and the new load order recalled me the results I was getting when using LOOT. My load order never go beyond 50 plugins and I don't need that tool.

 

 

 

Vortex has LOOT built in, you don't need the standalone.

You also don't need to micromanage your load order like you did with NMM.

If you try to force Vortex to be like NMM, you're going to have a hard time.

[Havredave]

Preface: I really only play and mod Bethesda games at the moment, so my recent experience with mod managers is pretty well limited to that.

 

I thought I'd post something with a little more feedback for Tannin and crew in case it leads to development or explanation of current ways to do what I find isn't possible or easy in Vortex.

 

I never did have real problems with Vortex once I read its guides. I'd been using it since late alpha or early beta if I recall correctly, up until a few months ago. It worked fairly well out of the box, and most of the 'complaints' I had about it were addressed as I learned. I do not buy the comments about a mod not supporting use from Vortex. I've never met a mod I couldn't use from Vortex successfully, even ones that pretty strongly suggested that I don't. Am I an advanced modder? Maybe. Depends on who I'm compared with.

 

One of the Vortex features I thought was the most cool once I figured out how to tweak the installed archives properly is it can actually install SKSE/F4SE etc. and manage it from the mods list. Yes, Vortex CAN install the .dll and other files to the base game directory. It requires a little massaging (that might not be for beginners) of the downloaded .zip archive (not the installer version), but it works and works well. Cue other mods that want files dropped into the base game folder, and it becomes much easier to know updates are available and get them handled for the ones that are hosted on Nexus. That also means that mods of this type can be toggled on/off easily. You could even group all script-extender-required mods on and off along with the script extender really easily. I haven't tried it, but I'd imagine ENB could be handled like this also if you were careful and knew just what you were doing. Again, not exactly for beginners, but a cool feature.

 

I use MO2. Why? The overrides folder primarily. It helps immensely to keep the data folder clean as long as I don't mess with the data folder without MO2 being open. For example when I run a game and a mod creates files for personal configurations made through in-game SkyUI and similar menu systems, MO2 will show me what's been created in the override folder, and I can put them either in the mod they belong to or a personal empty mod created just for that mod's settings. That way the settings survive mod re-installs, updates, etc. The end result is I don't have files laying about that the mod manager has no idea what they go to, which leaves the data folder cluttered.

 

If Vortex has a way to indicate which data folder non-stock files it isn't managing are so I don't have to purge-and-guess, then move the files to the appropriate mod folder, I haven't been able to find it.

 

With MO2, starting with a fresh base game is as easy as wiping out my mods list or creating a new profile. With Vortex, my data folder gets filled with 'managed by vortex' files, empty folders, and other files that Vortex doesn't know belong with whatever mod I've run and later uninstalled, for example. Do these hurt a new mod build? No. Do these trigger OCD? Yep! Really though, you don't have to be OCD to appreciate a clean data folder. It also makes hopping between mod managers if you're inclined toward trying new things out for fun, a breeze.

 

That's one of the larger beefs I have with Vortex actually - when I ask Vortex to purge the entire mod list, please get rid of those managed by Vortex files, and clean up the empty folders properly. When I remove or deactivate a mod, I'd like it to remove the mod entirely like it already does, and if the folder associated to those linked files is suddenly empty and it isn't a stock folder, get rid of that too. I want a purge to leave me with a clean, pre-mod-manager data directory outside of anything I put there myself from outside the mod manager.

 

Another feature I'd love to see in Vortex is a way to browse the data folder and see what files belong to which mod like can be done in MO2's data tab. I don't use this tremendously regularly, but it's handy. See a script error with no mod associated? In MO2, look for the script in the data browser and you find out which mod it's from very easily. With Vortex it's a matter of opening.. every.. mod.. Or I guess I could use a command line to find it, but this really ought to be something the mod manager makes a simple task.

 

Oh, and please make the dashboard's launch section able to be resized so I don't have to scroll when I have so much unused horizontal screen space in the dashboard. While you're at it, why not make the blocks (I'm calling the dashboard a 'block') resizable and lockable? That could make the launch section tweak unnecessary if it auto-repositions the launch buttons as the dashboard is resized. Reorganizing those launch buttons would be nice too, and I don't recall that being possible from the Vortex UI after they're created.

 

If anyone knows how to get any of what I've mentioned done in Vortex, do let me know. I liked Vortex. I just don't like messy folders!

[jsonger47]

In response to post #73661678.

Havredave wrote:

Preface: I really only play and mod Bethesda games at the moment, so my recent experience with mod managers is pretty well limited to that.

 

I thought I'd post something with a little more feedback for Tannin and crew in case it leads to development or explanation of current ways to do what I find isn't possible or easy in Vortex.

 

I never did have real problems with Vortex once I read its guides. I'd been using it since late alpha or early beta if I recall correctly, up until a few months ago. It worked fairly well out of the box, and most of the 'complaints' I had about it were addressed as I learned. I do not buy the comments about a mod not supporting use from Vortex. I've never met a mod I couldn't use from Vortex successfully, even ones that pretty strongly suggested that I don't. Am I an advanced modder? Maybe. Depends on who I'm compared with.

 

One of the Vortex features I thought was the most cool once I figured out how to tweak the installed archives properly is it can actually install SKSE/F4SE etc. and manage it from the mods list. Yes, Vortex CAN install the .dll and other files to the base game directory. It requires a little massaging (that might not be for beginners) of the downloaded .zip archive (not the installer version), but it works and works well. Cue other mods that want files dropped into the base game folder, and it becomes much easier to know updates are available and get them handled for the ones that are hosted on Nexus. That also means that mods of this type can be toggled on/off easily. You could even group all script-extender-required mods on and off along with the script extender really easily. I haven't tried it, but I'd imagine ENB could be handled like this also if you were careful and knew just what you were doing. Again, not exactly for beginners, but a cool feature.

 

I use MO2. Why? The overrides folder primarily. It helps immensely to keep the data folder clean as long as I don't mess with the data folder without MO2 being open. For example when I run a game and a mod creates files for personal configurations made through in-game SkyUI and similar menu systems, MO2 will show me what's been created in the override folder, and I can put them either in the mod they belong to or a personal empty mod created just for that mod's settings. That way the settings survive mod re-installs, updates, etc. The end result is I don't have files laying about that the mod manager has no idea what they go to, which leaves the data folder cluttered.

 

If Vortex has a way to indicate which data folder non-stock files it isn't managing are so I don't have to purge-and-guess, then move the files to the appropriate mod folder, I haven't been able to find it.

 

With MO2, starting with a fresh base game is as easy as wiping out my mods list or creating a new profile. With Vortex, my data folder gets filled with 'managed by vortex' files, empty folders, and other files that Vortex doesn't know belong with whatever mod I've run and later uninstalled, for example. Do these hurt a new mod build? No. Do these trigger OCD? Yep! Really though, you don't have to be OCD to appreciate a clean data folder. It also makes hopping between mod managers if you're inclined toward trying new things out for fun, a breeze.

 

That's one of the larger beefs I have with Vortex actually - when I ask Vortex to purge the entire mod list, please get rid of those managed by Vortex files, and clean up the empty folders properly. When I remove or deactivate a mod, I'd like it to remove the mod entirely like it already does, and if the folder associated to those linked files is suddenly empty and it isn't a stock folder, get rid of that too. I want a purge to leave me with a clean, pre-mod-manager data directory outside of anything I put there myself from outside the mod manager.

 

Another feature I'd love to see in Vortex is a way to browse the data folder and see what files belong to which mod like can be done in MO2's data tab. I don't use this tremendously regularly, but it's handy. See a script error with no mod associated? In MO2, look for the script in the data browser and you find out which mod it's from very easily. With Vortex it's a matter of opening.. every.. mod.. Or I guess I could use a command line to find it, but this really ought to be something the mod manager makes a simple task.

 

Oh, and please make the dashboard's launch section able to be resized so I don't have to scroll when I have so much unused horizontal screen space in the dashboard. While you're at it, why not make the blocks (I'm calling the dashboard a 'block') resizable and lockable? That could make the launch section tweak unnecessary if it auto-repositions the launch buttons as the dashboard is resized. Reorganizing those launch buttons would be nice too, and I don't recall that being possible from the Vortex UI after they're created.

 

If anyone knows how to get any of what I've mentioned done in Vortex, do let me know. I liked Vortex. I just don't like messy folders!

I agree 100% about vortex messing up your game folders when you try to uninstall a mod but I only mod skyrim le and se
and I use MO2 any mod conflicts just drag them around is so much faster then the "rules" vortext asks for