Nexus-Mods / Vortex

Vortex Development
GNU General Public License v3.0
910 stars 134 forks source link

Can't install VR Performance Toolkit to game root folder. #14147

Closed kamikaze00007 closed 1 year ago

kamikaze00007 commented 1 year ago

VR Performance Toolkit is a small kit that is installed inside the root folder of the game for VR games like FO4 VR and Skyrim VR, to provide some necessary features that improve the graphical performance of these VR games. It needs to be in the same folder as the game's .exe as well as the Script Extender .exe files. As it is now, Vortex seems to be incapable of installing this mod to its proper location. Setting it's mod Category into "Utilities" like how F4SE is categorized, or as an "ENB Preset" doesn't do anything at all. The mod still installs inside the Data folder which makes it not work. It is also not possible to manually type in a category like "enb" as this tutorial states for ENB files to be installed to the root game folder.

There needs to be a way to set such mods like one would with the ENB main files, where the installation location is the root folder of the game and not inside the DATA folder. Right now, the only way to install this mod is to manually extract the files into the game folder.

OS: Windows 10 Vortex Version [1.7.8]

The easiest solution would be to add a Category that basically tells Vortex to install that mod in the game's root folder where the game .exe is. This should cover files like ENB too so it would be a one-stop solution.

To clarify,

Double-clicking the mod on my Vortex shows the right pane with only the following fields:

That's all. I don't see a Mod Type field, even though the column is ticked on and available on the mod list itself. This is on a fresh new install by the way. This is why I got confused and assumed what I'm supposed to do is set it in the Category field--simply because my rational mind states that it's the only field that gives me something with "ENB" written on it, and Category conflates with "Type".

Also, NOTE: Other mods downloaded straight from the Nexus which Vortex picked up allows me to indeed edit the "Mod Type" field. So I don't know why that applies to those mods, but not this one.

TanninOne commented 1 year ago

No offense but this is mostly a reading comprehension issue on your end. The tutorial tells you explicitly that this is supported and what to do. It's telling you to assign the "Mod Type" ENB. Categories are independent from this, the category is purely for organizing stuff, it doesn't (and dear god should it ever not) have an effect on how mods are being installed.

kamikaze00007 commented 1 year ago

No offense but this is mostly a reading comprehension issue on your end. The tutorial tells you explicitly that this is supported and what to do. It's telling you to assign the "Mod Type" ENB. Categories are independent from this, the category is purely for organizing stuff, it doesn't (and dear god should it ever not) have an effect on how mods are being installed.

I would understand my own stupidity and lacking of reading comprehension, but upon checking right now, it seems I'm not mistaken although I did seem to improperly explain the situation.

Double-clicking the mod on my Vortex shows the right pane with only the following fields: Description (thumbnail image) Mod Name Author Archive Name Version Variant Source Category Installer Collection Installation Time Enabled Time Downloaded Time

That's all. I don't see a Mod Type field, even though the column is ticked on and available on the mod list itself. This is on a fresh new install by the way. This is why I got confused and assumed what I'm supposed to do is set it in the Category field--simply because my rational mind states that it's the only field that gives me something with "ENB" written on it, and Category conflates with "Type". Perhaps you could tell me how to make it so I can edit the Mod Type then?

Also, NOTE: Other mods downloaded straight from the Nexus which Vortex picked up allows me to indeed edit the "Mod Type" field. So I don't know why that applies to those mods, but not this one.

TanninOne commented 1 year ago

The "mod type" field should show for any installed mod (state shows enabled or disabled), it's not available for mods that aren't installed.