BeowulfSchmidt

Gopher has also done a very good set of Vortex tutorials, including one covering how to install SKSE using Vortex if one chooses to do so. Highly recommend. Search youtube for "Gopher vortex".

SKSE is sensitive to the version of Skyrim itself. Make sure youâve matched up the version of Skyrim you have and get the appropriate version of SKSE.

If all you want to do is avoid redownloading your mods, trey renaming the folder that contains all your mod downloads, then install Vortex, open Vortex, and then copy and drag all the mod archives from the old folder and drop them on the Vortex âdownloadsâ panel. If you want to avoid reinstalling all your mods, I think youâre out of luck. As was mentioned, Vortex maintains some metadata about the mods youâve installed, and thatâs gone. Hopefully, one of the devs can provide more information if that is in fact possible.

In my opinion, downloading to the game directory implicit in the Nexus game section from which one is downloading is the correct behavior. If I'm on the Nexus and downloading a Skyrim SE mod, I don't want it going to some other directory. At least not without a warning, or a game specific setting. Just because I'm currently managing Skyrim doesn't mean I might not want to download an XCOM2 mod, and I sure as heck wouldn't want to mistakenly download such to my Skyrim directory. I wouldn't even want a global setting. If you can do it, I'd actually like to see a game specific setting. So on the Skyrim VR game management, there'd be an option for "If I'm managing this game (Skyrim VR) and I download from this section of the Nexus (Skyrim SE), it's OK." If I'm managing some other game, or I'm not downloading from the selected Nexus section, then whatever I download should go to the appropriate game directory.

If youâre actually running Vortex as admin, i.e. youâve chosen âRun as Administratorâ or set the shortcut to Run as Administrator (either of those options should display the Windows UAC box asking if youâre sure you want this application to make changes to your computer), try opening your default browser as admin first. And, as I posted before, if youâre habitually using âRun as Administratorâ, as opposed to just being logged in as an account with admin privileges, don't. :)

If Vortex itself, as opposed to the installer, doesnât need to run as admin, it shouldnât be run as admin. Arbitrary and unnecessary elevation of privileges waters down the security Windows is trying to enforce. Itâs not stupid for Windows to enforce security between admin and non-admin applications, itâs stupid to run as admin when itâs not needed. Heck, I have a separate account for day to day use that isnât an admin.

Is there already a category field that one can set for mods. I thought I remembered seeing one. If there is, why would you not use that, instead of messing with the lid order.

@Tannin42, if I recall correctly, when one changes the directory to which mods are downloaded, Vortex actually moves any that already exist in the old location. Am I remembering correctly?

Did you provide feedback in Vortex's feedback option? That's probably a better way to get the issue in front of the dev.

You could probably have just started over with an un-modded game (I backed up all of my game folders before starting with Vortex) and re-installed those mods from their sources. That would have let you deal with them individually; the way you've done it, Vortex sees one mod, rather than each individual mod. That's not a criticism, whatever works for you works for you. Just noting the other approach for others who might pass this way.

Sadly, that's not it. I would have been happy were it user error. :)

From what version of NMM are you trying to import?

Given that there is likely some functionality of NMM that will never be implemented, that basically means that Vortex would never be released. As well, this is an alpha, which is clearly posted in multiple places on the download page. It's not a stretch to think that there might still be some features not fully implemented. Programs like this are never feature complete. There's always something. Claiming that it shouldn't have been released is like saying that one shouldn't taste the soup until it's on the table.

Can you post the entire contents of the "Target" value, i.e. copy it out of the box and paste it in here. If the target is in fact, a Java ARchive file, rather than an executable, batch file, or command file that wraps the call, you might need to call java.exe, or include some command line parameters. It's possible that Vortex, or the operating system itself, is automatically running Java when the target is a jar file. Have you verified that you have Java installed, and that the path to the java.exe executable is in your path? Some apps check for, and install if absent, the required version of the Java Runtime Environment (JRE), while others depend on you to do it. To check if java is present, open Windows Explorer, navigate to the root of your C:\ drive, and in the search box, type "java.exe". If it finds anything (it will probably be in either "C:\Program Files\Java" or "C:\Program Files (x86)\Java") or both, you at least have a version of Java installed. If you find it, open a command prompt, and just type "java --version" at the prompt. If you get version information back, Java is at least in your path. Check that version number against the version of the JRE that your patchers require. If you don't get a version blurb, you'll need to add java to your path. At the same command prompt, type "path" (without the quotation marks) and check for any If you have Java installed, open a command prompt, change to your "Start In" directory, and then execute the exact command line you have in "Target". If that works flawlessly, then the problem might be with Vortex. If you get "bad command or file name" or some such similar message, it means you need to add Java.exe to the beginning of your "Target" command. You might also need to If it runs, but generates an error, the error generated might yield a clue. In the event the above doesn't work, in that same command prompt, navigate to your game's data directory, and execute the "Target" command line. If that works, you'll need to change your profile's "Start In" value to the game's data directory.

I'm not sure that's 100% true. I get different results when I sort with LOOT than I do when I let Vortex sort. For instance, LOOT sorts Lanterns of Skyrim before Unofficial Skyrim Special Edition Patch, but when I select "Sort Now" in the plugins tab, the order is reversed. I know from reading LoS's Nexus page that it should in fact go before USSEP, so perhaps it's simply a matter of Vortex, for some reason, not having an updated rules list? I'm using LOOT version 0.12.3 downloaded from github just a week or so ago. ​That is why I made the question. I've seen LOOT sorting the load order in a different way that Vortex does it ... however, in relation to this particular mod : Lanterns of Skyrim, I setup a rule in Vortex to load this mod first and before USSEP so when I run LOOT, this mod remains in the position I told Vortex. And what you pointed out about this mod is strange, because back in NMM, Lanterns of Skyrim was ALWAYS placed before USSEP by LOOT, so I do not know what is going on with your setup. ​I recommend to setup a rule in Vortex; choose USSEP to "load after" Lanterns of Skyrim and RE-DEPLOY ( button located under MODS tab ) so changes will apply. After that, run LOOT and see what happens. LOOT should respect your decision and if it does not, then use the feedback in Vortex but I doubt it that you would have to do that. I think you might have misunderstood. LOOT already puts LoS and USSEP in the right order. It's Vortex that puts them in the wrong order. I'm well aware that I can set up a rule to make Vortex do the right thing, but that's not the point. If Vortex is supposed to be doing the same thing that LOOT is, it's not. That cause might be the version of LOOT I'm using versus the version of the LOOT API that Vortex is using, or it might be that, for whatever reason, Vortex isn't using the same master list that LOOT is, or it could be because I'm doing something wrong. I'd prefer to find out what the actual problem is before I go an try to fix it. For now, LOOT is doing the right thing, so that's the method I'm going to use. I will happily change things around, if necessary, when I know what the actual issue is. FWIW, I've submitted feedback from within Vortex. I'll be happy to perform any addition test tannin thinks might be helpful.

Good luck to me! :)

For future reference, you should be able to add the -d flag to the Vortex WryeBash command line. Use the three vertical dot menu in the command block, and choose edit. Just out of curiosity, what happens if you Purge Mods, then Deploy Mods, then enable them all, and then try to run WryeBash?

I'm not sure that's 100% true. I get different results when I sort with LOOT than I do when I let Vortex sort. For instance, LOOT sorts Lanterns of Skyrim before Unofficial Skyrim Special Edition Patch, but when I select "Sort Now" in the plugins tab, the order is reversed. I know from reading LoS's Nexus page that it should in fact go before USSEP, so perhaps it's simply a matter of Vortex, for some reason, not having an updated rules list? I'm using LOOT version 0.12.3 downloaded from github just a week or so ago.

I believe you have to explicitly tell NMM to take back control of the links, simply turning it off in Vortex won't revert it back to NMM (or MO, for that matter). It's an operating system setting that applications set, not a setting in the application itself. I haven't used the new NMM, but the old one had an option somewhere in the menu system to take control of those links.

Did you download the Vortex installer from Nexus, or somewhere else?

+1 Probably not quite as simple as it sounds though. Do you want installed mods, or enabled mods? Should it be an unconditional display, or only when requested? Should it be in the scripted installer window, or a separate one? A reasonable feature, but there are probably permutations that neither of us has noticed.

Seems like a reasonable feedback item, as I expect the devs to look at feedback from the app before feedback here. Not because they're ignoring what's posted here, but because it's in the actual application.

Ads pay for the internet, just as ads paid for radio and TV in their heyday (and still do for those of us who've migrated back to broadcast). The ads on Nexus aren't especially obnoxious. They don't play sounds, they don't display a pop-up, they don't open a new browser instance, they're just there. They're among the absolute least obnoxious ads I've come across on the entire web. You can click on them or not, and they don't annoy you when you don't. Vortex is part of the Nexus platform, it's one piece of the whole. Nexus is eminently usable without it, either by manually installing mods, or by using one of the other mod managers that are available. Vortex promotes premium membership because, as part of that whole, it costs money to produce and operate, just as the other pieces do. The greater the number of people who are reminded that they are receiving value without being required to pay for it, the more likely it is that some of them will recognize that value, and contribute to offsetting the costs involved. And in fact, as I recall, Vortex only displays one ad, the one for premium membership. It doesn't display any of the other ads that Nexus does, though I believe it's well within the capabilities of the application platform that's been chosen to do so. So there's that as well. In addition, the Nexus does not stop you from accessing it when you use an ad blocker, a strategy becoming much more common among freemium web sites. You are, of course, free to continue using both Vortex and Nexus for absolutely free, without having your access restricted in any meaningful way. Neither Vortex nor Nexus (to the best of my remembrance) has any features, save for the premium servers, unavailable to those who won't (or can't) pay, so you have absolutely the same functionality that I do, and that all the other premium subscribers do, without paying one red cent. So, your choices appear to be: pay for some level of premium access, stop using Vortex and/or Nexus, or deliberately thwart the site's owners by using some form of ad blocking, thus withholding even the paltry revenue that ad impressions give them. Personally, I hope you'll choose the first of those, as even the lifetime membership was ridiculously inexpensive when compared to the value I've gotten from the site over the course of the last few years for just one game, Skyrim.

Are you sure the installation process is complete? I have noticed a couple of places where the UI thread appears to not quite be in sync with what is actually happening. Or rather, two different parts of the UI are reporting two different things. I've been trying to pin it down in order to report something akin to an actual reproduction recipe, but it doesn't seem to be consistent. Have you tried closing Vortex and restarting? Have you tried restarting Windows?

 You can, but not in a way that i am content with.  example: i have battlegrounds installed at C:/PUBG. Can't have that with plain steam, can i? Yeah, if youâre not happy with the way steam organizes things, youâre gonna have a harder time. Your way is a little more flexible in that you can scatter your actual game directories all over your file system, according to your own needs, and just have hard links or junctions in steamâs location. Vortex currently has some requirements that make that flexibility...problematic, however. Also however, this is an alpha of the first version, so while handling that flexibility would be a good feature, I suspect it takes a back seat to primary functionality. Fortunately, Vortex will be open source, so someone whoâs really interested in that feature could probably write a patch and petition for its inclusion.